Live data from Hacker News

The next two years of software engineering

addyosmani.com

151–160 of 403 posts

Re: The next two years of software engineering

#151

> Senior developers: Fewer juniors means more grunt work landing on your plate I'm not sure I agree with that. Right now as a senior my task involves reviewing code from juniors; replace juniors with AI and it means reviewing code from AI. More or less the same thing.

> More or less the same thing. Worse. The AI doesn't share any responsibility.

And can’t be mentored by the senior except in some ersatz flat text instruction files.

Re: The next two years of software engineering

#152

Earlier quoted context omitted.

I don't think that works. The fact that it can produce different output for the same input, usage of tools etc. don't really fit into the analogy or mental model. What has worked for me is treating it like an enthusiastic intern with his foot always on the accelerator pedal. I need to steer and manage the brakes otherwise, it'll code itself off a cliff and take my software with it. The most workable thing is a pair p…

I feel like some of the frontier models are approaching run-of-the-mill engineer who does dumb stuff frequently. That said, with appropriate harnessing, it’s more like go-karts on a track; you can’t keep them out of the wall, but you can reset them and get them back on a path (when needed). Not every kart ends up in the wall, but all of them want to go fast, so the better defined the track is the more likely the kart…

I don't really know if I agree with you but the analogy is really good. :)

Re: The next two years of software engineering

#153
post #75

Earlier quoted context omitted.

Please don’t get my hopes up. Adaptable people like me will outcompete hard in the post-engineering world. Alas, I don’t believe it’s coming. The tech just doesn’t seem to have what it takes to do the job.

Some related fields will be gone too. And the jobs which will remain will be impossible to get.

> And the jobs which will remain will be impossible to get.

Exactly my thoughts lately ... Even by yesterday's standards it was already very difficult to land a job and, by tomorrow's standards, it appears as if only the very best of the best will be able to keep their jobs and the ones in a position of decision making power.

Re: The next two years of software engineering

#154

Earlier quoted context omitted.

Generally the demand for software engineers has increased as their productivity has increased, looking back over the past few decades. There seems to be effectively infinite demand for software from consumers and enterprises so the cheaper it gets the more they buy. If we doubled agricultural productivity globally we'd need to have fewer farmers because there's no way we can all eat twice as much food. But we can abs…

> Generally the demand for software engineers has increased as their productivity has increased, looking back over the past few decades. There seems to be effectively infinite demand for software from consumers and enterprises so the cheaper it gets the more they buy. I see this fallacy all the time but I don't know if there is a name for it. I mean, we make used fun of MBAs for saying the same thing, but now we shou…

Jevons paradox and it’s not a fallacy. It’s an observable behavior. The problem is it’s not predictive.

Re: The next two years of software engineering

#155

> Senior developers: Fewer juniors means more grunt work landing on your plate I'm not sure I agree with that. Right now as a senior my task involves reviewing code from juniors; replace juniors with AI and it means reviewing code from AI. More or less the same thing.

The juniors get better and closer to the ideal that my team requires via this process. Current AIs don’t, not the same way.

Re: The next two years of software engineering

#156

>The flip scenario: AI unlocks massive demand for developers across every industry, not just tech. Healthcare, agriculture, manufacturing, and finance all start embedding software and automation. I find this one hard to believe. Software is already massively present in all these industries and has already replaced jobs. The last step is complete automation (ie drone tractors that can load up at a hub, go to the field…

I think there's a good chance demand goes up in Europe. We are going to need to de-risk our software dependencies, and Germany is going to need to use computers. Germany is going to be crazy, I think.

Germans were so quick to revert back to paper after COVID that it felt like one of the only reasons they came out of lockdown eventually was to get paper back.

The Gewerkschaft tactics to resist AI is what I’m really interested in seeing.

Re: The next two years of software engineering

#157
post #148
post #121

Earlier quoted context omitted.

Does Linus Torvalds count?

When has he stated that he uses AI like that? The last I heard about him a month ago, he specifically stated that he was not interested in AI to write code: https://www.zdnet.com/article/linus-torvalds-ai-tool-maintai...

3 days ago: https://github.com/torvalds/AudioNoise/blob/main/README.md

> Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters -- and that's not saying much -- than I do about python. It started out as my typical "google and do the monkey-see-monkey-do" kind of programming, but then I cut out the middle-man -- me -- and just used Google Antigravity to do the audio sample visualizer.

Re: The next two years of software engineering

#158

Earlier quoted context omitted.

> Generally the demand for software engineers has increased as their productivity has increased, looking back over the past few decades. There seems to be effectively infinite demand for software from consumers and enterprises so the cheaper it gets the more they buy. I see this fallacy all the time but I don't know if there is a name for it. I mean, we make used fun of MBAs for saying the same thing, but now we shou…

Jevons paradox and it’s not a fallacy. It’s an observable behavior. The problem is it’s not predictive.

> Jevons paradox and it’s not a fallacy. It’s an observable behavior. The problem is it’s not predictive.

I was referring specifically to this point, which, IMHO, is a fallacy:

>>> There seems to be effectively infinite demand for software from consumers and enterprises so the cheaper it gets the more they buy.

There is no way to use the word "infinite" in this context, even if qualified, that is representative of reality.

Re: The next two years of software engineering

#159

Earlier quoted context omitted.

> More or less the same thing. Worse. The AI doesn't share any responsibility.

And can’t be mentored by the senior except in some ersatz flat text instruction files.

And the mistakes AI makes don't carry the same code smells juniors make. There are markers in human code that signals how well they understood the problem, AI code more often looks correct at a glance even if it's horribly problematic.

Re: The next two years of software engineering

#160

Earlier quoted context omitted.

What I want is for universities to offer a degree in Software Engineering. That's a different field from Computer Science. You say that belongs in a trade school? I might agree, if you think trade schools and not universities should teach electrical engineering, mechanical engineering, and chemical engineering. But if chemical engineering belongs at a university, so does software engineering.

Saying this as a software engineer that has a degree in electrical engineering - software "engineering" is definitely not the same as other engineering disciplines and definitely belongs in a trade school.

Right, because the guy sitting next to me and is designing a PCB for next copy of rPI is so much more for an engineer than the other guy designing a distributed computing algorithm? It shows that you only dealt with the trivial things in SE. There are very complex areas in both disciplines and as much as I can find trivial things in SE I can do the same for EE. Let's just not pretend it's a science fiction when it's not.
Post reply on HN