[netdevnet]

Not sure if comparing salary potentials coming from two different socio-economic periods is useful or likely to mislead.

Tech and people versed in it were not common (to people outside tech) and so the high salaries would reflect that. Now is not the case. It was always going to be temporary. As people become acquainted with tech people, the magic vanishes, you see the code behind the pixels. At the same time, tech people themselves did cause this by making tech easier to understand and manipulate.

It's like a magician, the first few times, it is enticing and mysterious but after a while it becomes ordinary. Tech wizards are just like that.

[busterarm]

People with wizard-like skills are out there but typically can't command the salaries they used to.

Todays SWEs tend to know far less about how computers operate and how protocols work than in the old days.

[netdevnet]

The reality is that thanks to those tech wizards, most companies don't need tech wizards to build tech products and most tech workers don't need to know anywhere near as much as you would need to back in the days.

The same kind of "I just love to code" tech wizard that builds an amazing service/library/product, overworks itself while letting big companies extract max value out of it and contribute nothing or extremely little to the open source world.

Every day I think of the Homebrew creator who got rejected by the company that uses his software daily. This should be in the mind of every dev imo.

Tech wizards wrote their fate on code, compiled it and served it to the market. This is the result

[randomdata]

> Every day I think of the Homebrew creator who got rejected by the company that uses his software daily. This should be in the mind of every dev imo.

To be fair, he does not come across as the kind of person you would want to work with, no matter what kind of software he is able to produce. Once hired, others actually have to work with him in such companies. In fact, Apple did end up hiring him soon after said rejection but quickly determined he wasn't a good fit there either. No wizard is worth having by your side if they make your life miserable.

[shiroiushi]

How bad could he have been? According to the parent, his software is used daily by that company. At the very least, they could have just hired him full-time and then stuck him in a remote cubicle by himself, reporting to one manager who just keeps tabs on him, and told him to basically just keep working on that, and if he has spare time, think of other convenient projects to work on that customers might like.

[randomdata]

Perhaps they could have, but why? What would be gained in hiring him to sit there and do nothing just because in the past he wrote some code that a company happened to find useful?

[shiroiushi]

I thought the consensus was that he was extremely skilled, and he's obviously proven himself at making very useful tools for that system. Why not hire such talent and put it to some use? Not all positions need to have a lot of team interaction.

[kortilla]

>Every day I think of the Homebrew creator who got rejected by the company that uses his software daily.

Why does this surprise you? Google didn’t even employ the chefs that made the food consumed by the employees daily either.

Just because you made a thing that was useful doesn’t mean you have the skills that Google is looking for.

Homebrew was very useful because Mac osx didn’t have a good package ecosystem for one-liner installs. The tech behind it though wasn’t particularly unique or groundbreaking. So the author’s skill here was finding a market with unmet demand for a free package manager. That’s not what Google was looking for.

[listenallyall]

Identifying unmet demand is probably the most valuable skill any Googler can have, it already has enormous engineering talent. It's the difference between GMail or Android (or Search, obv), vs throwing away hundreds of millions on Google Glass or Google+

[kortilla]

Engineers don’t pick products anymore. That died a long time ago

[listenallyall]

Kind of the point - the engineers rejected the guy because (in their perception) he wasn't good enough at leetcode or some esoteric language feature or whatever - meanwhile they were blind to the fact that he possessed a skill that was far more valuable to the company, which they themselves had no ability to recognize or evaluate.

[busterarm]

Yeah most of Google's successful products are acquisitions, not homegrown.