James Shore
jamesshore@mastodon.online
<p>I transform software development organizations when repeated fixes have failed. Author of The Art of Agile Development. Writing about all aspects of software development success, with an emphasis on leadership.</p>
Posts
-
View post
One CIO I talked to recently, with 170 people in his organization, measured a 2.1x increase in productivity from AI. That productivity came at a cost. His top users of AI each spent $21,000 on tokens per month. Another engineering leader spends six to eight thousand dollars per engineer per month. If you’re going to make these tradeoffs—and *somebody* is going to—they need to be good ones. Which raises the question: how do you know what you’re getting? https://www.jamesshore.com/v2/blog/2026...
-
View post
As I talk to engineering leaders, I’m seeing *order-of-magnitude* differences in spending on AI. Should you spend thousands per person per month on hands-off agentic coding? Or hundreds on analysis and fancy auto-complete? It depends on the outcomes. You can’t pick the right approach to AI without knowing what you’re getting, and you can’t afford to half-ass this. So how do you measure it? Measure and compare approaches in part 2 of my series on quantifying AI impact: https://www.jamesshore....
-
View post
If AI is doing the maintenance, do we care how easily a human can understand the code? Among the people I&#39;ve talked to, there&#39;s widespread agreement that heavy use of AI produces code that humans have trouble understanding. But there&#39;s disagreement about how much that matters. This is what we need to measure. Is there an impact? If there is, is it enough to matter? Ultimately, we want to know if AI usage is sustainable. Part 3 of my series on quantifying AI&#39;s i...
-
View post
I was a consultant for 23 years before I joined OpenSesame as their VP of Engineering. Now, three years later, I'm returning to consulting. Why? Put simply: impact. https://www.jamesshore.com/v2/blog/2026/returning-to-consulting
-
View post
I gave a keynote at Agile Cambridge a few weeks ago on &quot;The Accountability Problem.&quot; How do we define software department accountability so our business partners don’t do it for us? The transcript of that presentation is now available on my site: https://www.jamesshore.com/v2/blog/2025/the-accountability-problem
-
View post
Hey, did you know I wrote an open source testing framework for JavaScript? It&#39;s simple, boring, and very, very detail-oriented. Its raison d&#39;etre is to provide a better test automation API. I built it after test tool magic bit me in the butt one too many times. I&#39;ve been using it on my production code for years, but never made a big deal about it. Anyway, I just released a new version. Check it out if you like simple, well-documented tools that are pleasant to use. ht...
-
View post
Hi folks, I&#39;ve got a great job opportunity for the entry-level to low-senior software engineers in your network. Canada and Latin America only at this time, in US time zones. If you know someone who&#39;s a good fit, please forward this to them! 1/
-
View post
Apologies, folks, the link I posted was incorrect. Here’s the correct link: https://job-boards.greenhouse.io/opensesame/jobs/7927745?gh_jid=7927745
-
View post
New blog: I’ll get straight to the point: your AI coding agent, the one you use to write code, needs to reduce your maintenance costs. Not by a little bit, either. You write code twice as quick now? Better hope you’ve halved your maintenance costs. Three times as productive? One third the maintenance costs. Otherwise, you’re screwed. You’re trading a temporary speed boost for permanent indenture. Oh, you want to know *why?* Sure. Let’s go for a drive. https://www.jamesshore.com/v2/blog/2026/y...
-
View post
Hi everyone! I&#39;m hiring another XP (Extreme Programming) senior software engineer to come work with us at OpenSesame. This is a fully-remote position and we&#39;re looking for folks in Canada or Latin America in Eastern or Central time zones. You&#39;ll help mentor a team in using XP practices such as TDD, pairing, and continuous integration. Most of your work will involve leading by example as the team adds features and tests to our legacy PHP codebase. 1/