The smaller the org, the better the chances of having only reasonable levels of misalignment... but without taking on high risk, it's just better pat to work on a large, worse org. Frustrating.
If you're making a Linux distro, please don't do this. I will not watch your video. I was interested, and now I'm not.
What is "a fascist" (in context of being labelled that on the interwebs). That could mean a lot of things.
As a reader, you learn basically nothing about DHH other than that some people might not like him.
___
So to fix that:
DHH has always been a very opinionated guy - with not all of those being agreed on, but there being usually some kind of point to them.
Starting somewhere late-ish last year, however, he seems to have dropped deep through the alt-right pipeline and started babbling talking points basically copy-pasted as-is from other talking heads.
So, in essence, he kinda stopped being opinionated, because that would require having an own opinion, and instead started just being yet another person not doing all too well mentally on the internet.
I mean the guy suddenly started talking about "body counts". What's his age again?
__
Of course, moral outrage happened but achieved absolutely nothing, because it's not the right tool for the job here.
Fascist is not just a silly label. The political collapse of neoliberalism made a lot of closet fascists emerge and they seem quite common among what was earlier thought of as "techno libertarians". E.g. the VPN provider owner (forgot which) just lately.
If there was too much crying wolf 15 years ago, doesn't really matter now anyways.
Imo we know the tools (social, + technical) to make good software that works. But in the face of massive complexity, people just want the next feature, the next thing sales can use as a win
And yeah I agree with the other commenter here - I don't think this is AI. We had terrible software before, even declining quality.
I work in mediation and have recently seen a few cases where I’ve wondered if the participants were suffering from AI psychosis as related to their claims: where they’d constructed their legal cases hand-in-hand with an LLM and had become absolutely convinced despite a contestable set of facts.
People have always been subject to delusion, but in these cases, all documentation submitted was obviously created by chatbots.
It's glaringly obvious that poorly checked, AI-written, code is the culprit, I'm just wondering when companies will wake up.
Nobody gives a flying fuck about resiliency, good practices, security or any of that now that AI is there. All anyone cares about is pure output of features.
Any and all "productivity" gains attributed to AI efficiency are actually due to the complete disregard for any care or standard in the software industry in the past 2 years. Yeah you can output more shit when you don't give a fuck, big surprise, AI doesn't change anything here.
Optimistically, I think we might just enter a new phase at some point, where businesses make very conscious decisions about what to invest in to differentiate. Like, everyone has support bots now. Where do we invest, absolutely stunning human support? Or is support not that key and we should invest into being the most reliable? The most enjoyable to use?
One can hope.
That's a complete non-starter unless you're serving some extreme luxury premium market with absurd margins, and/or your customer interactions already require a lot of human involvement. So 99.9% of digital products are right out.
Good human support is absurdly expensive and will easily make your product 10 times more expensive than your competitor's. But almost no customer is willing to pay 10 times more for good support.
So taking it at face value is kinda part of the problem here.
The only way this can get better is by completely suffocating it off attention. It doesn't exist. It's not real.
My experiences as a user haven't really changed. Streamers fail to cast to TVs. Browsers are devices which reliably and efficiently propagate red console text and 500s from companies to you. I still see bluescreens on public touchscreens.
Uncle Bob nailed one reason why the industry isn't getting better: the growth of programmers is exponential, such that half of all programmers have less than n years experience (5?).
I offer two additional reasons:
Firstly, you hone your skills doing individual algorithms on a single thread, where it's OK to get it wrong and change it as many times as you like.
When you get a job, you don't even realise you're in a distributed system and the getter/setter model you practiced on is woefully inadequate for interacting with partner systems, cqrs, event-sourcing, auditability, idempotency or whatever else is required.
In short, 10 years of practicing writing for-loops and data-structures will not translate into building a system that customers can access via their phone and multiple tabs of a browser, at the same time as a database schema is being updated.
Secondly, while I don't think there is any realistic alternative to agile development, it seems that nontechnical POs have captured the software lifecycle. 'Focus on happy path only, for the MVP' is how you build buggy software. Good developers can learn that this will guarantee the need for a rewrite in the future, but POs never will.
It seems like the languages have been increasingly targeting the beginner segment (C++ -> Java -> JS -> Python), while the tasks have been getting more complicated (b2b distributed systems, 24/7 uptime, millions of users, resistance to hackers, machine learning, etc.)
I don't necessarily believe in 10x devs, but there is a very clear output difference between various developers. During my career I've been both in a position where I was delivering much higher quality code at a similar pace to other coworkers and also mediocre code at a slower pace. Sometimes at the same time.
Now, AI itself is a force multiplier. Depending on the task, your setup, your skill level (both as a developer and with LLMs), the weather, the model and so on, it can range anywhere from actively hindering you, to solving the entire thing for you. Let's say that on average you get a 20% productivity boost.
If you take a 0.8x developer and give them a 1.2 force multiplier LLM, you get a 0.96x developer. Worse, the axis that has moved is speed, not quality.
All this to say that if you let a below average developer vibecode, you get a much higher volume of slop. You can make an agent create good code, but this developer didn't care before so why should they now?
*Note that this is from experience. I've started getting feature PRs from our devops team. It's been a very enlightening experience.
Microsoft didn't need AI to make windows 11 as bad as it is.
The incentives are large companies are fundamentally not in align with making high quality software people actually enjoy interacting with.
This is hilarious.
I still don't understand how a full focus stealability debounce is not the norm. If I am in the middle of writing, or interacting with one UI bit in any way, no other app should be able to steal focus, full stop. Add an annoying popup if you want, make angry computer noises, flash icons, I don't care. 99.9, if not 100% of the time, it's completely unrelated to what I'm doing and can absolutely wait. While some OSs have something along these lines, they also give the tools to bypass it (I'm looking at you, Cisco VPN! Being connected after clicking on connect is not an emergency notification!)
Imagine you're working in a terminal and an app decides to steal STDIN. Why do we accept that for a GUI?
Now with AI new superior people can actually produce compilable code, and ship it to production!
One of my absolute favourite features on KDE Plasma with Wayland is the global setting to control what can steal focus. It works wonderfully, and I always miss it when I have to use my work mac or windows computers.
See here for docs, under "Focus stealing prevention" - https://docs.kde.org/trunk_kf6/en/kwin/kcontrol/windowbehavi...
I think that points do the solution. We should not make stuff more complex than we can the level of complexity at which we can make it reliable.
The issue is only partially within those who code. They get directions from those in charge, and they are just making idiotic decisions. And those who code, for some reason don't stand against those idiotic decisions in defense of a common sense and a great UX.
A blatant, exaggerated parallel would be: you are designing your kitchen and you've chosen a place for your washing machine such as that it will be unable to open its door. When inviting a professional, you expect them to correct such wrong decisions and explain to you that it won't work. But in programming, those who program, calling themselves "software engineers", would just place this washing machine where they're told, because it's "not my job". It's not a feature of an "engineer". It's being a coder lemming.
I guess so, but that's abstract and hard to grasp for most people.
"The guy has clearly lost it and thus is probably not making sensible decisions" otoh is pretty easy to understand, signals effectively the same and side-steps basically all the drama.
It is really hard to keep your cool.
I do not disagree with what your said, but I think it just boils down to that.
Sorry to say, but that word probably has an equally low impact on regular people by now. Worse if we look at what people actually think/vote/etc.
People by now at large seem to be rather fine with both being called racist or just.. well.. being racist.
We do not actually want that, because (big surprise upcoming) racism is bad. But I think we might need to remind people why that whole cluster of ideas is bad.
This shouldn't be too hard, given that it's objectively worse in many many aspects, but for that to be seen, I suppose we need to point out what makes it objectively worse.
The shorthand is unfortunately dead and got killed by twitter dot com.
__
How that could be done is how I've demonstrated before you've regrettably dismissed it and tried returning to the shorthand
A month later, no refund. I contacted them again, they said unless the book is sent back, no refund. I told them about the previous conversation and they said that the CSR had lied to inflate his scores, and if I've thrown the book away I'm out of luck, he generated a return label. I complained and they threatened to close my account unless I send verification documents. I didn't, I just sent the book back and the refund processed automatically.
About a year before that I had a Samsung Fold and it cracked down the middle. I told Amazon that it was only 6 months old and it was broken, and Samsung said I need to send it to Cyprus for some reason. Amazon said to send it back for a refund, I did, and I got a warning that I'd returned something "not in original condition" and next time I'll be banned.
Last week a package didn't arrive. I queried it and there was no longer the option to talk to anyone, just a link to phone numbers for the external courier.
So I would say that Amazon having stellar support 15 years ago, building a brand on it, and then choosing to stop doing that mostly proves how wrong you are. Sure, you can still sometimes speak to someone, but it's getting worse.
If you create a startup you really want to focus on a small audience that you understand and know really well, instead of chasing everyone. And for that a support team is one of the most important asset you have
And bring back change & configuration management processes and documentation reviews. All the boring slow stuff.
Except now make it part of your CI/CD pipeline.
Bizarre experience.
AussieWog93•59m ago
rightbyte•54m ago
Running non free software is essentially giving up our freedom. Before internet connectivity the problem wasn't too bad but nowadays there is always the temptation to squeeze the lusers.