gregdoesit
Joined 11 years ago
Joined 11 years ago
In April 2025, Zitron wrote [1] "I am sick and tired of everybody pretending that generative AI is the next big thing." This was at the time when AI coding tools had already gone "mainstream" with devs, and pretty much everyone was using tools like GH Copilot, Cursor, or something similar.
So I replied with this observation, saying how, at least within software engineers, AI is being adopted faster than any technology before [2]. To stay objective, obviously I brought receipts: sharing how, based on an older survey I ran, ~75% of devs in that survey said they used AI coding tools. Zitron made fun of the small sample size (216 people), blocked, and pretended like AI had zero PMF anywhere in the world.
I stopped taking him seriously since then. And I'm wondering ever since: does he deliberately only look at numbers and facts that he can tell the AI doomer story around? Or is it more that he finds that there's not many people who are "informed sceptics", and decided to play this role?
[1] https://x.com/edzitron/status/1916903519594156407?s=20
[2] https://x.com/GergelyOrosz/status/1916906481686921483?s=20
It’s an interesting question if the decline would have happened regardless of LLMs, just slower?
[1] An annotated visualization of the same data I did: https://blog.pragmaticengineer.com/are-llms-making-stackover...
Interestingly, this was my exact experience when working with a publisher (Manning, in my case), and it was the main reason I decided to part ways when writing my book (The Software Engineer’s Guidebook). While I did appreciate publisher’s desire to please a broader crowd by pushing a style they thought would broaden the appeal: but doing so makes technical books less attractive, in my view. And even less motivation to write!
In my case, self publishing worked out well enough with ~40,000 copies sold in two years [1], proving the publisher’s feedback wrong, and that you don’t need to dumb down technical books, like this specific publisher would have preferred to do so.
Even if it wouldn’t have worked out: what’s the point writing a book where there’s little of the author (you!) left in it. Congrats to OP for deciding to stick to your gut and write the book you want to write!
[1] https://newsletter.pragmaticengineer.com/p/the-software-engi...
From the legislation:
“ Section 174(c)(2) provides that the required § 174 method does not apply to any expenditure paid or incurred for the purpose of ascertaining the existence, location, extent, or quality of any deposit of ore or other mineral (including oil and gas).”
Is there an explanation how software developers creating software for oil and gas companies are different than for any other industry?
Or can we assume that the oil and gas industry managed to (yet again!) have its lobbyists where it mattered?
I did what seemingly no other publication reporting on it did: signed up for Klarna, bought one item and used this bot.
I was... not impressed?
Klarna's "AI bot" felt like the "L1 support flow" that every other company already has in-place: without AI! Think like when you have a problem with your UberEats order and 80% of cases are resolved without a human interaction (e.g. when an item is missing for your item.)
I walked through the bot's capabilities [1] and my conclusion was that pretty much every other company did this before (automating the obvious support cases.) The real question should have been: why did Klarna not do it before? And when it did, why did it build a wonky AI bot, instead of more intuitive workflows than other companies did?
My sense is that Klarna really wants to be seen as an "AI-first tech company" when it goes public, and not a "buy now pay later loan company" because AI companies have higher valuations even with the same revenue. But at its core, Klarna is a finance or ecommerce-related company: an not much to do with AI (even if it uses AI tools to make its business more efficient - regardless of whether it could use non-AI tools to get the same thing done)
This is a full-remote startup and they have now added a mandatory in-person interview to their recruitment loop.
Amusingly, in their case, using local job boards did not help: they got candidates pretending to from Poland or Serbia, yet not speaking the language.
A little sad to see how each episode like this casts more doubt and uncertainty into full-remote interviewing.