[stavarotti]

> On novel work:

> Work that introduces new methods, highly creative ideas, or solutions that have not been used or experienced before. More generally, an approach that introduces an innovative strategy to solve a complex problem.

Something that I've been thinking about for the past year or so is coming to grips with the fact that the vast majority (anecdote) of software engineering work is not novel (and maybe that's okay). Few opportunities lend themselves to doing truly novel work. Other than infrastructure work and highly specialized software, pause and ask yourself when you last encountered software were you said "how the hell did they do that?" or "damn, that's nice" (for me, the most recent was Ghostty). I think much of the angst that people have when they fear for their job is coming to the realization that LLMs can do most of the "standard" work that a lot of highly compensated individuals currently do. We've built livelihoods around this and the threat of that coming to an end is genuinely frightening.

[thunky]

> I think much of the angst that people have when they fear for their job is coming to the realization that LLMs can do most of the "standard" work that a lot of highly compensated individuals currently do.

Amd do it better in most cases imo. Which is also hard to come to terms with, because there is a good bit of elitism/entitlement going around. The idea that a SWE is working at a higher level, which is beyond the reach of mere mortals, so therefore the high compensation is justified. Meanwhile everyone is, for the most part, doing some slight variation of the same thing as you suggested.

After starting out working minimum wage jobs I've always thought that the work gets easier and easier from there. Compensation and hard work are negativity correlated.

[manoji]

This is spot on ! Most of the work we really do is pure boilerplate and should be automated. While there are instances of interesting work those are far and few in between . The most recent instance of "how the hell did they do that?" for me was duckdb.

[casey2]

All public school students in the US at least are taught how to do basic scientific research. They should be making novel discoveries every day. The only thing that stopping them now is their own laziness.

[rfgplk]

> Something that I've been thinking about for the past year or so is coming to grips with the fact that the vast majority (anecdote) of software engineering work is not novel (and maybe that's okay)

Correction, essentially 0% of software is novel. Git wasn't novel. Chromium wasn't novel. Linux wasn't novel. Even C when it came out wasn't novel. Likewise Unix. They're all permutations of either prior knowledge, or evolutions of already existing concepts. They only might _appear_ novel to people who lack the depth to see what technology really is. Effectively applied physics (which has been solved for... over a few centuries at this point?) which itself is applied mathematics. There is novely to be found in physics and math themselves, but it's far out of scope of practical engineering.

[hackingonempty]

> pause and ask yourself when you last encountered software were you said "how the hell did they do that?"

Like every month for the past 5 years? The progress in machine learning is dizzying. It is astonishing what can be done now with text, images, audio, video, code, etc...

If you don't study it, however, you have no idea how it works or how to do it yourself.

oblig. xkcd https://xkcd.com/1425/