Disclaimer: This content reflects my personal opinions, not those of any organizations I am or have been affiliated with. Code samples are provided for illustration purposes only, use with caution and test thoroughly before deployment.
In my previous post about ADR as Event Sourcing, I talked about capturing architecture decisions continuously as they happen, not months later when everyone’s forgotten the context. But writing ADRs is only half the battle. The other half is actually enforcing them—and that’s where most teams fail. ADRs sit in a separate wiki or documentation tool like Confluence or Notion, gradually becoming archaeology rather than law.
What if we could give our AI code reviewer the ADRs as instructions, so it flags violations automatically on every pull request?
Does any organization actually have good, up-to-date software architecture documentation? I’ve worked with enough teams to know the answer is almost always “no.” Most architecture docs become outdated the moment they’re written. Engineers don’t have time to maintain documentation while shipping features. Traditional Architecture Decision Records (ADRs) are often written after decisions are made, not during the decision-making process. And when you’re busy, you simply forget to document parts of your architecture, leaving it spotty and unreliable. With Generative AI, I think we should treat ADRs more like event sourcing—capturing decisions as they happen, not reconstructing them from memory weeks later.
As a busy parent, I often only have 5-10 minutes of uninterrupted work time before my child needs attention. Traditional coding workflows—where you need a laptop open, an IDE running with AI agents actively working, and constant supervision—simply don’t work for someone in my situation. I needed a setup that could run in the background without any intervention, could be accessed from any device including my phone or tablet, and would let me make meaningful progress in short bursts throughout the day. Here’s the complete remote vibe coding workflow I’ve built using GitHub Copilot and Cloudflare Pages.
The TOGAF Practitioner exam can be challenging, but with the right strategy, you can significantly improve your chances of success. Unlike the Foundation exam which tests knowledge recall, the Practitioner exam tests your ability to apply TOGAF principles in realistic scenarios. Here’s a battle-tested approach that helped me pass the exam.
In September 2008, I wrote my first blog post, a humble guide about fixing missing screen resolutions in Ubuntu. Eighteen years and 88 posts later, I’m celebrating a different milestone: the 10th anniversary of moving this blog to its permanent home on shinglyu.com. What started as a way to document Linux troubleshooting tips has evolved into something far more significant: a chronicle of my entire career, from browser hacker to cloud architect, and a testament to the power of owning your own platform.