Jim Grey on software management dev.jimgrey.net

The bottleneck has moved: redesigning the SDLC for AI

dev.jimgrey.net·1w

The real AI coding revolution: learning speed, not coding speed

dev.jimgrey.net·3w

AI coding in a traditional company: what it actually takes

dev.jimgrey.net·4w

The player/coach trap: why Engineering Managers shouldn’t be expected to code

dev.jimgrey.net·7w·Hacker News

You can’t build loosely coupled software with loosely coupled teams

dev.jimgrey.net·8w

How to earn credibility with engineers (lessons from a college radio station)

dev.jimgrey.net·9w·Hacker News

The invisible foundation of engineering transformation

dev.jimgrey.net·10w·Hacker News

From quality function to quality system: reimagining the Quality Engineer

dev.jimgrey.net·11w

AI enables more complex systems

dev.jimgrey.net·12w

Quality advisors, test automation, and the work that’s disappearing

dev.jimgrey.net·13w

The discipline of the light hand

dev.jimgrey.net·15w

A Substack experiment

dev.jimgrey.net·16w

A nine-point framework for rapidly assessing software-engineering organizations

dev.jimgrey.net·16w

Unlocking high software engineering pace: Automate testing to test early and often

dev.jimgrey.net·17w

Unlocking high engineering pace: Prevent unplanned work

dev.jimgrey.net·24w

Unlocking high software engineering pace: Ruthlessly eliminate drag in your processes and technologies

dev.jimgrey.net·26w·Hacker News

Unlocking high software engineering pace: Use CI/CD to capture market opportunities right when they emerge

dev.jimgrey.net·34w

Unlocking high software engineering pace: Partner with Product to pay down technical debt

dev.jimgrey.net·38w·Hacker News

Unlocking high software engineering pace: Build less, ship frequently, learn faster

dev.jimgrey.net·43w

Unlocking high software engineering pace: Drive adoption of AI

dev.jimgrey.net·53w

Log in to enable infinite scrolling