This is the first edition of my rebranded newsletter, straight from my desk. Every other week, I'll write something about what we're seeing across the software
This is the first edition of my rebranded newsletter, straight from my desk. Every other week, I'll write something about what we're seeing across the software companies we work with at madewithlove. Think audit insights, AI in real codebases, technical due diligence, CTO struggles, the patterns we keep running into, ...
Hope you enjoy!
If you want to stay updated on what we're learning about AI and agentic engineering as it happens, we've built a separate AI Fast Track newsletter. Subscribing there brings our latest AI insights to your inbox the moment they're published, piece by piece.
On my desk this week
>> Here's something we were chewing on internally this week: the AI pull request handoff problem.
A teammate created an AI-assisted pull request, then went on holiday. Someone else picked it up and finished it without AI involvement. A critical bug slipped past QA.
What actually broke was the handoff. The original author held a mental model of what the AI had generated and which parts he trusted. None of that was written down. The next person walked in without that context, shipped the work, and the bug landed in production.
If your team is shipping AI-assisted work, two cheap fixes go a long way: label AI-assisted PRs explicitly, and require a short context note on what was generated, what was reviewed by hand, and what's still soft.
The framing that stuck with me: the part that truly deserves praise is the pull request of the plan. The implementation is downstream.
See you in two weeks,
Andreas
Oh, and we have a new website by the way. Happy to hear your feedback.
Bi-weekly conversations between Sjimi and Andreas on what's actually shaping SaaS right now. Unscripted, under ten minutes. Subscribe on YouTube or Spotify.
From Andreas' Desk
Bi-weekly insights for founders, CTOs and investors, curated by our CEO Andreas.