I noticed that is quite hard to make people change habits regarding software. There is shortcuts to learn and we might feel slow at first which reinforces the feeling of « it’s not better ». It takes a while to get used to nvim, once there it’s faster but that explain why many people stay in their confort zone
One of the most important things I've ever read as someone that wants to be able to break out of my comfort zone was from Uiua's website. Foreign != confusing
I agree, search in ClickUp is awful and it’s impossible to find back old cards from previous years. A nightmare. Plus, if consumes gb of memory in the browser.
That’s exactly part of the feelings I have. I always loved to learn, dig subjects, debug, create. Now I feel something has been taken away and has no value. I feel indolence and apathy. In my company the CEO explicitly says that code quality does not matter. He doesn’t care as long as we ship fast and iterate.
I am genuinely sad and feel I’m losing something and if I do everything like I used to do, I am pressured that I waste time.
I'm in a similar boat. Today I commented on a junior developer's pull request, and he pasted the answer he got from Claude Code, verbatim.
Ignoring how disrespectful that behaviour is, I can't understand what value he thinks he brings in. Were you hired to be an interface between me and Claude? Because I don't need you. You are just accepting that you are redundant by doing that.
> Now I feel something has been taken away and has no value.
Did you feel similar when Wikipedia was created or Google or when you first got access to the internet?
All of these tools have made digging into subjects and learning easier. I find the same with AI. I love it when a random thought pops into my head and I can explore it with an AI such as Gemini. Then ask it for the sources it used so that I can read further.
AI is just a tool, much like StackOverflow. It doesn't prevent creativity, it just makes it easier and more accessible.
> The moment you start working on something, someone else is already automating the exact thing you are doing now.
Good. If a machine can do my job then I can work on something more interesting. Perhaps a more interesting problem to fix is having the people working on something getting told about the automation.
I recently at around 42yo learned how to darn/mend my socks. My mom taught me how to do it.
I have enough money that I could just throw my socks with holes to throw trash and buy new ones inconsequentialy, but mending them by hand gives me something, it is kind of therapeutic and a sense of accomplishment.
Im sure there are machines that could do it in a second, or a patch I could stick on it as well.
Point being that we can still find satisfaction in doing things by hand that technology can do fast/easily. We just stop doing it by hand for profit.
>Much of modern life is automating away the boring useless bits.
>AI, on the other hand, changes the conversation on what’s boring or useless.
A compression algorithm finds and removes redundancy. Simple automation is like simple compression algorithms (RLE like). AI (which even internally - at least the encoding to the representation parts - looks like compression) just like a much more sophisticated compression algorithm which finds and removes redundancy where we thought the creativity and originality were.
It does look like our civilization has accumulated a lot of cruft masquerading as creative/original/intellectual activities ("Bullshit jobs" comes to mind, also all that talk about stagnation in science, and all those huge collective collaborations - where collective there is a stagnation - and now with AI individual scientists will again be able to wield all the bleeding edge across the wide fields while digging deep in desired target research direction), and the AI is the vacuum cleaner for that cruft.
I feel the same as you. But at the same time: do you not think your CEO will be proven wrong? Maybe I'm delusional, maybe I'm just rationalizing, but surely code quality, and code understanding, does matter?
And if your CEO is right, then surely their business is doomed? If they don't understand, or can't maintain their own product, what's to stop their customers from just "making it" themselves?
I’m in a similar line of thinking and actually some customers are making their own version of our tool. It’s nowhere near feature complete but it suits their needs.
Code quality does matter it’s just marketing people being shortsighted because their job is to react to the market. LLM gives a sense of « it’s kind of easy to build stuff, why bother loosing time with quality when I’m there at 80% in 20% of the time ? ».
There is compounding effects where given any big enough system this won’t scale, even Google did talks this week on this topic. So I guess you’re right, time will prove who’s right or wrong and what bet was the best with which consequence
They matter, but you can't argue that human written quality code that strokes the developer's ego is so much better than AI written code of slightly less quality. Understanding also matters, but now you're trying to familiarize yourself with the AI's code, not your colleagues' code and never the code you've written yourself.
It’s a fragile equilibrium and it depends on the kind of project you’re working on. If the knowledge debt is ok then yes, it’s just like a delivery job, if the truck has an engine problem I won’t continue to deliver the packages by walking or finding and setting up an other truck from where the vehicle breakdown happens. I’ll just wait because the wait is still faster than the other solution because of the knowledge debt it’s too long to pickup by hand and continue.
Now if it’s my job then I can’t have a knowledge debt and if Claude is down I’ll continue working manually because I know and understand and can continue without having to understand a lot of logic before continuing
> It’s not lying. It’s not even wrong, necessarily. It’s just incapable of the thing that makes a real architect valuable: saying “no.”
In my workflows Claude does pushbacks all the time and justifies why. There is back and forth just like a colleague. It’s not perfect but the results are usually good
I thought the same and it depends on which context you work.
Below is an answer on slack from our CEO when I said talking about Claude code source leak : « Dirty, un-architected code is the new norm; it makes billions, who cares… »
He answered:
> Well, yeah, who cares?
> This is where we need to differentiate between what truly needs to be clean (critical APIs) and where some random guy coding a product in a week will wipe the floor with a team of engineers with a clean architecture and no product after three months.
> What's more, this "vibe coder" is on the right side of history… Who's to say AI won't be able to just rewrite the code cleanly while keeping the core idea within 6, 12, or 18 months?
> This is also the question that drives business... and in business, "good enough" has almost always trumped "perfect." Except when you're making an ultra-luxury product like a Ferrari or something. Which software almost never is (if ever).
So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
> Who's to say AI won't be able to just rewrite the code cleanly while keeping the core idea within 6, 12, or 18 months?
Well lets say it's 18 months from now and AI writes lovely, ideal code. At that moment, the AI would have eliminated the need for AI, right? If the code is good, you can just read it and edit it.
The selling point of AI is that you will embrace that idea that you code is a mile-high stinking garbage heap, so that any human would be overwhelmed by the stench. Only so long as the best strategy for engineering is to pile the garbage as high as possible as fast as possible will the best tool for engineering be AI.
So my counter argument is: just wait 18 months and you can completely skip adopting AI.
> So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
This is especially true when the people who suffer the consequences of bad software are far removed from the company making it. You'll be forced to spend hours fighting with customer service over errors made by people using that bad software, but it won't impact the CEO of the company who vibe coded it. I hate that we're moving to a world where everything around is getting worse and less reliable while marketing companies try to convince us all that this is somehow progress.
I agree it works nicely for me.
From my experience it’s not realistic to expect one-shot each time. But asking it to build chunks and entering a review cycle with nudging works well. Once I changed my mindset from it « didn’t do a one-shot so it’s crap » and took it as an iterative tool that build pieces that I assemble it’s been working nicely without external frameworks or anything. Plan-review, iterate, split, build, review iterate
Very nice insight, that’s where the value is, even with a lot of time refactoring, testing and reviewing the compressed code phase is so much gziped than it’s still worth it to use an imperfect LLM. Even with humans we have all those post phases so great structure around the code generation leads to a lot of gains.
It depends on industries and what’s being developed for sure
reply