Simon Wdowiak

Managing Director @Accenture EMEA. #tech #innovation #leadership

[Simon Wdowiak @wdowiak]

@thekitze PETG?

[Simon Wdowiak @wdowiak]

Tell me more...

[bleach breakfast (salome) 🏳️‍⚧️ @sirhanseranwrap]

behold the pierogi pizza!

[Shaun Davis @DataShaun]

Never forget what they took from you.

[Simon Wdowiak @wdowiak]

AI CLIs are bringing back serious ’90s vibes — and I’m absolutely loving it.

[Simon Wdowiak @wdowiak]

Andrej Karpathy (former Tesla AI Director and OpenAI co-founder) recently published detailed observations from months of intensive AI-assisted development. He has moved from cautious skepticism to declaring this a "phase shift" in software engineering.

What strikes me most from his findings:

1. The 80/20 inversion happened in weeks, not years. Karpathy went from 80% manual coding / 20% AI assistance in November to the complete reverse by December.

2. The role is inverting from "writer" to "commander." Generalists who can specify outcomes clearly and review work critically are becoming more valuable than narrow specialists.

3. The stamina bottleneck is broken. Features that used to get cut for budget or time constraints become feasible.

4. The 10x performance gap is widening, not closing. AI amplifies existing skill differences. This will show up in productivity metrics and eventually in compensation expectations.

5. "Slopacolypse" is coming. 2026 will see platforms flooded with low-quality AI-generated code and content. Quality assurance and trusted delivery become premium differentiators — anyone can generate volume now.

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Simon Wdowiak @wdowiak]

Aren't you terrified that your impolite behavior toward artificial intelligence today might result in a terminator targeting you in the future?

[Alvaro Cintas @dr_cintas]

New study shows being rude to AI makes it perform better.

Researchers tested modern LLMs with 250 prompts across 5 politeness levels (from Very Polite to Very Rude).

The results? Aggressive prompts outperformed polite ones significantly:
• Very Rude: 84.8% accuracy
• Very Polite: 80.8% accuracy

This contradicts older research that showed the opposite pattern. Something fundamentally shifted with newer model architectures.

The dataset covered math, science, and history questions. Each one rewritten in different tones and tested 10 times.

They tested this on ChatGPT-4o specifically, and noted earlier models (GPT-3.5, Llama-2) behaved completely differently.

[Simon Wdowiak @wdowiak]

@dr_cintas Aren't you terrified that your impolite behavior toward artificial intelligence today might result in a terminator targeting you in the future?

[Simon Wdowiak @wdowiak]

I have already viewed this movie, and it appears to be playing again.

[Anthony Pompliano 🌪 @APompliano]

Artificial intelligence is coming for every white collar job.

You are delusional if you think yours won’t be automated at some point.

[Simon Wdowiak @wdowiak]

@APompliano We dealt with this in the 90s, 00s, 10s and here it is again!

[Simon Wdowiak @wdowiak]

Hydration level: overachieved.

https://t.co/W6mDFmM4BT

[Simon Wdowiak @wdowiak]

https://t.co/LcvESSWB3j

[Simon Wdowiak @wdowiak]

"Consulting is at risk. AI can already do in a minutes what once took consultants weeks."

[Simon Wdowiak @wdowiak]

@Malka_Sargon @aaditsh Looks Like Magic

[Simon Wdowiak @wdowiak]

@james406 Show the coffee station!

[Simon Wdowiak @wdowiak]

@aaditsh https://t.co/ibYIkNrSN8

[Simon Wdowiak @wdowiak]

@thegarybrecka Would not post workout cold exposure negatively impact growth hormone levels?

[Simon Wdowiak @wdowiak]

@FitFounder @brian_drago_ No HRV boost in a day to day tracking (N=1).

[Simon Wdowiak @wdowiak]

@themgmtconsult @apollonator3000

[Simon Wdowiak @wdowiak]

@themgmtconsult Almost correct, but now analysts don't wear ties.