3 ms·
There's a balance here. On the one hand, you have to have the ability to figure things out on your own when nobody knows the answer; sometimes you do need to r
by JoshTriplett 11y ago
There's a balance here. On the one hand, you have to have the ability to figure things out on your own when nobody knows the answer; sometimes you do need to read through a pile of undocumented "legacy" code and puzzle out what it does. On the other hand, no one person can know every last detail of a twenty-million-line codebase; you're going to have to be willing to work on codebases you don't fully understand, and do the best you can with what you know. That doesn't mean people working on such a codebase are not "interested in learning everything they can about development", or not "caring about solving problems". However, there's a balance; you can't be so busy learning that you never take the time to apply what you've learned; knowledge.
You definitely shouldn't be focused on "getting as many lines of code out the door as [you] can"; if you think that's what your employer and co-workers expect, then either you aren't interpreting it correctly, or you need a new employer and co-workers. However, you should be focused on being as productive as you can. Develop a reputation as being the developer who almost always knows the answer to whatever crazy question their co-workers have, or who knows a little something about almost everything; those people are invaluable in an organization. And in the meantime, don't forget to actually write code.