3 ms·
Thirty years ago, I was thirty years closer to being a junior developer. That changes a lot of things. It makes it hard for me to judge. Back then, I got to
by AnimalMuppet 4y ago
Thirty years ago, I was thirty years closer to being a junior developer. That changes a lot of things. It makes it hard for me to judge.
Back then, I got to work on one thing, because one thing at a time was all that they expected of me. Now I get pulled in many directions at once, and it's really hard to focus on one thing. But that may not be so much because the processes changed, but because my role did.
Thirty years ago, the problems and projects were simpler, but the tools were worse. It kind of evened out.
I think the processes have gotten more complicated because the projects are more complicated. For the same complexity of project, I think the processes have often gotten simpler, because the stakes are smaller. You're building a web page front end for your ecommerce site? Your process is a lot lighter than when people were building NORAD air-defense systems, even if the complexity of both is about the same.
I still have the same limits I did. 100,000 lines of code is about all I can comfortably deal with; after that I start getting lost.
As I have gotten older (and I worked with older co-workers), the level of interpersonal maturity has gone up. That's been a good thing; both I and some others used to be jerks, and now we're not (or at least not as much). Again, though, that's just tracking with my age and seniority, not the industry as a whole.
- convolvatron 4y agoI kind of blanked that part out. yes its true. not so much in the 80s, but by the 90s it was quite common and expected that programmers were all self-important assholes competing for the title of alpha-asshole. glad that's finally gone.