I'm working on a prompt to give you an #EventModeling engineer. You can play with it here if you are on GTP4:

I'm hoping you can just feed transcripts of your brain storming sessions and it will give you an event model to start with. https://t.co/7VBbmuD9cgchat.openai.com/share/378a24fc…
I got it to include GWTs and GWs. This is hit and miss at the moment but refining this will end up giving you some great examples of each command and read model.

Don't use squash or rebase as part of your git workflow. Merge and reset only. It's a discipline that will push good organization and accountability of work. Start each feature from a common start tag. These tags should reflect your sprint, milestone and/or release cycles. An integration branch is used for continuous integration testing. Think of building release candidates to get focus on near-term attainable goals.

TDD is about design. So with @eventmodeling
it goes out the window. What you have is unit tests to help give you regression tests. But even then, you are doing OCP more than recent years allowed. So plow through the happy path ASAP. Use THAT as the backbone to your system. More on this at tomorrow's meetup. This is truly agile. I never thought I would ever think to discourage #TDD. But here I am saying exactly that after practising it for 20 years.

I really appreciate @conways_law 's perspective into his Law. It's much deeper than the writings about it give insight on. The monetary incentives that shape how the work gets done. There are literally battles for budget that affect the quality, speed, etc of the solutions. Not the conclusion expected, but monolith for the organization isn't as bad as people make it out to be. Artificial teams and too many of them can cause far more damage.