The uncanny valley is happening with enterprise work. My boss is in love with Copilot writing documentation that we've sorely needed for many years. He and I can bang out tons of it in minutes that would have taken months before. We do this and then no one reads it.
I've asked people about it and they seem disillusioned. It wasn't written by a human so they see no human value in it. They view it as AI writing documentation for another AI to summarize to them and then another AI to reply or comment. So they don't care or are actively repulsed by it.
I think AI has a long uphill battle in winning over the average Joe.
My experience with AI-written documentation is that, as a category, it contains just enough technical errors that more often than not I end up spending time running down confidently stated errors the old fashioned way: cross-referencing API documentation, reading code, etc. At that point you inevitably end up trying to get in touch with a human from the other team.
In other words, it's not because I don't know it's there, or I don't want to read it, it's because my priors tell me it's going to waste my time. What I end up doing is searching, finding the docs, and reading until I start to get the feeling of hallucinated factual errors.
I'm sure there's AI-written documentation in there where the authors really did a good job reviewing it, and I just didn't notice. But I've also had engineers under me lose weeks of productivity at this point because of documentation confidently presented, insufficiently vetted, that turned out to be wrong.
The step that a lot of people leave out is the revising: it is worth the human hours to go over the outputs of AI for this kind of thing with a fine-tooth comb to make sure it is usable, readable, accurate, etc.
I would then have to wonder if all the time saved in the first place at all. I have heard anecdotes of verifying AI output to be more time-consuming and generally even more painful/stressful than doing the whole work yourself perhaps.
As an employee, I would prefer to not be stressed and as an employer, I would prefer to not additionally stress my employee on all times so that I can have them use the stress for the works which truly matter the most (which is a limited resource as an employee shouldn't be burnt out or shouldn't be given unlimited stress)
Also its probably the ethical thing to do but even rational logic dictates so in my honest opinion (not sure how much of it works exactly on documentation stuff though*)
> He and I can bang out tons of it in minutes that would have taken months before
Here's the problem I have. No doubt an LLM made it faster to write those docs, but did you fully spot check it for accuracy?
A lot of people aren't which I think is why the average joe hates it. These docs can still have AI generated mistakes which are easily glossed over by a regular human.
> Here's the problem I have. No doubt an LLM made it faster to write those docs, but did you fully spot check it for accuracy?
Yes. That was just the writing portion, there is a whole team that works on publishing and proof reading and there are acceptance levels all the way up to the CISO where people validate they read it and approved of the contents. Even with that, no one cares about it.
In general people always seem to want documentation, so they can pull it up exactly when they need it, but will do anything to avoid actually having to read it until that singular moment.
The number of meetings where I can answer all the other attendees' questions because I'm the only one who even skimmed the presenter's docs, I swear.....
Yeah, IDK what to tell you then. Sometimes docs just go unread. There's a reason why "RTFM" is a meme.
It might be that they are wordy. It might be that your readers are lazy. It also might just be they don't realize the effort has been put in to make sure the docs are of high quality.
I assume by "proof-reading" you don't mean just checking that the text doesn't contain spelling mistakes or is incoherent, but including that the content is actually correct. If your people actually invest that much into documentation, what the point of the LLM? Isn't the actual writing part like 10% of the total effort expended, in terms of man-hours?
Ignoring how a thing was created, is it useful to me (or anyone)?
The fascination with LLM coding seems rooted in the new ability to create something with very little effort. Unfortunately, some people do not see the trade comes at the moment you have to evaluate the output for fitness or quality.
It turns out that you often need to understand the thing pretty well in order to be qualified to determine the quality of the output. That tends to dilute time gains, unless you leave off the evaluation step.
> Here's the problem I have. No doubt an LLM made it faster to write those docs, but did you fully spot check it for accuracy?
Hi. I write lots of documentation already. I enjoy the taste of clean, fresh, accurate documentation.
Spot-check it for accuracy? I review it. The same way I would review other documentation in the past. The difference? Fewer errors and issues, and when I do find them, it's far easier to get things sorted out.
> A lot of people aren't
Correct. A lot of people aren't reviewing. Not even AI, just reviewing in general. And even when they review, they are only looking, not testing.
The difference is that before, it was a human mistake. Now it's an AI mistake, and people HATE AI mistakes. Even if the number of AI mistakes is fewer than the human mistakes.
I don't want to pretend that documentation is easy, and well-made human documentation is still far better than the best AI documentation for the most part. But... it depends on the audience and purpose. Most importantly, AI documentation is good enough for most cases, and well-made human documentation is far rarer.
>Now it's an AI mistake, and people HATE AI mistakes. Even if the number of AI mistakes is fewer than the human mistakes.
That's because AIs make mistakes no human would. If you're documenting a function, you might misspell something (or orthographically spell something that should be misspelled), or confuse two functions with similar names; you won't reference a function or feature that doesn't and has never existed.
> you won't reference a function or feature that doesn't and has never existed.
That does sometimes exist in human docs. I've stumbled on "aspirational" features in docs that never really existed but were more just intended to exist.
To me the mistakes are bad, but it's also that the docs tend to be pretty low quality IMO. LLMs tend to like to write novels where a sentence would have been better.
Yeah, that's true. I don't understand why they do that. People don't write like that, we're pretty economical. It's not even that they're repetitive to emphasize a point, they just engage in horrific circumlocution. Is it, like, that the facts of the input only percolate through the network when they emit a token, so they only "think" when they're outputting something? I don't know if that's it, but that's what I would think if I caught someone writing like this, that they're writing faster than they can think, so they fill the void with vacuous noise.
My non-serious assumption is that they prioritized the classic writings of 1800s authors like Johann David Wyss in their training. These authors were paid by the word, which resulted in long pointless chapters in their books just to milk money out of the printers.
> Now it's an AI mistake, and people HATE AI mistakes. Even if the number of AI mistakes is fewer than the human mistakes.
I dont know. We have this hype cycle where ai or cars are talked about flawless or so much better then people ... years before they actually are. And then in each time we find that nah, they were not but now this time they certainly are.
And each time I read on HN about how people expect so much better from tech then from people. And usually, when you look at it, the opposite is true. Where human get criticised, tech gets tripple benefit of doubt.
AI documentation is also often incredibly verbose. It makes it difficult to see the forest through the trees. I am often repulsed by the README.md in many "AI generated" projects.
Regardless of reasons they tell you, if no one reads your documentation, then it isn't good enough. Good documentation gets read, as long as it is good. It sounds to me like you're disillusioned, if you're not responding to the feedback, even if you sometimes have to look through the reasons people tell you on the surface.
There are many reasons people might not read your documentation, and "it isn't good enough" is only one of them. To wit:
- they don't know about it
- they can't find it when they need it
- they just don't read documentation (quite common)
- they've been burned by stale docs in the past
and I'm sure other reasons besides.
And while you're right, that sometimes/usually/always the documentation isn't good enough, it's a fallacy to think that the person who has the information needed, has the skill to write docs that are good enough for people to read. And if they have the skill, they don't have the time to apply it sufficiently.
Let's face it: good docs aren't valued. Not by the organization structurally, and not by the individuals within the organization. You may say that you value it, but I bet that if someone offered to document whatever code or process to your 'good enough' level, and it would take a month to do, as a manager you would tell them to take less time (i.e. create bad documentation) and get to something more important.
Maybe. But also if the thing was not documented for years, then maybe the users learned how to use it without documentation? Or at least how to get what they need done.
People won't read documentation of something they already know (or think they know).
My co-worker has been using Copilot for his readme files. It would be better to have nothing at all. Without a readme fill I would go to the code to find what I need, or ask him. With the Copilot readme file, I get a bit excited that I will save some time, read it, think some things sound a bit off, go to the code, find that the readme is a fabrication with no basis in reality, reach out to the co-worker to tell him what happened, wait for him to manually write a proper readme, and then I can carry on with my work.
I see these AI docs as a net negative. The uphill battle isn’t with the average Joe, it’s for the technology to live up to its promise, or to stop selling lies.
This to me is an anti-pattern that I see everywhere because we're still in the early stages of understanding how to adopt these things and create real agentic workflows.
Why should humans read all that documentation if they're ultimately not going to be the ones implementing it?
I see similar patterns like this everywhere, people asking questions about a PR that an engineer then copy pastes to an agents and the copy pastes back to the PR. It's obvious that humans are still in the loop in awkward places.
I've pointed this out before, but web development went through similar growing pains where we did all sorts of weird stuff because we hadn't quite figured out the patterns that work.
Right now nobody really knows what works and the tools we're using are still changing very rapidly. 6 months ago almost nobody was using agent harnesses and thinking about agents writing all of your code was preposterous. Today even the hardcore, AI-skeptic people on my team still have agents writing the vast majority of their code.
It's very clear to me that we're still stuffing agentic behavior into workflows designed for humans. It shouldn't be at all surprising that these patterns feel weird and sometimes broken. It has nothing to do with "winning over the average Joe" but rather these patterns evolving so they actually make sense.
A) this is what happens with documentation, in general.
B) as an experienced reader of documentation, I can often tell when the documentation is likely to be accurate. It's not worth reading documentation that's inaccurate. AI written things tend to be inaccurate and not worth reading.
You should be happy that your people know to ignore the work you and the boss half assed.
Most people weren't reading documentation when it was written by humans. The low value status of documentation is well supported by the fact your workplace put it off instead of prioritizing it.
You're not wrong, but we've had a huge shake up internally and all of the people that used to complain about not having it are now in a position to create it and approve it. They just don't care anymore because now its just AI.
Those shakeups have happened many times over the decades. Nothing changed.
Once in a while someone wrote documentation - but nobody read it. Then that person was moved elsewhere in another shakeup and their documentation got obsolete. Often the documentation got obsolete even before than because the person writing it didn't maintain it (possibly because nobody was reading it?)
yup, ALMOST correct documentation, but using 10-20x the amount of words needed to actually document. Is it better than nothing? probably? Much of it is really hard for a human to read though. So if the purposed us to document what the AI did for a future instance of an AI, sure, but I don't see the current tech replacing technical writers in the short term.
I am seeing the same thing. People are even sending slack messages using cursor or claudecode. You post a PR or ask a question, I get a long response that was not written by a human. Uncanny valley it is.
Unless you've checked it for accuracy why would I read your AI-generated documentation when I can ask my AI (which in a month or two will be a newer, better model than what you used to generate that documentation) to read the code and summarize it for me?
If you did check it for accuracy then I don't understand how you compressed months of work into minutes.
Why bother having Copilot write documentation ahead of time? For the people who need it, they can just ask Copilot the one targeted question they have in that moment and it will serve them a textual answer to exactly that.
Having an AI write docs which are then saved and served strikes me as in the same uncanny valley as fax machines. It's a halfway step that doesn't understand the full import of a new technology. In that case, what you really want is emailing PDFs around and docusigning.
With AI documentation, let users request the docs they need on-demand.
Might depend on the target reader of the doc... if it's another engineer consuming APIs or libraries, yeah, they can just use Copilot or other to answer in real-time, no published doc needed.
But if it's a customer? They might not have access to Copilot at all, or whatever AI tool they use might not have access to the source code or other material used to gen the doc.
A lot of times its for audit purposes. You have to show a mature documented program etc.
Other times it's simply for reference purposes. So if you're talking about current enterprise architecture, the AI itself needs something to reference in order to answer.
Probably because you and your boss have valuable context and historical knowledge about why things are the way they are, and this is of course lacking when you pawn the task off to Copilot.
Yes, this right here. Generated content that's based on sources that readers already have access to has no value beyond what they can ask an LLM to generate themselves.
Now, if you write it with tender loving care and bake all that stuff into it, then will humans read it directly? Maybe not, but the information that their agents read and then pass on to them at least has a better chance of being correct and useful. If the success criteria for your documentation was "measurable count of human eyeballs" and not "better outcomes", your docs aren't going to be good anyway.
AI fatigue is one thing, what I'm seeing mistaken for fatigue is AI prejudice, whereby they don't care if it's high quality output, you could have had literal human experts certify it, because it is AI, they just call it slop and walk away. There is no standard or reasoning with these people about AI at all, they've written it off in the most ignorant of ways. I care about the quality of the output, and if its been human vetted.
Edit, adding more:
If its an AI video, I don't care depending on what its supposed to be, I've seen people upset a literal meme AI video was AI, that was the point, it was supposed to be a ridiculous meme, it was on purpose, some of them aren't even as bad as the person dismissing them make them out to be.
Intellectual laziness, worse than the laziness of some people who lean way too much on AI (some people cannot have a conversation with you, without prompting a model every few minutes, its getting ridiculous).
AI has become the next stage after social media, whether you like it or not. It has taken over human interaction in ways we are still learning more about every day. All the "normies" I know use ChatGPT like they would have used Facebook.
If the documentation is generated by AI, often it's better to just share the prompts used, instead of the documentation.
We do this to make sure people know what to ask for. The answer can be generated when they need it and it will be then based on the current state of things.
If you didn't have the time to write something, why would you expect someone to spend the time to read it? Did _you_ read all of the documentation you generated?
Nobody willingly reads docs. Docs don't exist for the reader, they exist for the writer(s) - because it saves them having to explain the same thing over and over again. Having docs is nice for continuity and for the people who take initiative to seek them out instead of just asking others, but their real value is turning daily (or hourly) 30 minute explanation into a link and a "let me know if you have any questions". The doc pays for itself the second time someone asks you about it.
If they can tell it is written with AI, then the docs are slop. If you're writing something lots of people will use, don't skimp on model or reasoning level, and front load with style guides and examples.
The new key for documentation is that it doesn't need to be was by humans. Good docs are just as valuable whether people read them, or just ask an LLM and the LLM RAGs the information from your docs. The main difference you have to focus on nowadays is ensuring your documentation, even internal documentation, has good "SEO" that it gets looked up.
If that documentation serves another human-operated querying AI it already provides value as a cached work that prevents another AI from re-extracting that knowledge from the code (burning time & tokens in the process).
Another question is keeping those docs up to date...
AI or not, most people never cared about documentation. I have always had to fight tooth and nail to get people to write shit down, and that hasn't changed with AI.
In 2021 I wrote a ton of docs for outlining our deployment and various how-tos, basically just got a "cool thanks bro" for my time. People never cared, I think AI is just a convenient modern excuse.
Work for a big enough enterprise and you’ll spend tons of time making reams of documentation that nobody ever reads and only exists to check a box. Stick around long enough and maybe a 3rd party auditor will read some of it.
To be fair, AI writing is often unhuman. The biggest problem its more verbose than human writing. It adds additional not needed mental load in processing text.
Even in code documentation, I just need a function block that says "DO NOT PASS A VALUE OF 2", with maybe a deeper comment that says "yea the math breaks here", instead of a 5 page discourse on why you should not pass a value of 2.
You make a good point but it's also subjective. The documentation we need is all technical in nature so we aren't looking for Shakespeare or Tolkien here. We just need it to be accurate and usable, which it is.
In the context of documentation, it's not about disillusionment. It doesn't matter if you write it, an AI writes it, if there's a searchable wiki, a chat bot front end etc., your colleagues will track you down and ask you about it personally. They don't want documentation. They want to make their problem into your problem.
my issue is that people insist their written ai work -- including documentation -- is correct only for myself and many others to repeatedly discover this isn't the case.
there's also the issue that people keep switching models when their quota is used up and so at first it seems to all be in order but upon digging in suddenly it hugely diverges in tone/usefulness if it doesn't just collapse in on itself outright; making diving into documentation even more of a hassle than it was before.
even worse is that when they bring back in the previous model upon quota reset it just consumes the information from the crappier/cheaper one and errors start compounding and you want to report it and they're like "sorry we closed our public issue tracker yoy have to join our discord server" and then you have to grab the attention of extremely unwilling developers who repeatedly insist there isn't a problem until you start copy-pasting their quite frankly shit documentation en-masse.
then its "oh that's a typo; the command is correct 25 pages/sections ago so why would you believe it in this section when it's obvious that its wrong here?" like it's your fault they can't keep their goddang slop together and parse through the glaring errors.
a manual should be able to be pulled off a bookshelf (or opened if digital) and allow you to flip to the relevant page so that you can refer to it as a reference and these jerks are hellbent on blaming users for when their jank documentation looks clearly hallucinated by 3 seperate LLMs.
others have commented some good comments on the documentation aspect. I wish to talk more about incentives instead. I will set aside the discussion of if the AI writing docs and people caring about AI written docs.
> He and I can bang out tons of it in minutes that would have taken months before
Pre-AI, you had some work X and you were given some salary Y and you did the work in time T, now you are expected to 10-100 times X work in time T but given the same salary Y
People are worrying about their salaries and future and some people especially within Silicon valley are worried for whats to come next with AI datacenters raising electricity prices and this fear of permanent underclass and job insecurity and a terrible job market with layoffs partially because of AI spending.
If it feels stressful, its because it probably is. I imagine that some people as such might feel that reading the very same AI documentation with the same passion/care is hard.
So yes, AI has a long uphill battle in winning over the average Joe because everything in its current implementation is actively trying to screw average Joe if we think about it
but it differs depending on your incentives on your current time. In your current job, you are the one writing these AI docs in minutes, now imagine spending hours reading those very same AI docs with all the things that I have mentioned, perhaps I hope you understand why it might be more frustrating.
(also when I mean average Joe I would consider software engineer folks like us to be the one more effected than even other professions so we are the average Joe I am talking about. Its not all gloom and doom though and the average joe is split between liking/disliking it and having a nuanced opinion in the middle)
I grew up learning how to write by hand, and when I was in college we were required to code by hand. It was cool. When I need to do something hard I still reach for pen and paper. Sometimes though, writing long stuff with pen and paper is just hard. It hurts and my handwriting isn't excellent.
I was curious about typewriters and so I learned about them and bought a few. They're amazing devices. Much closer to writing by hand with a pen then a printer. Composition and editing happen in separate stages. You can write very fast though with perfect handwriting.
I think from doing this, and other things, I realized that software was so well designed in the past because it was built by people who grew up with better metaphors for the work humans do. Computers were made because their benefits were so enormous that it was worth trying to get them even 1/10 as close as doing real work was. That experiment has largely succeeded. The only failure is then people grew up without seeing the computer as a metaphor for the work, but as the work itself. That's why software is so poorly designed.
Just take a cork board for example. You put your stuff on it. When you want to see something you just turn your head. If you leave for the day and come back everything is still there. There's no on or off. Everything is persistent by default. Input and output are universal. You just write on stuff. You want to share a file with someone, just give it to them. Or make a copy.
I think we have forgotten how great real life was at getting stuff done. The computer was supposed to assist them and for a time it did. That is until we forgot what it was for and made it replace life altogether.
> I think we have forgotten how great real life was at getting stuff done. The computer was supposed to assist them and for a time it did. That is until we forgot what it was for and made it replace life altogether.
I read the book how the internet happened (great book btw) and I would politely like to refuse this claim :)
Or perhaps there could be a separation between the computer and the internet (or more accurately the browsers)
When only computers existed, there were assists of working tools (maybe older versions of docs,excel etc.) but when the internet browsers happened (Netscape), from the very start of it, there were ideas of advertisement and monetization of it.
The only reason that internet turned out to be so open in the start was that Netscape wanted to have it open to get as much turf as possible before Microsoft realizes and they did everything and even then Microsoft had too much monopoly and they released Internet Explorer.
Before internet or pre-dawn of it, there were people with computer magazines and people tinkering and it might be one of you judging from writing code by hand :)
There was an real passion in it and people like you followed it, until the internet experiment really worked and then sooner or later things from internet started reverting to some form of enshittification and immense advertisements and stock markets wanting more advertisements leading to wanting more retention and wanting to create/replace life altogether (most literally Meta and its failed metaverse)
While writing this comment, I have come to insight: Internet had come to replace to the Television (Information Highway) but lately it has ended up becoming one. The last line of "That is until we forgot what it was for and made it replace life altogether." might apply to television as well and the only bottleneck during that time was the technology which seems to have been the internet as now we have youtube,insta,tiktok with infinite scroll feeds, so perhaps things have always been like this way but you were never exposed so much to that side but now its coming for the coding side of things which you are passionate about.
In that sense nothing is as good or as bad as it seems but we are certainly going on a downward trend perhaps depending on the metric and I would prefer living in the golden past so I envy you :)
>AI is not so elegant, to make a comparison similar to Berry, as the humble, sterile Microsoft Word.
This is much like Berry drawing the line at a typewriter instead of a computer. To call a computer "sterile, untouched, factory made" and still use a typewriter is comical. Now let me tell you why etching into stone is the best medium.
People can have their preferences, but this kind of "I'm old fashioned and here's why that's better" posts are just nostalgia bait.
Neither the original 1987 story nor the blog post make any sense to me. I feel the authors are focused on a niche aspect: exchanging deep human thoughts with other humans. For that use case, sure, don’t use a computer, don’t use AI.
But there’s nothing wrong with a car made by a robot factory. The car is useful, regardless of how it was made. AI lets some people create new products, those may be useful.
Probably not the author's point but to me, the takeaway is that these people are driven by emotion and can't be won over with rational arguments. They have an emotional attachment to their old ways, a fear of being obsoleted, a wish that there is something special about humans, etc.
the point I see is that even if you automate all that is possible to automate, there are some core activities that can't be delegated to machines in order for a product to feel very good. May it be the design, or whatever: I don't have an opinion on which aspect must be curated by a human, but some aspect has to. Maybe this aspect is simply AI review and prompting, or AI infrastructure creation and maintenance... I don't know. But the point is that this part of production exists, and it's what makes a useful product something you want to buy more than another useful product.
I'm pretty undecided on where I stand on LLMs, but I have to point out that I use them before making my point.
The thing with AI is that the output we get from it is not deterministic. With assembly lines you can get a good enough deterministic output (having component failures in mind) that everything is gonna be fine. I've never been to a car factory, but I'm sure there are guard rails in place to ensure minimum damage if something goes wrong. There is simply not such a thing with AI, thus the programmer has to be the guardrail. The blog post leans a bit heavy into sentimental words for the programmer's mind, but I'm guessing this is what they mean by the "deep human thoughts" part.
I do love some comments where people have nuanced thoughts on LLMs, so thank you for sharing them!
I'm more so undecided on them because of the social effects on them. I am all for innovation but social media hasn't been the ideal example either (Facebook famously has young girls who are insecure who might delete their pics and not upload them and would show them predatory ads on top of it with countless other examples)
I am one of the younger folks on this website and I honestly feel like it might've been much better for us in the past pre social-media perhaps.
Have we as a society ever truly reflected on innovation. Nuclear innovation comes to my mind in terms of arms race (ironically which I believe that Nuclear could've been really great for power production and I hope that it gets more looked into)
I am also unsure if regulation might make sense, regulation has been tried and nothing seems to work. I had a decent chat with simon once and sort of the conclusion from that and others seems to be that the cat is out of the box.
Thus we might have to think some more about the sentimental values instead as well and do proper evaluations on if it should be used and when.
The whole culture towards AI perhaps can be seen like a fake projection of confidence. Similar to how as you point out from the deterministic/undeterministic part of it from technical point of view as well. (Many) People are projecting AI to be completely deterministic when in reality it sort of isn't.
The quote accurately mirrors a lot of the anti-AI sentiment in my experience. The pushback comes from a visceral, emotional aversion, and the technical or economic arguments proposed against it are largely post-hoc rationalizations.
> The body characterizes everything it touches. What it makes it traces over with the marks of its pulses and breathings, its excitements, hesitations, flaws, and mistakes. On its good work, it leaves the marks of skill, care, and love persisting through hesitations, flaws, and mistakes. And to those of us who love and honor the life of the body in this world, these marks are precious things, necessities of life.
Full of intelligence in the statement.
It makes me feel the warm.
AI is not intelligence or a person, even not the real AI, current AI is useful for some things, but not so useful for real value or real world, and it will waste too much your energy, resources, and money in the end.
As a user and consumer of objects, sometimes I want a meaningful experience with a thing made lovingly by human hands. I will take a dinner cooked by my friends over take-out any day of the week even if the restaurant makes objectively better food. But sometimes I am happy to use a mass produced utilitarian object because it solves the problem. I don't have an emotional relationship with my stapler.
These two perspectives are not completely separate. In practice, every object has some mixture of human care and machine optimized productivity.
Likewise, as a producer of objects to be used by others, I want them to have a meaningful connection to me as the maker. But I also want to be able to produce more objects more efficiently so I can affect the lives of more people.
Again, those are not entirely separate stances. With my books, I hand-lettered every single word in the illustrations. But I scanned those and cleaned them up in Photoshop instead of painting over mistakes with correction fluid, and I use the magic of the web and print on demand to put those books in front of thousands of people.
I think most people have had a very uneasy truce with the amount of soulless manufactured junk in our lives versus the crafted things that we cherish. Most of us have a nagging feeling as we sit in our IKEA-filled homes watching parasocial videos on our phones that despite all the material boons industrialization has given us, we are suffering from a poverty of meaningful connection. But, also... we keep buying that stuff because stuff is nice and solves real problems.
AI has set off a bomb right in the center of that uneasy truce and now all of us are struggling to work through the psychological fallout. It is a true fact that AI will make it much easier and cheaper to produce more digital goods with real utilitarian value. It is also a true fact that it will flood our social spaces with slop and make it even harder to find a real connection with a real human in that hazy smoke of AI bullshit.
Reconciling those is the existential question of our generation. I don't believe it will be solved by taking a side. It will be solved, if at all, through some sort of more meaningful synthesis of the two halves.
> AI is probabilistic and any probabilistic system can inherently never be perfect as it also still makes numerous mistakes. Work still needs to be reviewed by humans.
I don't know why people keep saying this. I don't believe code needs to be reviewed by humans. Are humans infallible? I think 80%+ of code is basically human slop. Do we review the assembly language that is generated by compilers?
I think given where AI-generated code is, and where it's going, all we need to do is test the outputs, basically turning us into QA. As someone who loves to code, yes I find it distasteful, but we don't get paid for our code, we get paid for our programs. I prefer being paid.
If you want to write beautiful code, you can do it as a side hustle at home, but I think very quickly, this is what our industry is turning into. In January, someone told me that an expert told him that software engineering would be dead in 3 months, and I scoffed at the time, but now I think it's pretty accurate. It definitely won't survive this year.
Compilers are deterministic, though. If you don't put garbage in, you won't get garbage out. With a probabilistic system you can have varying outputs for the same input, thus the need to spend (waste?) effort verifying that your output is quality.
No comment on the rest of your comment. The assembly piece just bothered me in particular.
The top AI labs still employ thousands of software engineers. If it was dead, they'd be among the first to stop employing them. If by "software engineering is dead" you mean that using AI coding tools is now part of the job description, I think that's largely correct.
> In January, someone told me that an expert told him that software engineering would be dead in 3 months, and I scoffed at the time, but now I think it's pretty accurate
I mean, maybe your 3 month prediction is correct. But by definition that expert's 3 month prediction wasn't accurate because software engineering is still around and it's after April. We are 3.5 years in '6months until programming is solved'.
To me it's not a theoretical issue. I have personally caught multiple issues in code review this month that would have caused an outage had I allowed the PR to be merged. The agent that generated the PR made plausible-sounding but incorrect assertions about what the output should be. So if I don't want production outages I have to do code review.
I've seen some people suggest that I should be require agents to produce an extremely detailed PR description and review that instead, which perhaps would have worked. But I don't understand the appeal. Why would I want to review a lossy, imprecise description of what the code does instead of reviewing the actual code and what it actually does?
The uncanny valley is happening with enterprise work. My boss is in love with Copilot writing documentation that we've sorely needed for many years. He and I can bang out tons of it in minutes that would have taken months before. We do this and then no one reads it.
I've asked people about it and they seem disillusioned. It wasn't written by a human so they see no human value in it. They view it as AI writing documentation for another AI to summarize to them and then another AI to reply or comment. So they don't care or are actively repulsed by it.
I think AI has a long uphill battle in winning over the average Joe.
> We do this and then no one reads it.
My experience with AI-written documentation is that, as a category, it contains just enough technical errors that more often than not I end up spending time running down confidently stated errors the old fashioned way: cross-referencing API documentation, reading code, etc. At that point you inevitably end up trying to get in touch with a human from the other team.
In other words, it's not because I don't know it's there, or I don't want to read it, it's because my priors tell me it's going to waste my time. What I end up doing is searching, finding the docs, and reading until I start to get the feeling of hallucinated factual errors.
I'm sure there's AI-written documentation in there where the authors really did a good job reviewing it, and I just didn't notice. But I've also had engineers under me lose weeks of productivity at this point because of documentation confidently presented, insufficiently vetted, that turned out to be wrong.
The step that a lot of people leave out is the revising: it is worth the human hours to go over the outputs of AI for this kind of thing with a fine-tooth comb to make sure it is usable, readable, accurate, etc.
I would then have to wonder if all the time saved in the first place at all. I have heard anecdotes of verifying AI output to be more time-consuming and generally even more painful/stressful than doing the whole work yourself perhaps.
As an employee, I would prefer to not be stressed and as an employer, I would prefer to not additionally stress my employee on all times so that I can have them use the stress for the works which truly matter the most (which is a limited resource as an employee shouldn't be burnt out or shouldn't be given unlimited stress)
Also its probably the ethical thing to do but even rational logic dictates so in my honest opinion (not sure how much of it works exactly on documentation stuff though*)
1-shotting documentation with AI is a bad idea. You then have to have multiple verification passes to have any chance of it being worth anything.
Like if you have an AI generate a runbook, then you better have the AI actually validate the runbook and make sure it is correct.
> He and I can bang out tons of it in minutes that would have taken months before
Here's the problem I have. No doubt an LLM made it faster to write those docs, but did you fully spot check it for accuracy?
A lot of people aren't which I think is why the average joe hates it. These docs can still have AI generated mistakes which are easily glossed over by a regular human.
> Here's the problem I have. No doubt an LLM made it faster to write those docs, but did you fully spot check it for accuracy?
Yes. That was just the writing portion, there is a whole team that works on publishing and proof reading and there are acceptance levels all the way up to the CISO where people validate they read it and approved of the contents. Even with that, no one cares about it.
In general people always seem to want documentation, so they can pull it up exactly when they need it, but will do anything to avoid actually having to read it until that singular moment.
The number of meetings where I can answer all the other attendees' questions because I'm the only one who even skimmed the presenter's docs, I swear.....
Yeah, IDK what to tell you then. Sometimes docs just go unread. There's a reason why "RTFM" is a meme.
It might be that they are wordy. It might be that your readers are lazy. It also might just be they don't realize the effort has been put in to make sure the docs are of high quality.
In this case, effort has _not_ been put in to make sure the docs are of high quality, and the potential readers know that, which is surely relevant.
I assume by "proof-reading" you don't mean just checking that the text doesn't contain spelling mistakes or is incoherent, but including that the content is actually correct. If your people actually invest that much into documentation, what the point of the LLM? Isn't the actual writing part like 10% of the total effort expended, in terms of man-hours?
Ignoring how a thing was created, is it useful to me (or anyone)?
The fascination with LLM coding seems rooted in the new ability to create something with very little effort. Unfortunately, some people do not see the trade comes at the moment you have to evaluate the output for fitness or quality.
It turns out that you often need to understand the thing pretty well in order to be qualified to determine the quality of the output. That tends to dilute time gains, unless you leave off the evaluation step.
> Here's the problem I have. No doubt an LLM made it faster to write those docs, but did you fully spot check it for accuracy?
Hi. I write lots of documentation already. I enjoy the taste of clean, fresh, accurate documentation.
Spot-check it for accuracy? I review it. The same way I would review other documentation in the past. The difference? Fewer errors and issues, and when I do find them, it's far easier to get things sorted out.
> A lot of people aren't
Correct. A lot of people aren't reviewing. Not even AI, just reviewing in general. And even when they review, they are only looking, not testing.
The difference is that before, it was a human mistake. Now it's an AI mistake, and people HATE AI mistakes. Even if the number of AI mistakes is fewer than the human mistakes.
I don't want to pretend that documentation is easy, and well-made human documentation is still far better than the best AI documentation for the most part. But... it depends on the audience and purpose. Most importantly, AI documentation is good enough for most cases, and well-made human documentation is far rarer.
>Now it's an AI mistake, and people HATE AI mistakes. Even if the number of AI mistakes is fewer than the human mistakes.
That's because AIs make mistakes no human would. If you're documenting a function, you might misspell something (or orthographically spell something that should be misspelled), or confuse two functions with similar names; you won't reference a function or feature that doesn't and has never existed.
> you won't reference a function or feature that doesn't and has never existed.
That does sometimes exist in human docs. I've stumbled on "aspirational" features in docs that never really existed but were more just intended to exist.
To me the mistakes are bad, but it's also that the docs tend to be pretty low quality IMO. LLMs tend to like to write novels where a sentence would have been better.
Yeah, that's true. I don't understand why they do that. People don't write like that, we're pretty economical. It's not even that they're repetitive to emphasize a point, they just engage in horrific circumlocution. Is it, like, that the facts of the input only percolate through the network when they emit a token, so they only "think" when they're outputting something? I don't know if that's it, but that's what I would think if I caught someone writing like this, that they're writing faster than they can think, so they fill the void with vacuous noise.
My non-serious assumption is that they prioritized the classic writings of 1800s authors like Johann David Wyss in their training. These authors were paid by the word, which resulted in long pointless chapters in their books just to milk money out of the printers.
> Now it's an AI mistake, and people HATE AI mistakes. Even if the number of AI mistakes is fewer than the human mistakes.
I dont know. We have this hype cycle where ai or cars are talked about flawless or so much better then people ... years before they actually are. And then in each time we find that nah, they were not but now this time they certainly are.
And each time I read on HN about how people expect so much better from tech then from people. And usually, when you look at it, the opposite is true. Where human get criticised, tech gets tripple benefit of doubt.
> It wasn't written by a human so they see no human value in it.
Which is true, in a way, the data put down as documentation can now be calculated in seconds, and documentation is just a cache.
The truth is the documentation never had any value.
AI documentation is also often incredibly verbose. It makes it difficult to see the forest through the trees. I am often repulsed by the README.md in many "AI generated" projects.
> no one reads it. [... ] they seem disillusioned
Regardless of reasons they tell you, if no one reads your documentation, then it isn't good enough. Good documentation gets read, as long as it is good. It sounds to me like you're disillusioned, if you're not responding to the feedback, even if you sometimes have to look through the reasons people tell you on the surface.
There are many reasons people might not read your documentation, and "it isn't good enough" is only one of them. To wit:
and I'm sure other reasons besides.And while you're right, that sometimes/usually/always the documentation isn't good enough, it's a fallacy to think that the person who has the information needed, has the skill to write docs that are good enough for people to read. And if they have the skill, they don't have the time to apply it sufficiently.
Let's face it: good docs aren't valued. Not by the organization structurally, and not by the individuals within the organization. You may say that you value it, but I bet that if someone offered to document whatever code or process to your 'good enough' level, and it would take a month to do, as a manager you would tell them to take less time (i.e. create bad documentation) and get to something more important.
Maybe. But also if the thing was not documented for years, then maybe the users learned how to use it without documentation? Or at least how to get what they need done.
People won't read documentation of something they already know (or think they know).
My co-worker has been using Copilot for his readme files. It would be better to have nothing at all. Without a readme fill I would go to the code to find what I need, or ask him. With the Copilot readme file, I get a bit excited that I will save some time, read it, think some things sound a bit off, go to the code, find that the readme is a fabrication with no basis in reality, reach out to the co-worker to tell him what happened, wait for him to manually write a proper readme, and then I can carry on with my work.
I see these AI docs as a net negative. The uphill battle isn’t with the average Joe, it’s for the technology to live up to its promise, or to stop selling lies.
> We do this and then no one reads it.
This to me is an anti-pattern that I see everywhere because we're still in the early stages of understanding how to adopt these things and create real agentic workflows.
Why should humans read all that documentation if they're ultimately not going to be the ones implementing it?
I see similar patterns like this everywhere, people asking questions about a PR that an engineer then copy pastes to an agents and the copy pastes back to the PR. It's obvious that humans are still in the loop in awkward places.
I've pointed this out before, but web development went through similar growing pains where we did all sorts of weird stuff because we hadn't quite figured out the patterns that work.
Right now nobody really knows what works and the tools we're using are still changing very rapidly. 6 months ago almost nobody was using agent harnesses and thinking about agents writing all of your code was preposterous. Today even the hardcore, AI-skeptic people on my team still have agents writing the vast majority of their code.
It's very clear to me that we're still stuffing agentic behavior into workflows designed for humans. It shouldn't be at all surprising that these patterns feel weird and sometimes broken. It has nothing to do with "winning over the average Joe" but rather these patterns evolving so they actually make sense.
> We do this and then no one reads it.
A) this is what happens with documentation, in general.
B) as an experienced reader of documentation, I can often tell when the documentation is likely to be accurate. It's not worth reading documentation that's inaccurate. AI written things tend to be inaccurate and not worth reading.
You should be happy that your people know to ignore the work you and the boss half assed.
Most people weren't reading documentation when it was written by humans. The low value status of documentation is well supported by the fact your workplace put it off instead of prioritizing it.
You're not wrong, but we've had a huge shake up internally and all of the people that used to complain about not having it are now in a position to create it and approve it. They just don't care anymore because now its just AI.
Those shakeups have happened many times over the decades. Nothing changed.
Once in a while someone wrote documentation - but nobody read it. Then that person was moved elsewhere in another shakeup and their documentation got obsolete. Often the documentation got obsolete even before than because the person writing it didn't maintain it (possibly because nobody was reading it?)
yup, ALMOST correct documentation, but using 10-20x the amount of words needed to actually document. Is it better than nothing? probably? Much of it is really hard for a human to read though. So if the purposed us to document what the AI did for a future instance of an AI, sure, but I don't see the current tech replacing technical writers in the short term.
I am seeing the same thing. People are even sending slack messages using cursor or claudecode. You post a PR or ask a question, I get a long response that was not written by a human. Uncanny valley it is.
Unless you've checked it for accuracy why would I read your AI-generated documentation when I can ask my AI (which in a month or two will be a newer, better model than what you used to generate that documentation) to read the code and summarize it for me?
If you did check it for accuracy then I don't understand how you compressed months of work into minutes.
Why bother having Copilot write documentation ahead of time? For the people who need it, they can just ask Copilot the one targeted question they have in that moment and it will serve them a textual answer to exactly that.
Having an AI write docs which are then saved and served strikes me as in the same uncanny valley as fax machines. It's a halfway step that doesn't understand the full import of a new technology. In that case, what you really want is emailing PDFs around and docusigning.
With AI documentation, let users request the docs they need on-demand.
Might depend on the target reader of the doc... if it's another engineer consuming APIs or libraries, yeah, they can just use Copilot or other to answer in real-time, no published doc needed.
But if it's a customer? They might not have access to Copilot at all, or whatever AI tool they use might not have access to the source code or other material used to gen the doc.
A lot of times its for audit purposes. You have to show a mature documented program etc.
Other times it's simply for reference purposes. So if you're talking about current enterprise architecture, the AI itself needs something to reference in order to answer.
There are many reasons ultimately.
"If You are Asking for Human Attention, Demonstrate Human Effort"
https://tombedor.dev/human-attention-and-human-effort/
Probably because you and your boss have valuable context and historical knowledge about why things are the way they are, and this is of course lacking when you pawn the task off to Copilot.
Yes, this right here. Generated content that's based on sources that readers already have access to has no value beyond what they can ask an LLM to generate themselves.
Now, if you write it with tender loving care and bake all that stuff into it, then will humans read it directly? Maybe not, but the information that their agents read and then pass on to them at least has a better chance of being correct and useful. If the success criteria for your documentation was "measurable count of human eyeballs" and not "better outcomes", your docs aren't going to be good anyway.
If someone writes content with AI, I don't exactly see a problem with people using AI to synthesize the content. It's a good default.
AI fatigue is one thing, what I'm seeing mistaken for fatigue is AI prejudice, whereby they don't care if it's high quality output, you could have had literal human experts certify it, because it is AI, they just call it slop and walk away. There is no standard or reasoning with these people about AI at all, they've written it off in the most ignorant of ways. I care about the quality of the output, and if its been human vetted.
Edit, adding more:
If its an AI video, I don't care depending on what its supposed to be, I've seen people upset a literal meme AI video was AI, that was the point, it was supposed to be a ridiculous meme, it was on purpose, some of them aren't even as bad as the person dismissing them make them out to be.
Intellectual laziness, worse than the laziness of some people who lean way too much on AI (some people cannot have a conversation with you, without prompting a model every few minutes, its getting ridiculous).
AI has become the next stage after social media, whether you like it or not. It has taken over human interaction in ways we are still learning more about every day. All the "normies" I know use ChatGPT like they would have used Facebook.
If the documentation is generated by AI, often it's better to just share the prompts used, instead of the documentation.
We do this to make sure people know what to ask for. The answer can be generated when they need it and it will be then based on the current state of things.
If you didn't have the time to write something, why would you expect someone to spend the time to read it? Did _you_ read all of the documentation you generated?
> He and I can bang out tons of it in minutes that would have taken months before. We do this and then no one reads it.
Honest question, did you guys read it yourselves before asking the rest of the team to read it?
Nobody willingly reads docs. Docs don't exist for the reader, they exist for the writer(s) - because it saves them having to explain the same thing over and over again. Having docs is nice for continuity and for the people who take initiative to seek them out instead of just asking others, but their real value is turning daily (or hourly) 30 minute explanation into a link and a "let me know if you have any questions". The doc pays for itself the second time someone asks you about it.
If they can tell it is written with AI, then the docs are slop. If you're writing something lots of people will use, don't skimp on model or reasoning level, and front load with style guides and examples.
The new key for documentation is that it doesn't need to be was by humans. Good docs are just as valuable whether people read them, or just ask an LLM and the LLM RAGs the information from your docs. The main difference you have to focus on nowadays is ensuring your documentation, even internal documentation, has good "SEO" that it gets looked up.
AI might be exposing the valuelessness of corporate busywork.
If that documentation serves another human-operated querying AI it already provides value as a cached work that prevents another AI from re-extracting that knowledge from the code (burning time & tokens in the process).
Another question is keeping those docs up to date...
AI or not, most people never cared about documentation. I have always had to fight tooth and nail to get people to write shit down, and that hasn't changed with AI.
In 2021 I wrote a ton of docs for outlining our deployment and various how-tos, basically just got a "cool thanks bro" for my time. People never cared, I think AI is just a convenient modern excuse.
Work for a big enough enterprise and you’ll spend tons of time making reams of documentation that nobody ever reads and only exists to check a box. Stick around long enough and maybe a 3rd party auditor will read some of it.
To be fair, AI writing is often unhuman. The biggest problem its more verbose than human writing. It adds additional not needed mental load in processing text.
Even in code documentation, I just need a function block that says "DO NOT PASS A VALUE OF 2", with maybe a deeper comment that says "yea the math breaks here", instead of a 5 page discourse on why you should not pass a value of 2.
The AI seems to put it's internal reasoning into comments. I have to keep telling it to knock it the fuck off.
You make a good point but it's also subjective. The documentation we need is all technical in nature so we aren't looking for Shakespeare or Tolkien here. We just need it to be accurate and usable, which it is.
Part of being quickly usable might be the brevity or utilitarian style. Maybe it looks intimidatingly long?
In the context of documentation, it's not about disillusionment. It doesn't matter if you write it, an AI writes it, if there's a searchable wiki, a chat bot front end etc., your colleagues will track you down and ask you about it personally. They don't want documentation. They want to make their problem into your problem.
my issue is that people insist their written ai work -- including documentation -- is correct only for myself and many others to repeatedly discover this isn't the case.
there's also the issue that people keep switching models when their quota is used up and so at first it seems to all be in order but upon digging in suddenly it hugely diverges in tone/usefulness if it doesn't just collapse in on itself outright; making diving into documentation even more of a hassle than it was before.
even worse is that when they bring back in the previous model upon quota reset it just consumes the information from the crappier/cheaper one and errors start compounding and you want to report it and they're like "sorry we closed our public issue tracker yoy have to join our discord server" and then you have to grab the attention of extremely unwilling developers who repeatedly insist there isn't a problem until you start copy-pasting their quite frankly shit documentation en-masse.
then its "oh that's a typo; the command is correct 25 pages/sections ago so why would you believe it in this section when it's obvious that its wrong here?" like it's your fault they can't keep their goddang slop together and parse through the glaring errors.
a manual should be able to be pulled off a bookshelf (or opened if digital) and allow you to flip to the relevant page so that you can refer to it as a reference and these jerks are hellbent on blaming users for when their jank documentation looks clearly hallucinated by 3 seperate LLMs.
it is beyond frustratung.
others have commented some good comments on the documentation aspect. I wish to talk more about incentives instead. I will set aside the discussion of if the AI writing docs and people caring about AI written docs.
> He and I can bang out tons of it in minutes that would have taken months before
Pre-AI, you had some work X and you were given some salary Y and you did the work in time T, now you are expected to 10-100 times X work in time T but given the same salary Y
People are worrying about their salaries and future and some people especially within Silicon valley are worried for whats to come next with AI datacenters raising electricity prices and this fear of permanent underclass and job insecurity and a terrible job market with layoffs partially because of AI spending.
If it feels stressful, its because it probably is. I imagine that some people as such might feel that reading the very same AI documentation with the same passion/care is hard.
So yes, AI has a long uphill battle in winning over the average Joe because everything in its current implementation is actively trying to screw average Joe if we think about it
but it differs depending on your incentives on your current time. In your current job, you are the one writing these AI docs in minutes, now imagine spending hours reading those very same AI docs with all the things that I have mentioned, perhaps I hope you understand why it might be more frustrating.
(also when I mean average Joe I would consider software engineer folks like us to be the one more effected than even other professions so we are the average Joe I am talking about. Its not all gloom and doom though and the average joe is split between liking/disliking it and having a nuanced opinion in the middle)
[dead]
[dead]
[dead]
I grew up learning how to write by hand, and when I was in college we were required to code by hand. It was cool. When I need to do something hard I still reach for pen and paper. Sometimes though, writing long stuff with pen and paper is just hard. It hurts and my handwriting isn't excellent.
I was curious about typewriters and so I learned about them and bought a few. They're amazing devices. Much closer to writing by hand with a pen then a printer. Composition and editing happen in separate stages. You can write very fast though with perfect handwriting.
I think from doing this, and other things, I realized that software was so well designed in the past because it was built by people who grew up with better metaphors for the work humans do. Computers were made because their benefits were so enormous that it was worth trying to get them even 1/10 as close as doing real work was. That experiment has largely succeeded. The only failure is then people grew up without seeing the computer as a metaphor for the work, but as the work itself. That's why software is so poorly designed.
Just take a cork board for example. You put your stuff on it. When you want to see something you just turn your head. If you leave for the day and come back everything is still there. There's no on or off. Everything is persistent by default. Input and output are universal. You just write on stuff. You want to share a file with someone, just give it to them. Or make a copy.
I think we have forgotten how great real life was at getting stuff done. The computer was supposed to assist them and for a time it did. That is until we forgot what it was for and made it replace life altogether.
> I think we have forgotten how great real life was at getting stuff done. The computer was supposed to assist them and for a time it did. That is until we forgot what it was for and made it replace life altogether.
I read the book how the internet happened (great book btw) and I would politely like to refuse this claim :)
Or perhaps there could be a separation between the computer and the internet (or more accurately the browsers)
When only computers existed, there were assists of working tools (maybe older versions of docs,excel etc.) but when the internet browsers happened (Netscape), from the very start of it, there were ideas of advertisement and monetization of it.
The only reason that internet turned out to be so open in the start was that Netscape wanted to have it open to get as much turf as possible before Microsoft realizes and they did everything and even then Microsoft had too much monopoly and they released Internet Explorer.
Before internet or pre-dawn of it, there were people with computer magazines and people tinkering and it might be one of you judging from writing code by hand :)
There was an real passion in it and people like you followed it, until the internet experiment really worked and then sooner or later things from internet started reverting to some form of enshittification and immense advertisements and stock markets wanting more advertisements leading to wanting more retention and wanting to create/replace life altogether (most literally Meta and its failed metaverse)
While writing this comment, I have come to insight: Internet had come to replace to the Television (Information Highway) but lately it has ended up becoming one. The last line of "That is until we forgot what it was for and made it replace life altogether." might apply to television as well and the only bottleneck during that time was the technology which seems to have been the internet as now we have youtube,insta,tiktok with infinite scroll feeds, so perhaps things have always been like this way but you were never exposed so much to that side but now its coming for the coding side of things which you are passionate about.
In that sense nothing is as good or as bad as it seems but we are certainly going on a downward trend perhaps depending on the metric and I would prefer living in the golden past so I envy you :)
>AI is not so elegant, to make a comparison similar to Berry, as the humble, sterile Microsoft Word.
This is much like Berry drawing the line at a typewriter instead of a computer. To call a computer "sterile, untouched, factory made" and still use a typewriter is comical. Now let me tell you why etching into stone is the best medium.
People can have their preferences, but this kind of "I'm old fashioned and here's why that's better" posts are just nostalgia bait.
Neither the original 1987 story nor the blog post make any sense to me. I feel the authors are focused on a niche aspect: exchanging deep human thoughts with other humans. For that use case, sure, don’t use a computer, don’t use AI.
But there’s nothing wrong with a car made by a robot factory. The car is useful, regardless of how it was made. AI lets some people create new products, those may be useful.
Probably not the author's point but to me, the takeaway is that these people are driven by emotion and can't be won over with rational arguments. They have an emotional attachment to their old ways, a fear of being obsoleted, a wish that there is something special about humans, etc.
the point I see is that even if you automate all that is possible to automate, there are some core activities that can't be delegated to machines in order for a product to feel very good. May it be the design, or whatever: I don't have an opinion on which aspect must be curated by a human, but some aspect has to. Maybe this aspect is simply AI review and prompting, or AI infrastructure creation and maintenance... I don't know. But the point is that this part of production exists, and it's what makes a useful product something you want to buy more than another useful product.
I'm pretty undecided on where I stand on LLMs, but I have to point out that I use them before making my point. The thing with AI is that the output we get from it is not deterministic. With assembly lines you can get a good enough deterministic output (having component failures in mind) that everything is gonna be fine. I've never been to a car factory, but I'm sure there are guard rails in place to ensure minimum damage if something goes wrong. There is simply not such a thing with AI, thus the programmer has to be the guardrail. The blog post leans a bit heavy into sentimental words for the programmer's mind, but I'm guessing this is what they mean by the "deep human thoughts" part.
I do love some comments where people have nuanced thoughts on LLMs, so thank you for sharing them!
I'm more so undecided on them because of the social effects on them. I am all for innovation but social media hasn't been the ideal example either (Facebook famously has young girls who are insecure who might delete their pics and not upload them and would show them predatory ads on top of it with countless other examples)
I am one of the younger folks on this website and I honestly feel like it might've been much better for us in the past pre social-media perhaps.
Have we as a society ever truly reflected on innovation. Nuclear innovation comes to my mind in terms of arms race (ironically which I believe that Nuclear could've been really great for power production and I hope that it gets more looked into)
I am also unsure if regulation might make sense, regulation has been tried and nothing seems to work. I had a decent chat with simon once and sort of the conclusion from that and others seems to be that the cat is out of the box.
Thus we might have to think some more about the sentimental values instead as well and do proper evaluations on if it should be used and when.
The whole culture towards AI perhaps can be seen like a fake projection of confidence. Similar to how as you point out from the deterministic/undeterministic part of it from technical point of view as well. (Many) People are projecting AI to be completely deterministic when in reality it sort of isn't.
The quote accurately mirrors a lot of the anti-AI sentiment in my experience. The pushback comes from a visceral, emotional aversion, and the technical or economic arguments proposed against it are largely post-hoc rationalizations.
> The body characterizes everything it touches. What it makes it traces over with the marks of its pulses and breathings, its excitements, hesitations, flaws, and mistakes. On its good work, it leaves the marks of skill, care, and love persisting through hesitations, flaws, and mistakes. And to those of us who love and honor the life of the body in this world, these marks are precious things, necessities of life.
Full of intelligence in the statement.
It makes me feel the warm.
AI is not intelligence or a person, even not the real AI, current AI is useful for some things, but not so useful for real value or real world, and it will waste too much your energy, resources, and money in the end.
"I am not without hope."
I am not without hope that these writings offer a small respite to the AI weary.
This is a response to a short essay by Wendell Berry which you can read here: http://tipiglen.co.uk/berrynot.html
As a user and consumer of objects, sometimes I want a meaningful experience with a thing made lovingly by human hands. I will take a dinner cooked by my friends over take-out any day of the week even if the restaurant makes objectively better food. But sometimes I am happy to use a mass produced utilitarian object because it solves the problem. I don't have an emotional relationship with my stapler.
These two perspectives are not completely separate. In practice, every object has some mixture of human care and machine optimized productivity.
Likewise, as a producer of objects to be used by others, I want them to have a meaningful connection to me as the maker. But I also want to be able to produce more objects more efficiently so I can affect the lives of more people.
Again, those are not entirely separate stances. With my books, I hand-lettered every single word in the illustrations. But I scanned those and cleaned them up in Photoshop instead of painting over mistakes with correction fluid, and I use the magic of the web and print on demand to put those books in front of thousands of people.
I think most people have had a very uneasy truce with the amount of soulless manufactured junk in our lives versus the crafted things that we cherish. Most of us have a nagging feeling as we sit in our IKEA-filled homes watching parasocial videos on our phones that despite all the material boons industrialization has given us, we are suffering from a poverty of meaningful connection. But, also... we keep buying that stuff because stuff is nice and solves real problems.
AI has set off a bomb right in the center of that uneasy truce and now all of us are struggling to work through the psychological fallout. It is a true fact that AI will make it much easier and cheaper to produce more digital goods with real utilitarian value. It is also a true fact that it will flood our social spaces with slop and make it even harder to find a real connection with a real human in that hazy smoke of AI bullshit.
Reconciling those is the existential question of our generation. I don't believe it will be solved by taking a side. It will be solved, if at all, through some sort of more meaningful synthesis of the two halves.
Why must everything be art?
> AI is probabilistic and any probabilistic system can inherently never be perfect as it also still makes numerous mistakes. Work still needs to be reviewed by humans.
I don't know why people keep saying this. I don't believe code needs to be reviewed by humans. Are humans infallible? I think 80%+ of code is basically human slop. Do we review the assembly language that is generated by compilers?
I think given where AI-generated code is, and where it's going, all we need to do is test the outputs, basically turning us into QA. As someone who loves to code, yes I find it distasteful, but we don't get paid for our code, we get paid for our programs. I prefer being paid.
If you want to write beautiful code, you can do it as a side hustle at home, but I think very quickly, this is what our industry is turning into. In January, someone told me that an expert told him that software engineering would be dead in 3 months, and I scoffed at the time, but now I think it's pretty accurate. It definitely won't survive this year.
Compilers are deterministic, though. If you don't put garbage in, you won't get garbage out. With a probabilistic system you can have varying outputs for the same input, thus the need to spend (waste?) effort verifying that your output is quality.
No comment on the rest of your comment. The assembly piece just bothered me in particular.
The top AI labs still employ thousands of software engineers. If it was dead, they'd be among the first to stop employing them. If by "software engineering is dead" you mean that using AI coding tools is now part of the job description, I think that's largely correct.
I really wanted to write a well structured answer to your comment but then I saw the username and was like "nah I'm fine"
> In January, someone told me that an expert told him that software engineering would be dead in 3 months, and I scoffed at the time, but now I think it's pretty accurate
I mean, maybe your 3 month prediction is correct. But by definition that expert's 3 month prediction wasn't accurate because software engineering is still around and it's after April. We are 3.5 years in '6months until programming is solved'.
wait just three more months and software engineers will be out of job on time.
humans are way better at managing big contexts than a machine. The human mind is way more complex than any AI model + infrastructure.
To me it's not a theoretical issue. I have personally caught multiple issues in code review this month that would have caused an outage had I allowed the PR to be merged. The agent that generated the PR made plausible-sounding but incorrect assertions about what the output should be. So if I don't want production outages I have to do code review.
I've seen some people suggest that I should be require agents to produce an extremely detailed PR description and review that instead, which perhaps would have worked. But I don't understand the appeal. Why would I want to review a lossy, imprecise description of what the code does instead of reviewing the actual code and what it actually does?
[dead]
I like buying old flagships since I couldn't afford them like 5-10 years ago.
Still a few on my list would be neat to try like Specter 360, eventually I want one of the current newest XPS-13s
I recently got a Pixelbook for $80 running Ubuntu on that, great little device as far as thinness
Also like buying/trying out weird computers or old, like the ASUS Eee PCs or Librettos
did you even read the blog post my guy
Skimmed "write by hand or typewriter" yeah I'm not like that, I am rote based though so have to type into a computer to remember notes
Who wants to f around with a typewriter anyway I guess this guy in particular does
How you gonna blog with a typewriter