You get over it really quickly once you start actually using it. I find it basically impossible to read Clojure outside the editor in any meaningful sense.
The tools produce mediocre, usually working in the most technical sense of the word, and most developers are pretty shit at writing code that doesn't suck (myself included).
I think it's safe to say that people singularly focused on the business value of software are going to produce acceptable slop with AI.
I've always heard this sentiment, but I've also never met one of these newly skilled job applicants who could do anything resembling the job.
I've done a lot of interviews, and inevitably, most of the devs I interview can't pass a trivial interview (like implement fizzbuzz). The ones who can do a decent job are usually folks we have to compete for.
This is great. One of the things I say to my wife all the time, which is taken from a Kurt Vonnegut quote, is that "I don't have to be good at my hobbies".
It's my preference to a point. I think you can over-do it. I've worked in systems that didn't use it and worked just fine. I would bet most folks err on the side of too little, unless they have some kind of framework doing the heavy lifting.
I see a lot of times people (read: me) are lazy and make a mock that does not have anywhere near the behavior of the original. It's more like a very partial stub. I will mock an api with 20 possible calls with the 2 that I use. Unsurprisingly, this mock is closely tied to the current implementation.
I've been working on a web framework in Clojure. There are already a few others, but they're, in my opinion, too focused on the Clojure community, and are much harder to sell to people I know who might otherwise use Clojure. I wanted something that was more like a Rails or a Phoenix or a Next.js. We'll see if it goes anywhere.
I mean I hate low effort slop that's pushed from every vaguely technical source and tells me it's great. It's very clearly junk.
I think what people hate is the sense of quality degradation. Everything feels cheap. Everything feels like it's meant to be consumed in the next 20 seconds, and then forgotten about. People want stuff that doesn't suck.
There are plenty of things I work hard on because I like them, but there are also lots of things I have to work hard on because they need to get done.
I have similar feelings about Ikigai, the overlap of what you love, what you are good at, what the world needs, and what you can be paid for. Those things don't really overlap for me.
Isn't that begging the question? If you just accept the presupposition that intelligence is tightly coupled to consciousness, then all that makes perfect sense to me. But I don't see why I should accept that. It isn't obvious to me, and it doesn't match my own experience of being conscious.
Totally possible that we're talking past each other.
But that's not an answer. Why should intelligence and not some other quality be coupled to consciousness? In my experience, consciousness (by which I'm specifically talking about qualia/experience/awarenesss) doesn't at all seem tightly coupled to intelligence. Certainly not in a way that seems obvious to me.
"brain as computer" is just the latest iteration of a line of thinking that goes back forever. Whatever we kinda understand and interact with, that's what we are and what the brain is. Chemicals, electricity, clocks, steam engines, fire, earth; they're all analogies that help us learn but don't necessarily reflect an underlying reality.