When code stops being the source of truth A paradigm shift is emerging in software engineering: Requirements, not Code, are becoming the Source of Truth. For decades, engineers have treated code as the
When code stops being the source of truth A paradigm shift is emerging in software engineering: Requirements, not Code, are becoming the Source of Truth. For decades, engineers have treated code as the
This week I kept circling back to the same idea: the tools are getting smarter, but the real advantage is still how fast you and your team can learn.One thread is where LLMs
Technical TL;DR (for busy engineers) Static weights are the bottleneck. Most LLMs can infer in-session, but they don't durably update from experience unless you retrain or fine-tune. Context windows, RAG, and "memory" features help,
TL;DR Time invested: ~4 weeks of focused preparation Resources used: Frank Kane's Udemy course, Stephane Maarek's AI Practitioner tests, Tutorials Dojo practice exams, AWS documentation, hands-on Bedrock projects Difficulty level: Hardest AWS exam
You’re trying to ship AI features fast—without creating a security, cost, or reliability mess.This week’s three insights connect into one theme: move quickly, but design for enterprise constraints from day one. That means
You don’t need “more AI.” You need AI that survives enterprise constraints: security reviews, platform standards, and teams that still have to ship.This week’s three insights connect the dots: pick the right enterprise
I’ve been playing with a bunch of “AI + web” setups lately, and I keep running into the same vibe: the model is smart, but the search layer feels… constrained. You ask for
1. The enterprise AI bet: what AWS is actually optimizing for Here’s the uncomfortable truth about AWS in AI: they’re not trying to “win the model leaderboard.” They’re trying to win regulated, enterprise
Getting Started: “I’ll just use BMAD to move faster” Over the last couple of weeks I’ve been working with the BMAD framework on a personal project, and I wanted to write this up
Many times, when making an architectural decision, I am faced with multiple decision points. Each point leads to a new possibility of making another decision with three, four, or even five levels of