Software craftsman. I write about CQRS, Event Sourcing and DDD, with real code on real stacks | Freelance | Do more with less | Step father of one princess
๐ก I document CQRS, Event Sourcing and DDD with real code on real stacks.
Latest: CQRS: separating the command from the query
๐ https://t.co/xx3OFkUF3E
All my articles in this thread ๐
#CQRS#EventSourcing
@ItsChrisCorado@sakthisankara Support messages are evidence, not roadmap items. The feature request is usually a proposed fix.
Look for the workflow or business rule that keeps failing, then decide whether one change solves the repeated problem
The worst response would be to hire only people who are already ready-made.
We need to get better at spotting potential when the obvious signals are easy to produce.
I wrote the longer version here:
https://t.co/YLmcDyQ1Yq
I never believed in hiring junior engineers for their stack.
React, Node, TypeScript, Docker: useful foundations. Not a reason to hire someone.
With AI, that distinction matters even more.
AI can make the visible part of development look easy.
It does not tell you whether someone understands the problem, sees the rule a change might break, asks for missing context or knows when they do not have enough evidence to decide.
@zachlloydtweets 2-3x cost makes the split important: how much comes from first pass findings, rereview after fixes, and false positives?
That would show whether the extra spend buys new signal or just more churn
@Hi_Mrinal Microservices make a boundary executable. They don't create autonomy by themselves
If the decision, the data and the release cadence are not independent, you just moved the coordination cost onto the network where it becomes failure modes you cannot see in one transaction
@nyxienyxie Persisting the wait is the easy part. Hard part is knowing whether the agent is still allowed to resume when the answer finally comes back
I'd persist the decision, the owner and the acceptance criteria too. Otherwise you get a durable process that can keep doing the wrong thing
๐ก I document CQRS, Event Sourcing and DDD with real code on real stacks.
Latest: CQRS: separating the command from the query
๐ https://t.co/xx3OFkUF3E
All my articles in this thread ๐
#CQRS#EventSourcing
๐ DDD: Should I write all the code using English?
https://t.co/EUzQv3DPgu
๐ A simple decision to save you from one of your worst nightmares
https://t.co/d6yynW2xfI
New articles get added to this thread.
๐ The full post, with the code: https://t.co/3EJBK9zwNH
It's a demo, so it shows a lot at once. A real project takes what its problem asks for.
#Laravel#CQRS
In a restaurant, "order" means 3 things. The dining room sells the plate, the kitchen cooks it, the till charges it.
Same plate, 3 classes, and none of them knows the other 2.
Part 2 of my CQRS series, in Laravel ๐
And to the Laravel crowd who thinks it's not "Laravel Way" enough: don't lose the thread.
The series stays on Laravel and on this repo and we'll get there step by step. I'm going to get you all to make peace with it :)
@AkubueAlexander Designing the schema "for the future" is the trap IMHO. The business will change shapes you can't guess. I'd rather keep write decisions as they happened and rebuild any report when the question changes. The tables that answer today's questions stay disposable
@AkubueAlexander One rule accountants already follow is worth enforcing in the schema. A posted journal entry is never updated or deleted, a mistake gets a reversing entry. Then any balance can be recomputed from the lines and every number traced back to its source
@Vikram6072@piyushgarg_dev "ProductPriceUpdated" says what changed in the table. The business usually knows why: "PromotionApplied", "PriceIncreased", "PriceTypoCorrected". That's where events start answering questions a CRUD history can't
And what's a "simple application" or a "simple business"?