Becoming a tech lead was the goal from pretty early in my career. I had a clear picture of what the role was. More responsibility, more influence over the work, more of the interesting problems landing on my desk because someone had to figure them out and that someone, finally, would be me. It read like the natural next step. The thing you graduate to once you're good enough. What that picture did
“We have failover.” That sounds reassuring. But when real failure hits… many systems still go down — hard. Why? Because failover is easy to configure — but extremely hard to make reliable at global scale. Here are the most common ways failover fails in production: RDS Multi-AZ enabled Kubernetes failover configured Looks good on paper. Reality: Takes minutes instead of seconds Gets stuc
Reaching an annual salary of ¥8,000,000 is often seen as a major milestone for software engineers in Japan in 2026. On paper, it sounds like a ticket to a comfortable, upper-middle-class life in Tokyo. But is 8 million yen a good salary in Tokyo—really? But if you are coming from abroad—or if you've only looked at the "Gross" figure on your offer letter—you might be walking into a "logic bug" that
Background A nasty surprise Last summer while trying to deliver a feature for one of our customers, I encountered a nasty situation. The software we were developing, depended on a production grade license of Gurobi. People were on vacations except of my team and some unrelated staff, so developing the feature was in principle blocked. As I learnt due to some other situations, research
Si tu as 30 secondes. La mémoire versionnée d'un workflow Claude Code a un effet de bord que personne ne signale : une règle mémorisée qui colle au symptôme de manière plausible court-circuite la vérification, même quand elle ne s'applique pas au compteur précis que tu regardes. Je me suis coûté vingt minutes d'exploration SQL la semaine dernière parce qu'une règle de la forme du bug — sans en êtr
Technical debt and AI: is it gone? Lorenzo Battilocchi May 4 #ai #programming #management #technology 5 reactions Add Comment 3 min read
SOFTWARE ARCHITECTURE & REFACTORING 3 Domain-Centric Architectures Every Software Architect Should Know The first concern of the architect is to make sure that the house is usable; it is not to ensure that the house is made of brick. — Uncle Bob The expression domain is occurring in software bibles for a very long time now and is heavily discussed in the book Domain-Driven
How we moved from a fragile loop-based payout system to a reliable, idempotent, and traceable architecture. On paper, payouts sound simple: Customer places an order Platform collects payment Platform pays the seller That's it. Until you try to do it at scale. In any marketplace or fintech system, money flows across multiple parties: Sellers / vendors Delivery partners Platform fees Discounts, vouc