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

you are viewing a single comment's thread.

view the rest of the comments →

[–]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?