←
Tom Howlett2,322 posts
Tom Howlett avatar

Tom Howlett

@leantomato

AI Engineering Engagement @sonarsource. Exploring the AI coding quality challenge!

◷ Joined July 2009▧ 75 Photos and videos
Tom Howlett avatar
Tom Howlett@leantomato·21 May 2014

Present a good team with problems & they'll thrive on finding solutions. Ask them to implement your solution & they'll only find problems.

John Crickett avatar
⟳ Tom Howlett retweeted
John Crickett@johncrickett·Nov 11

AI isn't killing software engineering. Not even close. Instead it's exposing how much we've confused software engineering with writing code. Yes, coding is a fundamentally important part of the job, but it's only one part. Understanding what users need, figuring out what's worth building, making architectural decisions, and delivering software that actually solves problems are all part of software engineering. AI might change who, or what, writes the code. But that doesn't make those other skills less important. If anything, it makes them more important. In fact they're critical to stopping us spending a lot of time and effort building the wrong things. This clip is from a chat I had with Tom Howlett (@leantomato) on The Next Commit podcast. We talked about how AI agents are changing software engineering, why developers still need strong fundamentals, and the growing importance of human skills, engineering judgement, and taking responsibility for the software we ship. You can listen to the full episode here: thenextcommit.substack.com/p…

0:32
Simon Willison avatar
⟳ Tom Howlett retweeted
Simon Willison@simonw·Nov 10

When Anthropic release a new model it's always worth taking a look at their updated prompting guide - here's an entertaining tip to make Fable 5.2 less likely to be cautious in how it improves existing code: tell it "This codebase is yours" platform.claude.com/docs/en/…

Post attachment
Sonar avatar
⟳ Tom Howlett retweeted
Sonar@SonarSource·Nov 3

When an agent gets it wrong, do you fix the code or the process behind it? @slashBene, co-CEO at hackers&wizards, wants engineers to fix the process so the mistake doesn't come back. Hear why on this week's ep of The Next Commit w/ @leantomato. Listen: ow.ly/eo4O5103u7J

0:36
Tom Howlett avatar
Tom Howlett@leantomato·Oct 29

Here’s my deep dive on my conversation with Simon Vane, Staff Engineer at M-KOPA, I look at how review, tests and design conversations fit together when agents deliver faster than people can inspect. Read the full deep dive on Substack: thenextcommit.substack.com/p…

Tom Howlett avatar
Tom Howlett@leantomato·Oct 28

It's tempting to put all the time agents save into building more features. But without strong foundations, adding more complexity will make every new feature harder to add. Read my newsletter for more thoughts: thenextcommit.substack.com/p…

Tom Howlett avatar
Tom Howlett@leantomato·Oct 27

Which parts of pairing, TDD and quality still matter when agents write the code? I asked my old friend Simon Vane from MKopa on to The Next Commit, and we worked through what can move into agent instructions and automated checks, and what still needs people. Listen: thenextcommit.substack.com/p…

Tom Howlett avatar
Tom Howlett@leantomato·Oct 21

foundations remain as important today as they did in August. continue to invest accordingly :)

lauren@potetoJul 18

organic architecture good codebases have always had strong foundations and constraints. these files go here. this kind of code goes there. the codebase is held together either by catering to the lowest common denominator developer using conventional frameworks and languages, or by strict adherence to a style guide enforced by code review. the arrival of an infinite number of monkeys armed with keyboards have obsoleted the latter. codebases designed for agents need hard constraints so that even the dumbest agent (and pilot) can contribute meaningfully. the chaos must be tamed. refactoring your codebase and choosing a tech stack with strong type systems/compiler diagnostics has far greater impact than AGENTS.md and tweaking your skills. hard constraints and well thought out architecture guide agents to do the right thing by default. the best rules are in your code. invest accordingly.

Post attachment