> I just don’t look back [at school] and think “wow, there was a lot of wasted time there” I can’t edit that post, but I want to add... I DO look back the maj

> I just don’t look back [at school] and think “wow, there was a lot of wasted time there” I can’t edit that post, but I want to add... I DO look back the majority of coding jobs I’ve had in the Bay Area, and do very much think “wow, there’s a lot of wasted time there.” Half or more of my time as a pro coder is spent undoing work I just did because the task wasn’t specced correctly, deciphering someone else’s bug because they merged it and left the office, dealing with the same broken infrastructure over and over because new features are always more important, building something that some Dir. Eng. wants, but is totally unproven and won’t matter to any metrics, etc. I’m not passing the buck here, one of the main goals of my career is to become a better countervailing force to that stuff. But I want to highlight that making it into the workforce doesn’t mean you’re automatically spending all your time doing “real work”... sometimes it’s just the opposite.