3 ms·
Useful is a very broad term. My definition would be,once you can take a problem (whether it be your own or anothers) and solve it through code, your useful. Eve
by alexkiwi 16y ago
Useful is a very broad term. My definition would be,once you can take a problem (whether it be your own or anothers) and solve it through code, your useful. Even if it is small, it's still useful
- danilocampos 16y agoHmm, okay, that's fair. But what about all the issues of code quality, modular architecture, and anything else that would make you a developer someone else would want to work with? When I first got started on the iPhone, for example, I could solve certain problems through code, but that code was crap. I cringe to look at it now.
- olalonde 16y agoI would suggest reading a book on "meta" programming. Code Complete would be a good starting point.
- danilocampos 16y agoThanks for the guidance. What benefits might I enjoy from meta programming?
- _pius 16y agoGenerically, the fastest way to go from zero to a useful member of a programming team is to learn and consistently execute classical software engineering practices (e.g. document code, use encapsulation and abstraction, write tests). Those practices aren't designed to optimize for individual programmer productivity, but to allow programmers of all different skill levels to work together safely and effectively.