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
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
Hey Dev Community, Like many of you, I hit a wall with GA4. It’s powerful, sure—but it’s also cluttered, slow, and often feels like it was designed for a data scientist rather than a developer or a brand owner who just needs to see what’s working. I wanted something different. I wanted a platform that felt like a developer tool: minimalist, tech-oriented, and focused on actual insight rather than
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
Key Takeaways Multichain user journeys span social discovery, multiple chains, and offchain touchpoints so analytics tools must unify all data sources into a single user profile to avoid making decisions on structurally incomplete information. Web3 conversion cycles are far shorter than Web2 with users moving from first touch to transaction within a single session, making real-time attributi