I have tons of random receipts that come in every month that need to be captured, memoed, categorized and sent off to finance.
I made python to read image/pdf/whatever to text, easy.
I regex the value out, hard and fragile
I try to pull the vendors name out, just not reliable
Category... nearly impossible so i need to make some form of memory system to remember once I do it.
Python renames the file with input if it needs it and provides the meta
OR
python to text because it's effciient
api call to Ollama and let my old 2070 work it out. (highly reliable)
python renames the file and provides the meta
It's small, low power, hard to do with code, basically the perfect use case. This is a good use of AI
Go Rewrite FFMPEG in Rust.... that's a bad use of AI.
There's a lot of people out there using it in ways that cost a lot more than human eyes and have horrible societal and environmental impacts.
There's a lot of people using it for dictation, document triage and basic scripting where it has great advantages and isn't making the world a worse place.
His article is at odds with a great deal of his book. I wonder if this isn't just a grab to get hardcore anti-ai to buy it.
Nothing is helpful until you need help. The fact that you think AI is helpful for you don't have to force me to use AI. If you pay me $100k+ per year and you force me to use your tools to do my job why you even hired me ? To force this cult on me or to do the job ?
It's pretty normal for an employer to dictate what tools and applications an employee uses. If you prefer gitlab but your employer requires teamcity, you don't really get a say, right?
However, if you think you can meet your deadlines without using a code generating AI tool, then don't use it. Ideally, if they are as useless as you imply, no one will be able to tell whether you're using it. The conflict should only really appear if they do increase productivity, and you refuse to use them, resulting in less productivity than your peers.
Company will be able to tell if you're using it because companies behind sota models come with monitoring. You will have meeting with hr and your manager when you will be forced to use it even if you meet quotas. They will argument it that maybe you can do more and increase your normal quota with expected ai usage increase in productivity even if you had best productivity in team without ai and your productivity stays the same. Suddenly you will be under performing because you are refusing to use ai so you will be first to fire even if you are best employee. That's how corporations work. They are monitoring usage because it costs them money. For big corporations they pay upfront to get discounts. Company also make many trainings and meetings to encourage everyone use AI models they pay for but nobody wanted.
The conflict should only really appear if they do increase productivity, and you refuse to use them, resulting in less productivity than your peers.
While it should be easy to point out where this helps, it very much is not in reality because AI accelerates execution on ideas, but corporations nearly always suck much more at deciding which ideas to actually implement in the first place.
I predict that the longer this goes on, the more useless, untested half-features will be stuffed into software and the more bloated "fall back" implementations full of duplicated spaghetti code will exist.
If the tools don't stick around because it's too cost prohibitive to keep using them, we're going to be cleaning up after the bots for a decade.
It's been a boon for personal slopjects for me. But that's because I could never find time for execution in the past. Now I just have the (free tier) AI slop up my ideas.
Sure, but not at this speed. The bots can churn out a mountain of non-sense that does not work faster than people can review it and the bots themselves will lie to you and say "it's all implemented".
For people who have clear ideas of what to implement but struggle to find the time, this is a big gift. You can work hand-in-hand with the bot and say "nope, not that, this" until it implements what you had in mind. For aimless corporations with "ideation" meetings who cannot stop coming up with terrible ideas that none of their customers want, it'll hasten the process of them making their software worse over time.
That's exactly what I'm seeing at my current company.
That's a fair point, but it's not an issue with AI; it's an issue with corporate culture. Corporate culture can and does change, especially with advances in technology, but there will be a churn period where it's chaotic and mistakes are made.
I agree with that as well. A lot of the problem with my current company comes straight from the executive leadership level. I'm afraid that the culture will only change when they change (or more likely, the company will eventually just go bust).
They bought the lie that AI will replace all of software engineering, whereas I see the picture more like this:
A CEO that thinks that they're going to develop all of the software, even with Claude code, is nuts. They simply do not have the necessary skill set to run a software project even if 100% of the hands-on programming is done by AI. They are not going to be sitting there telling a machine to move things around on a web app. They are going to believe the bot when it says that "it is implemented".
In this, I think we more-or-less agree; I just don't see that as a fault with AI, nor as a reason not to continue to develop/adopt AI.
And maybe your point is what Doctorow was trying to make all along, but he pushed too far in the other direction? Even now, Code Generation is a useful tool, as long as it's used as only a tool by someone who knows what they're doing.
And maybe your point is what Doctorow was trying to make all along, but he pushed too far in the other direction? Even now, Code Generation is a useful tool, as long as it’s used as only a tool by someone who knows what they’re doing.
In this piece — which I read via RSS feed a number of weeks ago before it was published in this medium — he is writing about what most peoples' experience is in a company where they have decided to "do AI", and what most CEOs think about when they think about "doing AI".
This usually comes in the form of a company chatbot or "agentic workflow", and in the vast majority of cases these things are very much not helpful and can actively be annoying because attention is paid to developing these things when more practical and useful features could be developed instead (see: https://ludic.mataroa.blog/blog/i-will-fucking-piledrive-you-if-you-mention-ai-again/).
In other pieces, he discusses — using what I would call sort of esoteric terms that he often defines inline — people in saner places that get to choose how and why to use AI to assist with their jobs. But that's not the majority of people's experiences and that is certainly not what CEOs are often talking about.
I think he's being somewhat hyperbolic in this particular piece, and maybe that's due to the amount of "AI is changing everything" or "AI has changed everything" that is appearing in LinkedIn / X posts everywhere, when it's difficult for most to even name a single thing that the chatbot has spit out that has improved lives, and the vendored chatbot attached to an existing piece of software (which is mostly what people end up doing when they "do AI" at a company) is completely useless.
If I take myself as an example, he's largely right that I have to play this game with internal development teams that come up with "agentic workflows" and try to get me to use them to do my job when it's a lot easier and better to just....use Claude code myself.
AI hasn't "changed everything". The only thing it's really done so far is produce a lot of chatbots and agentic workflows that aren't very useful. It remains to be seen if: (1) it can ever be made to work more efficiently, (2) if you can ever actually run a profitable business building or running a "neocloud", and (3) what the broader effects on software will be from mass usage of this technology.
The early signals on all of these very real concerns (not to mention others such as environmental, cultural, and economic impact) are not very positive.
[–]melfie@lemmy.zip12 points3 days ago* (last edited 3 days ago)
(1 children)
LLMs are like a dishwashers. You could wash all the dishes yourself and probably get them cleaner in less time, but it’s useful to let a machine do the work, even I though it’s mandatory inspect every single dish to make sure the machine got them clean enough and re-wash a certain percentage of them. Dishwashers are useful, but the world wouldn't end if we didn’t have them. They also have the benefit of using less water than when do them yourself, which certainly isn’t the case with LLMs.
In the same line of thinking, this is why I hand wash my car, because the automatic car wash either does a bad job (touchless) or will scratch the paint up all over (brushes). Many people don't care very much about their cars though, so why put in the effort?
I find unreliable tools to be one of the most infuriating parts of my job, and unfortunately my entire job has effectively pivoted to spending all day babysitting an AI that frequently ignores instructions and can't learn without a ton of expensive fine-tuning training.
I don't let AI touch any of my personal code I care about, and with how much of the code at work is written by AI, it's pretty demoralizing. Why put in any effort designing something if it's just going to get blown away by a coworker's agent the next day?
Arguing with the AI over why its code review is wrong is also a whole other part of my day now...
I work at a sales-first (read: no accountability) software company, ran by inept nepo-babies and a hostile VC. I frequently have to completely re-do all of the sales engineering work when a new project starts, because they refuse to standardize or talk to each other.
After enough time doing this shit by hand, I took my best examples from previous projects and had an agent "fix the errors based on the conventions I established over here". Instead of going line by line on these big serialized data formats now, I do about 10min of checking the results and editing down the change log.
It's wack that I have to re-do someone else's job still, but at least I can force some version of standardization without killing myself on the tedious bits.
I work in government and part of my job is writing memos or documents that nobody will ever read but that some congressional mandate requires me to have on file. I absolutely offload that to AI so I can do my real job.
With ownership being as concentrated as it is now (more concentrated than during the guilded robber baron age), naturaly, most of the benefit flows to the biggest owners, and AI seems poised to deepen the wealth inequality further.
In a scenario without the insane wealth concentration, and with a dignified and decent economic floor being guaranteed universally, I would be in favor of any AI that does not burn our planet to a crisp and stink up the neighborhood with the gas turbine exhaust.
So in our world as it is, I have to be agaisnt the AI for the foreseeable future.
The other question Suresh implicitly raises is: "How can you reconcile the failure of AI in the enterprise with the individual claims of skilled technologists who insist that AI is helping them do great work?"
Part of the problem is AI isn’t a literal thing with a fixed definition. It’s more of a marketing term that translates into “I want you to buy this thing”. So some things are considered AI that are legitimately useful and others are not and then there’s the debate if wether it’s because it really is AI or if it is and AI just sucks.
OK, but the point still stands if you allow that: It has become impossible to tell managers mesmerised by artificial intelligence that the tools are often not, in fact, helpful.
Sure, although I would phrase it I think a bit more pointedly: "it has become impossible to tell managers mesmerized by artificial intelligence that the tools are not, in fact, capable of what they imagine they are capable of."
This points, rightly, at it being a failure on the part of the managers - not artificial intelligence. And God knows that's spot fucking on.
It depends on the tool to be honest. If it's Claude code and you're a programmer, sure that's helpful. But often it's an "agentic workflow engine" that's been developed in house that's complete garbage, or a chatbot that doesn't know anything telling you that it can't answer your question that was put together by your company. These custom tools are almost always not helpful.
Doctorow knows this as well, he writes about this crap constantly and has broken it down by user type in other pieces.
If you're already experienced developer and you use it skillfully, validate produced code it can help.
If you aren't (and unfortunately everyone thinks they are better than they actually are), it actually can do the opposite, it can help generate a lot of junk code.
Now when working in a team usually majority of people aren't that great developers typically there might be one or two star developers. The problem is that the other people will still use AI and generate MRs. Reviewing those is extremely time consuming and no one wants to do it. It's weird to say what's exactly wrong with those MRs they seem to do things but they seem to do things in a more complicated way.
The thing is that no one wants to review those MRs, everyone is afraid to point AI slop, so the quality of code goes down and even the people who previously were good are getting lost in the code themselves.
This is stupid. The tools are helpful. Overhyped? Sure. But to pretend they are in no way helpful is just wrong.
I have tons of random receipts that come in every month that need to be captured, memoed, categorized and sent off to finance.
I made python to read image/pdf/whatever to text, easy.
I regex the value out, hard and fragile
I try to pull the vendors name out, just not reliable
Category... nearly impossible so i need to make some form of memory system to remember once I do it.
Python renames the file with input if it needs it and provides the meta
OR
python to text because it's effciient
api call to Ollama and let my old 2070 work it out. (highly reliable)
python renames the file and provides the meta
It's small, low power, hard to do with code, basically the perfect use case. This is a good use of AI
Go Rewrite FFMPEG in Rust.... that's a bad use of AI.
There's a lot of people out there using it in ways that cost a lot more than human eyes and have horrible societal and environmental impacts.
There's a lot of people using it for dictation, document triage and basic scripting where it has great advantages and isn't making the world a worse place.
His article is at odds with a great deal of his book. I wonder if this isn't just a grab to get hardcore anti-ai to buy it.
Nothing is helpful until you need help. The fact that you think AI is helpful for you don't have to force me to use AI. If you pay me $100k+ per year and you force me to use your tools to do my job why you even hired me ? To force this cult on me or to do the job ?
It's pretty normal for an employer to dictate what tools and applications an employee uses. If you prefer gitlab but your employer requires teamcity, you don't really get a say, right?
However, if you think you can meet your deadlines without using a code generating AI tool, then don't use it. Ideally, if they are as useless as you imply, no one will be able to tell whether you're using it. The conflict should only really appear if they do increase productivity, and you refuse to use them, resulting in less productivity than your peers.
Company will be able to tell if you're using it because companies behind sota models come with monitoring. You will have meeting with hr and your manager when you will be forced to use it even if you meet quotas. They will argument it that maybe you can do more and increase your normal quota with expected ai usage increase in productivity even if you had best productivity in team without ai and your productivity stays the same. Suddenly you will be under performing because you are refusing to use ai so you will be first to fire even if you are best employee. That's how corporations work. They are monitoring usage because it costs them money. For big corporations they pay upfront to get discounts. Company also make many trainings and meetings to encourage everyone use AI models they pay for but nobody wanted.
While it should be easy to point out where this helps, it very much is not in reality because AI accelerates execution on ideas, but corporations nearly always suck much more at deciding which ideas to actually implement in the first place.
I predict that the longer this goes on, the more useless, untested half-features will be stuffed into software and the more bloated "fall back" implementations full of duplicated spaghetti code will exist.
If the tools don't stick around because it's too cost prohibitive to keep using them, we're going to be cleaning up after the bots for a decade.
It's been a boon for personal slopjects for me. But that's because I could never find time for execution in the past. Now I just have the (free tier) AI slop up my ideas.
Which happened without AI, too.
Remember that AI, in whatever form or field, only has to be better than the average human in the field, to be useful to a company project.
Sure, but not at this speed. The bots can churn out a mountain of non-sense that does not work faster than people can review it and the bots themselves will lie to you and say "it's all implemented".
For people who have clear ideas of what to implement but struggle to find the time, this is a big gift. You can work hand-in-hand with the bot and say "nope, not that, this" until it implements what you had in mind. For aimless corporations with "ideation" meetings who cannot stop coming up with terrible ideas that none of their customers want, it'll hasten the process of them making their software worse over time.
That's exactly what I'm seeing at my current company.
That's a fair point, but it's not an issue with AI; it's an issue with corporate culture. Corporate culture can and does change, especially with advances in technology, but there will be a churn period where it's chaotic and mistakes are made.
I agree with that as well. A lot of the problem with my current company comes straight from the executive leadership level. I'm afraid that the culture will only change when they change (or more likely, the company will eventually just go bust).
They bought the lie that AI will replace all of software engineering, whereas I see the picture more like this:
https://www.normaltech.ai/p/why-ai-hasnt-replaced-software-engineers
A CEO that thinks that they're going to develop all of the software, even with Claude code, is nuts. They simply do not have the necessary skill set to run a software project even if 100% of the hands-on programming is done by AI. They are not going to be sitting there telling a machine to move things around on a web app. They are going to believe the bot when it says that "it is implemented".
In this, I think we more-or-less agree; I just don't see that as a fault with AI, nor as a reason not to continue to develop/adopt AI.
And maybe your point is what Doctorow was trying to make all along, but he pushed too far in the other direction? Even now, Code Generation is a useful tool, as long as it's used as only a tool by someone who knows what they're doing.
In this piece — which I read via RSS feed a number of weeks ago before it was published in this medium — he is writing about what most peoples' experience is in a company where they have decided to "do AI", and what most CEOs think about when they think about "doing AI".
This usually comes in the form of a company chatbot or "agentic workflow", and in the vast majority of cases these things are very much not helpful and can actively be annoying because attention is paid to developing these things when more practical and useful features could be developed instead (see: https://ludic.mataroa.blog/blog/i-will-fucking-piledrive-you-if-you-mention-ai-again/).
In other pieces, he discusses — using what I would call sort of esoteric terms that he often defines inline — people in saner places that get to choose how and why to use AI to assist with their jobs. But that's not the majority of people's experiences and that is certainly not what CEOs are often talking about.
I think he's being somewhat hyperbolic in this particular piece, and maybe that's due to the amount of "AI is changing everything" or "AI has changed everything" that is appearing in LinkedIn / X posts everywhere, when it's difficult for most to even name a single thing that the chatbot has spit out that has improved lives, and the vendored chatbot attached to an existing piece of software (which is mostly what people end up doing when they "do AI" at a company) is completely useless.
If I take myself as an example, he's largely right that I have to play this game with internal development teams that come up with "agentic workflows" and try to get me to use them to do my job when it's a lot easier and better to just....use Claude code myself.
AI hasn't "changed everything". The only thing it's really done so far is produce a lot of chatbots and agentic workflows that aren't very useful. It remains to be seen if: (1) it can ever be made to work more efficiently, (2) if you can ever actually run a profitable business building or running a "neocloud", and (3) what the broader effects on software will be from mass usage of this technology.
The early signals on all of these very real concerns (not to mention others such as environmental, cultural, and economic impact) are not very positive.
Honestly if they hired someone who refuses to use AI in 2026 it’s on them.
LLMs are like a dishwashers. You could wash all the dishes yourself and probably get them cleaner in less time, but it’s useful to let a machine do the work, even I though it’s mandatory inspect every single dish to make sure the machine got them clean enough and re-wash a certain percentage of them. Dishwashers are useful, but the world wouldn't end if we didn’t have them. They also have the benefit of using less water than when do them yourself, which certainly isn’t the case with LLMs.
In the same line of thinking, this is why I hand wash my car, because the automatic car wash either does a bad job (touchless) or will scratch the paint up all over (brushes). Many people don't care very much about their cars though, so why put in the effort?
I find unreliable tools to be one of the most infuriating parts of my job, and unfortunately my entire job has effectively pivoted to spending all day babysitting an AI that frequently ignores instructions and can't learn without a ton of expensive fine-tuning training.
I don't let AI touch any of my personal code I care about, and with how much of the code at work is written by AI, it's pretty demoralizing. Why put in any effort designing something if it's just going to get blown away by a coworker's agent the next day?
Arguing with the AI over why its code review is wrong is also a whole other part of my day now...
I'm not necessarily suggesting Doctorow is correct with this assertion, but on a macro scale what productivity gains will generate AI provide?
Yes there's a few skills it's good at coding, medical research, and image recognition being a few.
The genuine question is: has this improved everyone's quality of life?
I work at a sales-first (read: no accountability) software company, ran by inept nepo-babies and a hostile VC. I frequently have to completely re-do all of the sales engineering work when a new project starts, because they refuse to standardize or talk to each other.
After enough time doing this shit by hand, I took my best examples from previous projects and had an agent "fix the errors based on the conventions I established over here". Instead of going line by line on these big serialized data formats now, I do about 10min of checking the results and editing down the change log.
It's wack that I have to re-do someone else's job still, but at least I can force some version of standardization without killing myself on the tedious bits.
I work in government and part of my job is writing memos or documents that nobody will ever read but that some congressional mandate requires me to have on file. I absolutely offload that to AI so I can do my real job.
What a grotesque job this is.
With ownership being as concentrated as it is now (more concentrated than during the guilded robber baron age), naturaly, most of the benefit flows to the biggest owners, and AI seems poised to deepen the wealth inequality further.
In a scenario without the insane wealth concentration, and with a dignified and decent economic floor being guaranteed universally, I would be in favor of any AI that does not burn our planet to a crisp and stink up the neighborhood with the gas turbine exhaust.
So in our world as it is, I have to be agaisnt the AI for the foreseeable future.
The later section addresses this
Part of the problem is AI isn’t a literal thing with a fixed definition. It’s more of a marketing term that translates into “I want you to buy this thing”. So some things are considered AI that are legitimately useful and others are not and then there’s the debate if wether it’s because it really is AI or if it is and AI just sucks.
OK, but the point still stands if you allow that: It has become impossible to tell managers mesmerised by artificial intelligence that the tools are often not, in fact, helpful.
Sure, although I would phrase it I think a bit more pointedly: "it has become impossible to tell managers mesmerized by artificial intelligence that the tools are not, in fact, capable of what they imagine they are capable of."
This points, rightly, at it being a failure on the part of the managers - not artificial intelligence. And God knows that's spot fucking on.
It depends on the tool to be honest. If it's Claude code and you're a programmer, sure that's helpful. But often it's an "agentic workflow engine" that's been developed in house that's complete garbage, or a chatbot that doesn't know anything telling you that it can't answer your question that was put together by your company. These custom tools are almost always not helpful.
Doctorow knows this as well, he writes about this crap constantly and has broken it down by user type in other pieces.
It is a double edged sword.
If you're already experienced developer and you use it skillfully, validate produced code it can help.
If you aren't (and unfortunately everyone thinks they are better than they actually are), it actually can do the opposite, it can help generate a lot of junk code.
Now when working in a team usually majority of people aren't that great developers typically there might be one or two star developers. The problem is that the other people will still use AI and generate MRs. Reviewing those is extremely time consuming and no one wants to do it. It's weird to say what's exactly wrong with those MRs they seem to do things but they seem to do things in a more complicated way.
The thing is that no one wants to review those MRs, everyone is afraid to point AI slop, so the quality of code goes down and even the people who previously were good are getting lost in the code themselves.