💬 Should code always be in English? 🇬🇧
Translating business terms into English in a #DDD context?
Bad idea. 🤯
It can cause misunderstandings & complicate communication with business teams.
📢 Real-life example + best practices here:
https://t.co/Xh94hqTtaC #SoftwareEngineering
Are you doing DDD or just implementing technical layers? 🤔
Domains and bounded contexts are business concepts, not framework constructs.
Discover how to truly embrace business-first design👇
#DDD#DomainDrivenDesign
https://t.co/c4yNad6ps9
#DDD can be powerful, but beware of domain events leaking out...
💡 In this post, I'll show you how you could avoid those troublesome Domain Event leaks. Read the full article here: https://t.co/BgrPzME844
Daily meetings are a micromanaging shitshow.
Most people know these 15-minute stand-ups are useless. But they do them anyway because "that's how it should be."
One day, the corporate world decided that Scrum answered every problem. Daily meetings became popular. Everyone. Every day. No exceptions.
When did we become numb to how inefficient this is? How much time do companies waste every year in this charade?
The funny part is that Scrum sells these by telling us they are a way to avoid other meetings. You gotta be kidding me!
Unfortunately, I've participated in daily stand-ups for decades. If I were to compress these years into a single story, it would read like this:
• We are still waiting for some. Where is he? We can't start unless we are all here. We are late already.
• There's a manager in the meeting. We know she shouldn't be here. Who is going to tell her?
• We take turns reading from a JIRA board shared on the big screen. Everyone can read, but we still do it out loud. She wants to hear us say it.
• Yesterday wasn't a great day, but I won't admit it. Instead, let me tell her, "I'm making great progress" and "I'm getting closer than ever."
• We are all talking to her. She said this is a "safe space." We trust her, of course. Now, she is questioning anyone who isn't moving fast enough.
• 15 minutes in, and we are still here. Same as yesterday.
The first time I led a team, I stopped daily stand-ups. One of the first principles of getting shit done is "maximizing uninterrupted time." Daily meetings are in direct conflict with that.
Why should I force everyone to be at the same time and place while stopping everything else?
I asked everyone to write instead. Some people wrote every day. Some people, whenever they had something to say.
10x improvement overnight. For the project and the team.
I've talked to many people about this. Many tell me developers will never communicate unless you force them into a room daily. They say I shouldn't trust them to put in writing what they need to tell everyone else.
They may be right. They need a better team.
Many executives fail to understand why tech companies are bloated. They are bloated because everything is held together with duck tape and "task force" teams. And it's due to gross lack of funding when it comes to removing complexity and technical debt.
Its getting into evening on a Saturday night. Time to reflect on the week.
What was your most ridiculous interaction?
I was told I don't know what CQRS is .. by a non-technical recruiter.
The lie that we can get more work done by working on multiple things at once is so absurd, so incorrect, & so utterly destructive that I can't believe it's a near-universal practice.
I wrote a ~~rant~~ post on why no one should multitask. Ever. Seriously.
https://t.co/emP1UQ6gwR
@lisalaposte on est d'accord que j'ai jusqu'à minuit et que ça semble mal parti pour que le bug soit résolu avant, au mieux, demain?
PS: J'ai utilisé les bonnes infos, c'est juste masqué hein :)