I'm a big fan of this explanation/rant from Andrew Murphy.

[alanxoc3@tilde.zone]

@elizayer Very very true.

[kirakira@furry.engineer]

@elizayer i think about this. according to the promises, all the little snags and bugs and oversights in all the software i use should be gone by now. "everyone's focusing on bigger things" doesn't excuse it, i was given the expectation these types of fixes should have been trivial and quick. computing should be better than ever, or at least as good as it was in the 2010s

[niall@mastodon.nz]

@beep @elizayer well yes, it's clear you haven't listened to the episode

[nickrauchen@c.im]

@elizayer

"The Mythical Man Month"

The Mythical Man-Month - Wikipedia

(en.wikipedia.org)

[aeischeid@mastodon.social]

@mtnrbq65 @elizayer developers sometimes reference the 80/20 rule. And let's say in certain ways LLM code tools can get you through that 80% part faster, but they also have very real risk of making the last 20% even slower.

[wbftw@hachyderm.io]

@elizayer yes, this. Code creation hasn’t been an issue for a long, long, long time. See “no silver bullet” (https://worrydream.com/refs/Brooks_1986_-_No_Silver_Bullet.pdf) written in *1986*.

[standard_phil@infosec.exchange]

@elizayer I've listened to a few podcasts now where software company executives (and even a CEO, who I would have expected to know better because he's a CEO) have talked about how much faster their teams are producing code, and since their QA teams can't keep up they've fired those people and are using Claude for QA now.

I get that devs don't study management subjects (I was one myself, many years ago) so they won't necessarily know how to find and fix bottlenecks, but I'm genuinely disappointed that software industry executives don't realise they're in a manufacturing business, nor do they understand how to optimise their value chains.

I know it's a cliche to say that people fail upwards, and I've worked with many executives who were clearly in their roles because they were intelligent, educated, and were delivering at a strategic level - but I'm beginning to wonder if software businesses are a special case.

[guitarsith@fosstodon.org]

@elizayer
Almost all of the code written by the major software companies since the late 80’s has been bloatware. Especially operating systems. The days when programming was an art and minimizing resource usage was the primary consideration are long gone. If that code is what AI and these LLM’s are being “trained” on then expect software to continue its downward spiral.

[mjt@mastodon.online]

@elizayer This is a fabulously well-written article on flow, constraints, and fixing the biggest constraint first. Well worth nyour time if you do…well, anything.

[wila@mastodon.social]

@Aedius @elizayer there's just going to be less open source

[waldi@chaos.social]

@spazcosoft @elizayer Wasn't this always? Newly hyped stuff is used for scam, or porn, or both.

[aedius@lavraievie.social]

@wila @elizayer

All code is open source when you push it with a map file.

[wila@mastodon.social]

@Aedius @elizayer when it is javascript yes.
I wasn't talking about less slop.
There will be more of that.

[robtherunt@cupoftea.social]

@macronencer @mroach @elizayer
When I was working, I would regularly solve a development issue while in the shower. I think it’s the brain being unstressed that does that.

[ulveon@derg.social]

@elizayer@mastodon.social Claude Code found a 23-year-old Linux vulnerability, the kind a regular human security auditor would have taken weeks or months to find (or in this case, 23 years). https://mtlynch.io/claude-code-found-linux-vulnerability/

[mroach@ublog.mroach.com]

@robtherunt @macronencer @elizayer Same! I’ve half jokingly said my bathroom is the most productive room in my home office setup. Sitting on the toilet and lots of a-ha moments

[joeslow@me.dm]

@elizayer @trendytoots I can very much relate to this

[elrohir@mastodon.gal]

@elizayer management blame productivity for strategy failure because their approach to strategy path-finding is flooding: say a bunch of random hunches overconfidently, make teams try different things out for a little while, see what sticks. They see making code faster not as a way to manufacture a good design more efficiently, but as a means to generate management fuck ups and backpedals at faster pace and greater scale.

[nienkez@mastodon.nl]

@elizayer @ArtHarg AI only solves one problem: paying people wages.

[diekehrseite@mastodon.social]

@elizayer word!