Newsletter, you say?

Sorry, but as another reply: pushing bugs to production doesn’t immediately equate to firing. Bug tickets are common and likely addressing issues in production.

It’s mainly for developers to follow decisions made over many iterations of files in a code base. A CTO might crawl the gitblame…but it’s usually us crunchy devs in the trenches getting by.

Cursor, an ai/agentic-first ide, is doing this with a blame-style method. Each line as it’s modified, added DOES show history of ai versus each human contributor.

So, not nonsense in probability, but in practice – no real enforcement to turn the feature on.

Thanks! I’ve always wanted an uncle bob, too!

I’ve settled on a future model where AIs are familiars that level up from their experience more naturally and are less immediately omnipotent

This is very cool. Any advice a simple software engineer (me) could follow to practice the same?