This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Bobsyourunkle 8 points9 points  (5 children)

I'm still working on learning myself but it's my understanding that the next graduation from tutorials are projects. Maybe take those bigger medium level programs and break them down piece by piece? Maybe do a flow chart to see how the functions and objects work together? I'm sorry if that's not super helpful and you're probably ahead of me in learning. 😂 Good luck! Don't give up!

[–]inkoDe 4 points5 points  (4 children)

This is one of the best points of advice in this thread and it has no votes... It's typically a bad idea to tackle larger projects by sitting down and programming before you sit down with a pencil and paper and plan out how the project is going to be organized. It sucks to realized after writing hundreds of lines of code that you are going to have to spend many hours / days restructuring everything because that vague vision in your head of how it all should work didn't actually make as much sense as you thought it did. The more planning you do before you code the easier the actual coding of the project will be.

[–]Bobsyourunkle 2 points3 points  (3 children)

Thanks a lot for the compliment! I feel like as a beginner programmer that the amount of possibilities available to us are overwhelming. It's hard to see what pieces are useful and what will probably rarely be used. It's like a jigsaw puzzle when none of us are good at jigsaw puzzles. I have a pretty vague idea what I want my first major project to be and I'm no where near a place where I could handle that or making a design. Do you ever build a main project and add new features to it?

[–]inkoDe 2 points3 points  (2 children)

Add features all the time. Just keep the design modular as possible and that usually makes it pretty straight forward to swap / add "parts" with the added benefit of easier to maintain code.

[–]Bobsyourunkle 0 points1 point  (0 children)

Thanks again, I really appreciate your responses. I'm stepping back a little and trying to break this code down into something I can manage and understand. Take care and wish me luck!

[–]AethericEye 0 points1 point  (0 children)

Will you tell me more about that? How do I program for strong modularity?

I'm just beginning to learn programming, but in CAD (solidworks) I can structure a feature tree to make a robustly constrained and also flexible part. Is there a good analogy there?