So when you first started learning math in elementary school and got many questions wrong, I could tell you to give up and go do something else.

Your argument is that of a 10 year olds. Who the hell tells someone to quit when they haven't even broke the water yet.

I wouldn't doubt it.

Code is subjective, primitive, and new fads/styles/paradigms come and go.

As your project scales in scope, it seems like you either bolt more shit on that you didn't expect, or at some point just do a full rewrite.

years later, rinse repeat.


The only thing that won't betray you is coherent code in small, logical chunks that can be unit tested.

Use overloaded functions. Use classes to define objects when you need to pass around lots of data. Add comments when you do something that is unusual.

Whatever you do, don't be the only person who can read the code you write. Some might argue job security, I would argue incompetence.

Hey,

Thanks all for the criticism, good and bad. I dont mind a few douches in the road but, as you've all mentioned, I'm learning and drinking from a firehouse. Six weeks to be exposed/learn linux, memory management, concurrency, C++, and C. I'm definitely drowning, programming isn't a skillset had prior to college but that's why I chose CSE over EE, I prefer the challenge and love the learning curves.

Anyways, I plan on doubling back and soaking up as much as I can in the future. It's been an arduous five out of six weeks so far but extremely enjoyable.