4 ms·
All of this is clearly a matter of balance. If you were to have infinite time, you would be idiotic to _not_ spend a bunch of time fully internalizing the enti
by esotericn 7y ago
All of this is clearly a matter of balance.
If you were to have infinite time, you would be idiotic to _not_ spend a bunch of time fully internalizing the entire stack; or at least, trying to comprehend as much as possible given your non-infinite memory. Hell, whilst you're at it, throw in a rounded education in the humanities and sprinkle a ton of socialization in there too.
But you don't have infinite time. So instead, you try to find the balance that allows you to perform the task you wish to perform.
And at that point it's a completely personal decision. Perhaps you spend more on soft skills because you have managerial aspirations. Perhaps you drill down into bit banging simply because it's of intrinsic interest to you.
There probably is some basic level that's useful for every programmer to have, sure, but what that even means is dependent on sector. I don't know a thing* about Windows because it's both highly uninteresting to me, but also because it'd be a waste of time for me to bother with it. (Perhaps the two are linked!)
* okay, I know a decent amount compared to the man on the Clapham omnibus, but not compared to a Windows developer
- Pigo 7y agoI like to roam around the projects I use the most on Github and see if there's a bug I can work on, or someway to help out, when I have the time. It took me too long to realize that I could help open source projects out without being the chief architect at Microsoft, or have a well established coding blog, etc...
- bcruddy 7y agoI love the infinite time explanation. It's a great way to explain how/why tradeoffs are made. I haven't been able to put it so succinctly, so, uhhh... that's mine now I'm stealing it. Please credit me in your original post.
- darepublic 7y agoIf I had infinite time I would procrastinate a lot more