> the productivity boost these things can provide is exhausting . What I personally find exhausting is Simon¹ constantly discovering the obvious. Time after time after time it’s just “insights” every person who smoked one blunt in college has arrived at. Stop for a minute! You don’t have to keep churning out multiple blog posts a day, every day. Just stop and reflect . Sit back in your chair and let your mind rest. W…
edited: quote misattributed
AI doesn’t reduce work, it intensifies it
141–150 of 329 posts
Re: AI doesn’t reduce work, it intensifies it
#142> the productivity boost these things can provide is exhausting . What I personally find exhausting is Simon¹ constantly discovering the obvious. Time after time after time it’s just “insights” every person who smoked one blunt in college has arrived at. Stop for a minute! You don’t have to keep churning out multiple blog posts a day, every day. Just stop and reflect . Sit back in your chair and let your mind rest. W…
I find Simon’s blog and TILs to be some of the highest signal to noise content on the internet. I’ve picked up an incredible number of useful tips and tricks. Many of them I would not have found if he did not share things as soon as he discovered something that felt “obvious.” I also love how he documents small snippets and gists of code that are easy to link to and cross-reference. Wish I did more of that myself.
You don’t know that. For all you know, your life would’ve been richer if you’ve read those thoughts after they’ve been left to stew for longer. For all you know, if that happened you would’ve said “most” instead of “many”. Or maybe not, no one can say for sure until it happens
> that felt “obvious.”
It’s not about feeling obvious. There is value in exploring obvious concepts when you’ve thought about them for longer, maybe researched what others before you had to say on the matter, and you can highlight and improve on all of that. Everyone benefits from a thoughtful approach.
> I’ve picked up an incredible number of useful tips and tricks. (…) I also love how he documents small snippets and gists of code that are easy to link to and cross-reference.
That is (I think clearly, but I may be wrong) not what I’m talking about. A code snippet is very far removed in meaning from a human insight. What I wrote doesn’t just concern Simon’s readers, but Simon as a person. Being constantly “on” isn’t good, it leads to exhaustion (as reported), which leads to burnout. While my first paragraph in the previous comment was a criticism, it was merely an introduction to the rest of the post which was given in empathy. I want us all to do and be better.
Re: AI doesn’t reduce work, it intensifies it
#143Earlier quoted context omitted.
> percentage of good, well planned, consistent and coherent software is going to approach zero So everything stays exactly the same?
> So everything stays exactly the same? No, we get applications so hideously inefficient that your $3000 developer machine feels like it it's running a Pentium II with 256 MB of RAM. We get software that's as slow as it was 30 years ago, for no reason other than our own arrogance and apathy.
Except some very well maintained software, some of the mundane things we do today waste so much resources it makes me sad.
Heck, the memory use of my IDE peaks at VSCode's initial memory consumption, and I'd argue that my IDE will draw circles around VSCode while sipping coffee and compiling code.
> for no reason other than our own arrogance and apathy.
I'll add greed and apparent cost-reduction to this list. People think they win because they reduce time to market, but that time penalty is delegated to users. Developers gain a couple of hours for once, we lose the same time every couple of days while waiting our computers.
Once I have read a comment by a developer which can be paraphrased as "I won't implement this. It'll take 8 hours. That's too much". I wanted to plant my face to my keyboard full-force, not kidding.
Heck, I tuned/optimized an algorithm for two weeks, which resulted in 2x-3x speedups and enormous memory savings.
We should understand that we don't own the whole machine while running our code.
Re: AI doesn’t reduce work, it intensifies it
#144The worst part is that it’s so convincing: not only does everyone who can’t make it work feel gaslit about it, but some people even pretend that it works for them so they don’t feel like they’re missing out.
I remember the last time this happened and people were convinced (for like 2 years) that a gif of an ape could somehow be owned and was worth millions of dollars.
Re: AI doesn’t reduce work, it intensifies it
#145Is a blog reposting other content worth its own post? Previous discussion of the original article: https://news.ycombinator.com/item?id=46945755
Re: AI doesn’t reduce work, it intensifies it
#146Earlier quoted context omitted.
> So everything stays exactly the same? No, we get applications so hideously inefficient that your $3000 developer machine feels like it it's running a Pentium II with 256 MB of RAM. We get software that's as slow as it was 30 years ago, for no reason other than our own arrogance and apathy.
Do not insult P-II w/256 MB of RAM. That thing used to run this demo[0] at full speed without even getting overwhelmed. Except some very well maintained software, some of the mundane things we do today waste so much resources it makes me sad. Heck, the memory use of my IDE peaks at VSCode's initial memory consumption, and I'd argue that my IDE will draw circles around VSCode while sipping coffee and compiling code. >…
Thanks for sharing the demo!
Re: AI doesn’t reduce work, it intensifies it
#147Earlier quoted context omitted.
I find Simon’s blog and TILs to be some of the highest signal to noise content on the internet. I’ve picked up an incredible number of useful tips and tricks. Many of them I would not have found if he did not share things as soon as he discovered something that felt “obvious.” I also love how he documents small snippets and gists of code that are easy to link to and cross-reference. Wish I did more of that myself.
> Many of them I would not have found if he did not share things as soon as he discovered something You don’t know that. For all you know, your life would’ve been richer if you’ve read those thoughts after they’ve been left to stew for longer. For all you know, if that happened you would’ve said “most” instead of “many”. Or maybe not, no one can say for sure until it happens > that felt “obvious.” It’s not about feel…
That's exactly what I try to do.
I wrote more about my approach to that here: https://simonwillison.net/2024/Dec/22/link-blog/#trying-to-a...
Re: AI doesn’t reduce work, it intensifies it
#148Earlier quoted context omitted.
> You don’t have to keep churning out multiple blog posts a day, every day. How do you know that? You don't think he's being paid for all this marketing work?
I'm paid by my GitHub sponsors, who get a monthly summary of what I've been writing about on the basis that I don't want to put a paywall on my content but I'm happy for people to pay me to send them less stuff. I also make ~$600/month from the ads on my site - run by EthicalAds. I don't take payment to write about anything. That goes against my principals. It would also be illegal in the USA (FTC rules) if I didn't…
Re: AI doesn’t reduce work, it intensifies it
#149Re: AI doesn’t reduce work, it intensifies it
#150I feel agentic development is a time sink. Previously, I'd have an idea, sit on it for a while. In most cases, conclude it's not a good idea worth investing in. If I decided to invest, I'd think of a proper strategy to approach it. With agentic development, I have an idea, waste a few hours chasing it, then switch to other work, often abandoning the thing entirely. I still need to figure out how to deal with that, fo…
Now I sit on an idea for a long time, writing documentation/specs/requirements because I know that the code generation side of things is automated and effortlessly follows from exhaustive requirements.