3 ms·
I doubt this was ever a thing at all. I think the author falls to the common nostalgia trap of an imagined "perfect" past that has degraded somehow. It's a trap
by unscaled 2y ago
I doubt this was ever a thing at all. I think the author falls to the common nostalgia trap of an imagined "perfect" past that has degraded somehow. It's a trap all human beings easily fall into, so I wouldn't blame him, but I fail to remember any such period from my career or older historical accounts that titles were reliably and consistently meaningful across the industry.
The moment you've got more than a handful of companies doing software, each company will do its own thing with the titles it gives — and there are few incentives (if any) to heavily gatekeep titles with a complex and hard-to-implement certification process. And if a company does end up implementing some sort of certification anyway, it would be specific for that particular company and not something that's relevant for the entire industry.
I would even argue that's not just the case for software, but for any industry that is not regulated by the state or by a mandatory certifying body such as law, accounting and medicine — and even in those industries, the standardized certificates you get are generally limited to a fairly entry level.
The only imagined past where career progression was strongly regulated that I can think of is European Professional guilds in the late Middle Ages through the Early Modern period, where you'd often apprentice for 7 years or so before attaining the title of Journeyman, and then you would have to wait anything between 10 to 20 years to never (the most common result) before you obtain the necessary funds and approval to become a master and practice on your own. I'm not sure there is any point going back to THAT system.
- gregjor 2y agoThe guild system lives on in a way in the skilled trades. An electrician or plumber goes through specific career stages. My son apprenticed learning how to make beer. It also lives on in the military. I think programming would benefit from an apprenticeship stage -- I had great mentors assigned to me early in my career but that seems to have gone away. The meritocratic nature of programming attracted me to it (as a young nerd with an incomplete degree in military history). If you could do the work you got paid and promoted, and companies would put in the effort to train and mentor juniors back in the day (or maybe I got lucky and feel nostalgic for an imaginary past). I saw the credential craze come and then mostly fade away (I got Oracle, Novell, and DEC certifications). Now I see companies insisting on CS degrees. My early programming heroes didn't seem to use titles -- Dennis Ritchie, Ken Thompson, Brian Kernighan. I suppose Bell Labs gave them titles but when I read their papers they just used their names. Rob Pike calls himself a programmer -- when he presented Go at OSCON a long time ago he introduced himself as a "programmer at Google." Maybe a humblebrag, but if you can walk the walk you don't need to show off with a fancy title. I think we shouldn't get hung up on titles, or use them to gatekeep or judge.
- anotherhue 2y agoI once saw Berners-Lee introduced as 'Web developer'.