Don’t write code that guesses the future
Avoid over-anticipating: don’t lay the groundwork for future features; they remain hypothetical. Instead, write code that can evolve.
Avoid over-anticipating: don’t lay the groundwork for future features; they remain hypothetical. Instead, write code that can evolve.
Few digital services companies possess true expertise. The majority sell precarious employment conditions to end clients, which suits them just fine.
8 ideas that are frankly ridiculous—and yet so widespread—when it comes to software development… Do yourself a favor: read this!
Agility is the art of “how,” Product Management that of “what.” One without the other is pointless: they are two sides of the same coin.
You don’t address all users in the same way. Each persona has its own language—and therefore its own context—and its own BFF (Backend For Frontend).
Ecology and software quality share Kant’s principle of universality: my action can only be good if everyone can act as I do.
This phrase, a DevOps mantra, is rooted in common sense. Yet the organization sometimes resists its implementation. CEOs, lay the groundwork.
“Lean is not a production system; it’s a learning system”: that line gave me the foothold I needed to grok Lean.
Until everything is done, it’s as if nothing has been done. To avoid a refactoring’s tunnel effect: the Strangler Fig pattern, which lets the old and the new coexist.
Beyond technology and methodology, it’s our values that drive us. For 2024, I wish you courage: to aim high, to question, to ask for help.
There is always a risk of doing harm while trying to do good. A coach, like other support professionals, should be supervised.
You probably don’t need these microservices, which are so difficult to deploy. The monolith—provided it’s modular—is right for you.
The Walking Skeleton aims to lay a solid foundation for reaching the MVP while minimizing technical debt. It’s a step worth formalizing.
Going freelance is an opportunity to double your income… or not. It all depends on your life plan. An account of a personal experience.
It would be a mistake to believe that functional design is the sole responsibility of the PM: we think more clearly when working together and using concrete examples.
Trunk-Based Development, which stems directly from Extreme Programming, is an excellent alternative to GitFlow, but be sure to thoroughly review the prerequisites.
A POC validates a marketing or technical idea, while an MVP aims to acquire your first users.
A project exists because we envision a goal to be achieved. A product has no end and evolves based on user feedback.
My main criticism of Scrum is that it says nothing about functional design. If you want it to work, it’s up to you to fill in the gaps.
2 common mistakes in dividing into Bounded Contexts: dividing by technical layers and dividing by entities. Think action verbs!