Kent Beck 🌻

17.1K posts

Kent Beck 🌻 banner
Kent Beck 🌻

Kent Beck 🌻

@KentBeck

Programmer, coach coach, artist, pokerist, singer/guitarist. Learning to be me. Blogging at https://t.co/x9OAJDl8v9. Mastodon: @[email protected]

San Francisco, CA Katılım Ekim 2008
840 Takip Edilen183.6K Takipçiler
Sabitlenmiş Tweet
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
I am continuing work on "Tidy First? An Exercise In Empirical Software Design" as a @substack . No paid tier yet, but that's where book chapters will be appearing. Sign up here: kentbeck.substack.com.
English
20
51
318
0
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
@davefarley77 It's in the toolbox & easier with the genie. It tends to be slow so I use it less frequently than just running tests. If computation was free I'd be continuously running it in the background, having it spit out new tests for corner case.
English
2
2
17
3.5K
Dave Farley
Dave Farley@davefarley77·
Interested to hear thoughts on mutation testing... have you tried it? What's your experience?
English
17
0
17
7.4K
Joe Hunt
Joe Hunt@JosephBHunt·
@KentBeck I'll always listen and respect your opinion, but this does look a bit like a recently unemployed programmer talking to a crowd of homeless around a burning barrel of trash. Still, I'm listening to the podcast.
English
1
0
2
94
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
10 years from now, who even knows what part of software development will still be a human activity? Nobody knows. But some people are staying ahead instead of catching up. Still Burning episode 1 now live.
English
6
14
81
12K
Scott Wolchok
Scott Wolchok@ScottWolchok·
@KentBeck Tried to add the pod on Overcast, couldn’t find it. Intentionally Spotify-exclusive?
English
1
0
0
255
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
Augmented development is such an opportunity for improvement. The genie will point to exactly where you have unnecessary friction in development. You do need to be listening, though.
English
2
3
33
6.4K
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
"remove duplicate work is going to be even more important" -- I agreed with the rest of this thoughtful & carefully observed post but when in Explore mode, duplicate work is useful because 1) it reduces latency at a time of high cost of delay and 2) you never know what you're going to discover.
Allie K. Miller@alliekmiller

Yesterday, I met with Anthropic and OpenAI and Google. (Separately, of course.) And while the conversations were largely confidential, I do want to share some aggregated reflections on the day as well as general SF takeaways. ⬇️ 1) Competitive advantage as a solo practitioner really does come from taking action and finding an area with a bit of friction and doubling down. Ex: memory management right now isn’t perfect, but allocating an hour to improving that system gives you a ton of leverage over others 2) SF continues to be the number one place for AI work. I know that’s not surprising. I would put New York at a healthy second place. SF tends to be more about crazy agent experiments for the thrill of capability and discovery and NYC tends to be more about kinda crazy agent experiments to find new ways to make money. Not saying either is better. But I met several people renting two apartments to straddle these worlds. You want the frontier of SF and enterprise insights of NYC. It’s one reason I travel between them so much. 3) All AI labs want to hear more from people. All of them. What are you using it for, what do you like, what do you hate, what do you need. Users have a TON of power on the direction of these tools. Keep testing and tweeting at them!! 4) There is very clearly a third customer cohort that is bubbling and underserved. It’s not developers…it’s not the business professional basic users…it’s builders. Everyone can build now. It’s marketing and sales folks vibe coding. It’s legal folks building complex skills. It’s a finance expert building a side project. This is a really undertapped customer base. They feel the Cursors of the world are too complex and doc summarization tools of the world are too basic. 5) Not sure if it was just sample size, but far fewer people were wearing tech gear compared to when I lived in SF. Everyone was still dressed casually, but I used to see Splunk and Optimizely and Slack and VC gear everywhere. People seem more in stealth swag now. 6) We may soon have our world model moment. 7) Speed of iteration and shipping is faster than I’ve ever seen. We see the nonstop drops from Anthropic. We see that because of scale, providers can get a much faster feedback loop of products or features that aren’t hitting. A lot of 2025 was experimentation, but ever since the OpenClaw moment over the holidays, the releases from all three labs have been more concentrated on…things that sorta look and feel like OpenClaw. 8) Small teams can pull off more than ever before. Small teams are the powerhouses of innovation right now. This means that finding new ways to share knowledge, break silos, and remove duplicate work is going to be even more important. AI agents functioning as actually teammates that support an entire system is key. 9) Build more Skills. Build better Skills. 10) Misinformation on AI tools and leaks spread FAST. I’ve seen so many fake stories on these AI labs. Your company needs to actually TEST these tools on your actual use cases to know which models and tools are best and you need to not make large-scale snap decisions based on a rumor of a rumor of a rumor. We will see more volatility. Plan for it. 11) You can feel the seriousness of this moment. Even during random conversations I had in line at a cafe. Lots of folks worried about job loss and lack of meaning. 12) Mac minis were sold out ;)

English
1
5
51
21.1K
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
All these “30% unemployment for new grads” predictions make a critical false assumption—they assume the number & composition of employers remains static. We’re going to see an explosion of new ventures, some of which will turn into new employers. My gut is that these new employers will more than absorb the people laid off by current employers.
English
17
8
98
15.1K
Daniel Junior
Daniel Junior@jrzabott·
Hey @KentBeck , I think of you a lot as a voice and a mind I respect and look up to. I was talking to Claude and(screenshot). I've felt a little shitty and happy at the same time. I was wondering if you ever felt like this, knew somebody like this or wrote about handling it?
Daniel Junior tweet media
English
1
0
0
1.1K
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
A new podcast, hosted by yours truly, coming soon...
English
5
4
44
6.7K
Peter Thomson
Peter Thomson@PeterJThomson·
@staysaasy Hey @unclebobmartin & @KentBeck Can we bring back XP, or multi-player somehow into modern work? It might need new tooling, but there has to be a human-to-human version of modern Pair Programming? Maybe like a group chat mode for Agentic Programming?
English
1
0
1
178
staysaasy
staysaasy@staysaasy·
Has anyone tried pair prompting? I feel like that should be a thing. Pair coding was a common practice where one person would code and another would watch, and they’d share ideas and work together on a problem. I think you could do the same thing with AI coding to great effect. But I’m not sure I’ve heard anyone do it. Imagine rapidly iterating on QA, checking results, switching between agents rapidly as a team.
English
11
1
29
3.5K
John Crickett
John Crickett@johncrickett·
TDD changed how I write software. Agentic engineering is changing it again. I don't think the classic red-green-refactor loop of TDD makes sense when an AI agent is writing the code. I've been a proponent of TDD since I read @KentBeck's XP Explained. I roughly followed what he describes as "Canon TDD": 1. Write a list of the test scenarios you want to cover. 2. Turn exactly one item on the list into an actual, concrete, runnable test. 3. Change the code to make the test (and all previous tests) pass, adding items to the list as you discover them. 4. Optionally refactor to improve the implementation design. 5. Until the list is empty, go back to #2. I say roughly, as I was never good at sticking to #2. I'd turn two or three test scenarios into runnable tests at a time, often using table-driven or parameterised tests. This process adds value when a human is writing code. But when an AI agent is doing the writing, I think Test First Development is currently a better approach. We can define all the test cases, let the AI write all the tests, then let the AI write the code to pass them. Doing each step one at a time would be a much more expensive way of using the agent. There would be far more tool calls, far more roundtrips to the inference engine, and it would consume a lot more tokens. Then there's the difference between the agent and an engineer. The agent isn't necessarily going to refactor like a human engineer would. I don't think we lose much from this change. We can still guide it after each feature to evolve the design. We can still iterate quickly and get fast feedback on the design and functionality. Are you still doing red-green-refactor when the agent is doing the typing?
English
15
4
85
14.3K
alex
alex@kurko·
@GergelyOrosz @KentBeck Can vibe coding be categorized as pair programming? 🙃 I think it can, right?
English
1
0
0
86
Gergely Orosz
Gergely Orosz@GergelyOrosz·
Amusing - I'm hearing a comeback of XP (Extreme Programming) practice. In the early 2000s these used to be popular (championed by @KentBeck). Then died down. They are now surging again. XP practices like small releases, frequent integration, and constant customer input!
English
49
28
489
72.2K
Corn Woman 🌽
Corn Woman 🌽@WomanCorn·
@rkobylinski @KentBeck @martinfowler I also need the ability to see that this is the change that was made without reading all the diff's and to confirm that the change i'm looking at is in fact just a rename
English
1
0
2
173
Rafał Kobyliński
Rafał Kobyliński@rkobylinski·
We should revisit automating safe refactorings not only in IDEs but also via CLI or MCP. Why use a risky, non-deterministic LLM to do a deterministic tool's job? @KentBeck @martinfowler
Rafał Kobyliński@rkobylinski

@karpathy I wonder which language would be best for both automated but deterministic code refactor (possibly via CLI/MCP) and LLM based output.

English
1
1
11
3.6K
Kent Beck 🌻
Kent Beck 🌻@KentBeck·
I've spent the last year deep in augmented coding — how genies change what programmers do & don't do. Now I'm curious what that looks like in govtech, where shipping isn't theoretical. Speaking at @Rise8's ShipSummit, Park City, March 31 - April 2.
Kent Beck 🌻 tweet media
English
3
7
45
6.5K