| GitHub | https://github.com/mheadd |
| Website | https://civic.io/about/ |
| https://www.linkedin.com/in/markheadd/ | |
| BlueSky | https://bsky.app/profile/mheadd.bsky.social |
Learn more about the SpecOps method, and find out more about the book here:
I was interviewed about the SpecOps Method for legacy system modernization on the Civic Tech Chat podcast. Check out the episode here.
The Nobel Peace Prize has gone to some less-than-deserving recipients over the years (understatement). But in honour of St Patrick's Day, here's some homework for you on two recipients who did, in fact, deserve the prize.
https://www.nobelpeaceprize.org/laureates/1998
You can read the entirety of the Good Friday Agreement online. For such an incredibly important document, it isn't that long.
https://www.gov.uk/government/publications/the-belfast-agreement
A new study out of Carnegie Mellon University reveals a troubling pattern in open source projects adopting AI coding tools: a dramatic short-term burst in productivity that fades within months, leaving behind a persistent accumulation of technical debt that slows future development. The fix, it turns out, may lie in an idea as familiar as a CONTRIBUTING file — but updated for the AI era.
The future of software development belongs to those who can best articulate what they want to build and how it should work. The ability to just write good code is no longer enough. Developers will have to write good words as well.
https://www.nytimes.com/2026/03/12/magazine/ai-coding-programming-jobs-claude-chatgpt.html
Early day is for this new offering from the creator of Kotlin. But the guiding principle is one that I think is going to fundamentally change the way we create software into the future.
Write specs, not code. Need to change the code, change the spec first. 🏆 👏
Steph (spring version???)
