I love Wube's FFFs. I wish more devs would do it; not just a devlog, but really going into the nitty-gritty of how some systems work.

>I always believe software wages shouldn't be more than a plumber or mechanic.

Wages in the trades have gone up a lot recently, at least where I'm from. Decades of parents telling their kids the trades are for losers lowering the supply of capable craftsmen...

And not all software will work as specialized tooling.

Calorie tracker apps? Sure.

Operating system kernels? Each with their own schedulers and allocators and ABIs and syscalls? Definitely not.

It's not just AI-generated, it's also slop!

>Use AI where it helps you and avoid where it doesn't

When all you've got is a hammer...

...you'll eventually stop knowing how to use other tools.

>Ever since LLMs started writing decent code, I started feeling like a part of that joy of code-writing has been taken away.

The SWEs that go all-in on AI will never understand this, because they have never enjoyed the joy of code-writing. I would even go as far as saying that many of them even hate it.

Of this group, I think the majority are the same people that have joined the industry not because of an innate love for engineering, but because they saw an opportunity to make big bucks in big tech.

>I think the antidote is ownership.

I've said this before, but people gloss over this fact.

>Someone with pride, drive, and a high standard feeling responsible for a particular area or thing.

I've also said this before, but AI-glazers just respond with "I think we may just have to let go of pride & kudos and their connection to our identity."

Most people who vibecode don't give a shit about their work. Any solution is a solution as long as it works.

>This might feel like gatekeeping, but it's the only way.

Gatekeeping is not inherently bad. We want gatekeeping.

If I'm getting surgery, I want an actual doctor with proven credentials to do it.

And to anyone claiming that software doesn't kill, please look up "Therac-25" or the 65 people that died due to Tesla's "Full Self-Driving".

Of course there are examples of software killing or being capable of killing (operating machinery or medical devices), but that doesn't apply to probably 90+% of software

Should've made my example a bit less extreme, but other forms of harm exist:

Downtime causing monetary damage (This one is obvious...)

Improper security measures causing leaks of customer data, making the victims a target for spam, or in extreme cases, identity theft, scams and (spear)phishing. One of the reasons why I am strongly opposed to having every random calorie counter app requiring you to sign up for an account asking you for your email and/or phone number.

I also recently saw a post here on HN about how VSCode had a bug that caused all commits to have a "Co-authored bv Copilot" line in the commit message, even if Copilot was disabled. One of the top replies mentioned how this could cause issues with employees working for companies that disallow the use of Copilot.

When you take these risks into account, I'm pretty sure you cover the vast majority of software.

>Many engineers are horrible at this and have no desires or ability to become a manager. This is why they went to engineering in the first place.

Bingo. If I wanted to spend my life managing incompetent sycophants, I would've studied for an MBA to try to rise the ranks at McKinsey.

Please verify that you are pushing to branch 'master' by saying "Doritos™ Dew™ it right!"

ERROR! Merge conflict. Please drink a verification can.

I used to work at a C# firm and we always called it "Microsoft Java", but that's such an insult. C# is way better, I've really enjoyed writing in it.

And it actually has pretty good interop with C++/CLI, too.

This has been attempted for as long as programming has existed.

Sure but now it actually works somewhat.