2,287 karma · joined October 3, 2024
What if the default chime triggers some PTSD? (Probably doesn’t, but it could happen!) What if the landlord doesn’t want you to drill a hole through the side of your house and it doesn’t come with a doorbell?
The solution isn’t “over engineered” it’s just “engineered” (not an off the shelf product)
For example, coral reefs provide protection and a vibrant home for a lot of sea life. But when the water gets a couple degrees too warm, it can essentially die, and when it does, the rest of the ecosystem disappears too.
Imagine if you were a human and your body temp was even a couple degrees above normal. You’d have a fever.
And these are only tiny examples… life finds away, but it also needs time to grow back.
For a woodworker, I think your analogy should be a “furniture factory,” not power tools. (Power tools in software would be like a great IDE and powerful language and framework tooling; AI is… way more than that.) I bet a “woodworker” in a furniture factory (if that even exists) doesn’t much care about their output, and doesn’t love the process anymore.
And getting paid for it doesn’t make you care about your work either, it just makes you care about money you can use on other things you do care about.
It would be foolish for anyone looking at the great change happening in software, and ignore the fact that we’re crossing a line where it’s less about craft, and where developers are just managing factory-like processes. Which is very different from what most signed up for.
And of course you can still do your craft, just like there are custom woodworkers as well as factories. But the space for that in AI-driven companies is vanishing as much as we might hate it or push back against it.
And of course there are also people like you who like the opportunity that more output provides, or who use it more like a tool and less like a factory. And that’s fine.
But no, the transition happening in the industry is not deliberately trying to keep the craft of it or even to keep developers interested in the job.
The transition is turning people who input stuff into a software factory and do QA on the output, or turning people into “factory automation engineers.” Those are both very different jobs from what people who like programming signed up for.
And yeah maybe no one “deserves” to have craft in their jobs. But let’s be honest, it is very natural, and very human, to be upset when the main motivation and reason for doing your work disappears. The same thing has happened in countless industries, and people have been talking about it for decades if not hundreds of years.
E.g. small-time farming replaced by exploitative big agriculture. A farmer might have a reason and identify in the work before, owning their own bit of land they tender. And now if they’re just hired to drive a tractor, they don’t. It’s a massive difference, and no wonder our society is increasingly depressed.
Configuration changes also change application behavior, otherwise is it really “config”?
What if they figured out what their platform can actually handle, provided the contractual level of service to their paying customers first, and put some god damn limits on usage.
Like they should just stop signups if they can’t handle the capacity yet. It’s a business decision, not a technical decision, to decide to screw over customers instead of adding limits based on your actual capacity.
In plain English, maybe it’d be more like “Package specifiers for git repositories should no longer include the HTTPS/SSH protocol. Instead, reference the repository name, and pnpm will resolve it through HTTPS. If SSH is still needed, add an override in your global git settings”
> Starting later this year, new Sign in with Apple addresses, previously issued on privaterelay.appleid.com, will be issued on private.icloud.com. Existing addresses on privaterelay.appleid.com will continue to work and forward mail to users without interruption.
For example, Walmart tried to invent their own mobile pay solution instead of Apple Pay when Apple Pay came out a decade + ago. They didn’t want to loose on the extra fees Apple charges.
Deploy to the staging cluster, have the LLM monitor with read access to the logs. Opus is… better than a human at looking at logs and comparing timings and checking for warnings and errors.
If it passes a small load test there, deploy to the live cluster and actively monitor. If it doesn’t fall over under load, is faster, is still correct, not throwing errors it works good enough.
Does much more matter? This produced a fairly large performance improvement. Verification in this case is the process of running it under load and double checking the code isn’t doing anything truly wacky.
User facing apps are harder to validate, sure, but you can easily have an LLM looping looking for errors, log issues, etc.
For home apps, this is more validation than you would have personally done
So even professional tools all follow industry design and product trends which are too simplistic, don’t give you the info you need, and are optimized for abstract brand design or chasing metrics for the company, and not optimized for “how do I let my user accomplish their task as fast as possible”
Why not just… a GUI framework or layout that’s meant to be keyboard driven and information dense?
Second, I found a product I liked but was the wrong size. As far as I could tell, they can’t even show you recommended similar products. They show you what other people clicked on or bought in the same order. But not just actually similar products in the same style.
1. People do not like email-based patch processes.
2. GitHub made everything dead simple, and free. Lots of Open Source projects have flourished because GitHub is both easy to use and makes collaboration across repository painless.
3. Very few people actually care about decentralization. As long as you have a full copy of your repo on your own machines as well as GH, it’s hard to argue you’re gaining anything with decentralization.
4. Most people also don’t want to self host a git server.