So what's the moneyline on all these outages being the result of vibe-coded LLM-as-software-engineer/LLM-as-platform-engineer executive cost cutting mandates?
Even if they were being hypocritical, I think the impact of briefly-bad UI on someone's blog post pales in comparison with bad UI in a product of macOS scale.
I don't know, I figure with a billion dollars Apple should be able to do much better at being awful than this. More proactive rather than accidental awfulness. Something that isn't just bad but capital intensive at the same time. Anyone can build a bad UX on a few menus, or a whole system incrementally over time. But to really lean in? Maybe commission famous artists with eye watering fees for each icon, truly over the top marketing campaigns, really get the cash-fired furnaces going. Really just go full-potlatch on things.
I've used macOS for development for 15+ years now but always built my gaming rigs using Windows. For the first time in my life I'm so annoyed with Windows I'm seriously entertaining the idea of putting SteamOS on my rig and fighting my way through whatever nonsense I have to to make it work. I was able to tolerate a lot of Microsoft's nonsense so I could have a very easy path to just turn my machine on and play some games without having to think too much about it but my patience is finally at an end.
The content of the document matters too. I don't really care if someone was AI-assisted writing a project plan. As long as it's sane and clear I'm not gonna lose sleep over that. However for my performance review I definitely want my manager to put in the effort and actually tell me nuanced thoughts on my performance. I don't want AI output for that part.
Wait until you find out that most managers write feedback using copy/paste boilerplate with maybe a few tweaks to personalize it. And this was happening long before LLMs.
Oh I'm well aware. When I was an EM for a bit last year a bunch of colleagues told me they used ChatGPT to write their reviews. It was gross and I always hand crafted, small batch artisanal reviews when I'm in the managers chair.
Who is "they" and where is the proof there was widespread "system abuse" that warrants voluntarily abdicating any lead we have in research to other countries?
Individuals are rarely (not never, but rarely) the full problem. Groups of people are what cause feedback loops and cultural reinforcement like the author describes. Sometimes this is a virtuous reinforcement cycle but more often than not the well gets poisoned over time.
> "Go is often touted for its ease to write highly concurrent programs. However, it is also mind-boggling how many ways Go happily gives us developers to shoot ourselves in the foot."
In my career I've found that if languages don't allow developers to shoot themselves (and everyone else) in the foot they're labelled toy languages or at the very least "too restrictive". But the moment you're given real power someone pulls the metaphorical trigger, blows their metaphorical foot off and then starts writing blog posts about how dangerous it is.
Though a good language would point out that what the junior (or in some cases even senior) dev is holding in their hand is in fact a gun and not a gun disguised and marketed as this nice and easy to use toy, which is especially true for Go.
One must keep in mind that devs manage to implement even flawed logic that is directly reflected by the code. I'd rather not give them a non-thread safe language that provides a two letter keyword to start a concurrent thread in the same address space. Insane language design.
reply