Learn it. 7-8 weeks should be fine, and even online isn't an issue, most of the work is by yourself anyway. It's good to have someone to ask if you get stuck, but it doesn't seem that difficult. Stop procrastinating.
Learn it. 7-8 weeks should be fine, and even online isn't an issue, most of the work is by yourself anyway. It's good to have someone to ask if you get stuck, but it doesn't seem that difficult. Stop procrastinating.
Yeah. I think you're right. I'll do it.
java and c++ are not easy as starter languages, and if you don't have a good professor to explain the fundamentals properly you are doomed.
Python is more "forgiving", although some basics are still needed before you write the first line of code.
IMHO the "Hello world" program is a stupid way of starting a course. Start with explaining data types, assignments, operations, functions in plain English. Then use them to write the hello world program.
I think I hung in there about 2 weeks with Java and then bailed. This was in mid 2002. So back then, what were we using? Still on Windows 98/ME or something? Maybe Windows 2000 with XP on the horizon? Linux was barely a thing yet in the mainstream -- or at least not that I could see. Seemed like everyone was mostly on Windows back then still. So resources weren't as plentiful back then which is part of why I think I had more trouble. Then in 2008 I tried to take the "C Programming" (I just looked at my transcript). So not even C++,... just plain C (not entirely sure what the difference is except I think C is older and more difficult to learn?) Well anyway, again I hung in about 2-3 weeks. First couple weeks I was really doing well and getting it. We were doing algorithms, and other non-coding sorts of things.
The part that where I derailed both times was for 2 reasons (and I had trouble with this in Shell Scripting too). First, the syntax. There is only ONE way to deal with that and that is to practice practice practice. I tend to not be the most patient person and so I can never get it to stick. The second part is when it comes time to start learning For and While loops. In my mind, I see it as For loops are for setting finite tasks and While loops are for setting infinite tasks. But the application of either of those things makes no sense to me.
So let's say you wanted to write a program that picks up apples on an assembly line and then puts them down. If you only had 10 apples then you write a For loop to do something 10 times. If you don't know, then you write a While loop to do it until something happens. Ok cool, I get that. But when it comes time to start writing it all falls apart in my head. For some reason For is needed instead of While. Or vice versa. I can't get the logic of it and then I get frustrated and give up.
Another problem I have is with If, Else. In my brain, it should be, "If I have an iPhone then I can download iPhone apps or else I can't". But when you go to code, it doesn't actually write out that logically. At least to me it doesn't.
So if I do this, then I'm going in with all these bad experiences I'm hoping to one day overcome. I did pass the Shell Scripting class so I know I can do it. But man it's hard. Doesn't come easy for me.
Last edited by Webhead; 11-12-2014 at 07:55 PM.
Ummm... you're thinking in terms of what you'd WANT them to be, not in terms of what they are. They are both (or all 3 if you consider while{} and do{}while) loop control methods. They work pretty much the same, you can see FOR as an extension of WHILE, it performs one operation before the loop and one operation at the end of each loop.
Writing
is EXACTLY THE SAME asCode:for(a=1; a<10; a++){ BLAH; }
except for maybe a couple of minor compiler optimizations.Code:a=1; while(a<10){ BLAH; a++; }
And hell, you could write
^--- exactly the same shit.Code:a=1; for(;a<10;){ BLAH; a++; }
Just view FOR(THING1, CONDITION, THING2){
BLAH
} as
THING1
WHILE(CONDITION){
BLAH
THING2
}
In other words, both do a loop while a condition is true, FOR will also set a variable and do another operation for you part of each cycle. It's usually an increment/decrement of the counter for legibility, but it doesn't have to be.
Formulating the problem properly is very important. If you know for sure you have at least 10 apples you write the loop to pick 10 apples. But it may happen that you SHOULD have 10 apples, but on occasion you have fewer.
why???
Don't think in terms of code. Think in terms of plain language. Big blocks that get broken into smaller blocks. Then code it, and you can code it in almost any language.Code:if(phone==IPHONE){ GoToDownload(); } else{ Display("Sorry"); }
Reading your post brings me back to when I was in class trying to learn it. I don't think I've had the patience or focus to do well with it previously. These days with math, I've gone into it with more patience and focus this time and have improved a lot so maybe the same will be true for this. Gonna give this one more try. Maybe third times a charm.
Eeek.
I started my project. It is a great language to learn but the learning curve is a bit steep for me right now.
Not to mention I want to integrate my project with excel. Which can be easily done, or so I have read. I don't have excel right now and am not sure I am going to buy it for this.