Introduction For engineers, code reviews occupy a significant portion of daily work. Many struggle with questions like, “How granular should I get?”, “Where is...
TL;DR One person posts a complaint in Discord, nobody can tell if it’s real or not, and your whole team burns two days chasing it. I’ve seen this happen at stu...
TL;DR Diving into Lovable without a plan turned my first build into an unusable mess. The fix: build throw‑away prototypes first. I now spend a few hours creat...
Background Software projects rarely fail because someone can’t write code. In this project we were building a product with a fairly standard stack: - Frontend:...
API‑First Frontend Development: A Real‑World Walkthrough In many teams, the frontend and backend evolve in parallel — and very often they drift apart. I’ve see...
Introduction It's 9:47 AM. Your team is arguing whether a story is a 5 or an 8. Forty minutes in. Nothing has shipped. This is Scrum theater—and most organizat...
Introduction Every Wednesday at 2 PM, twelve developers file into a conference room. For the next ninety minutes they hold up cards with Fibonacci numbers, deb...
I recently led a project for a retail client: new domain, tight deadlines, big expectations. Instead of disappearing into “tech planning mode” and coming back w...
Plans change, APIs break, and priorities shift. It is simply part of the job. What separates great teams from average ones isn’t their ability to avoid change,...
Tutorials are useful. Courses are helpful. But growth happens when things break. I started coding at a young age, and one thing became clear early: > Reading ab...
Summary - Traditional work is meeting‑driven: discussions and conclusions happen spontaneously during meetings. - It feels easy because you just follow the sch...
Day 2 – Legality and Foundations With the project brief completed, Day 2 focused on legality and foundational setup. I spent the day researching the legal impl...
