Jon Eaves Michael Rembach They’re a useful option, especially for companies where you have lots of developers who don’t want to get in each other’s way. But it’s just an option - unfortunately microservices have become a default choice for many, used all to often without thinking about their suitability

You probably already know the Actor Model. It's neither exotic nor complicated. Sure, it's no silver bullet, but it might help structure thoughts, architecture discussions and ultimately software. No conflict with other paradigms necessary: FP, OOP, DDD all work well with it.

If you have Junior Devs in your team, don't be afraid to let them review your PR. Instead, actively encourage them to do so. Tell them to ask questions for everything they don't understand. That way you can mentor them and at the same time make your code easier to understand!

Assemblies are units of deployment not for separating layers Assemblies are units of deployment not for separating layers Assemblies are units of deployment not for separating layers Assemblies are units of dep

DDD versus Classic Approach. An introduction of DDD by Tobias Goeschel at #socrates2019

To a lot of people this is true....

"The first step of any project is to grossly underestimate its complexity and difficulty." ~@nicollhunt

TDD does not take extra time. Writing tests _first_ is not overhead because they force you to think through the problem and partition it properly. You’d have to do that thinking anyway. Testing after the fact IS overhead because you did all that thinking already.

I hate to think of the number of hours wasted across the industry investigating why end to end tests are failing. Push automated testing down to lower levels. If you can’t do this you have a design problem, not a testing problem.

Microservices are maybe not what you think they are, so here's a #Thread to describe them... 1/14

2018: "How to split your monolith into microservices" 2023: "How to consolidate your microservices back into a monolith"

Back to #Aarhus after many years… 🤩 We are so glad to be hosted by @MjolnerDK for a two-day #EventStorming Master Class with Alberto Brandolini 🔸 Two days of tips and tricks, many sticky notes and interesting conversations with a passionate group of learners. Thank you all!

"I've set the wedding date. I've not asked her out yet."---how software projects are managed.

Dont think in older normalized relational DB terms. Having copies or value types is fine :-)

If you remake awful software from scratch without changing the culture that created it: you'll remake awful software

Challenging the spec is doing your job, are you doing it? Every task has a spec: even if an implicit, half thought, barely communicated one.

Software development is not manufacturing. We are paid to create something new and change the world.

Frustrating: resetting a 20-min failed refactoring; Elating: when it takes 5 mins to redo it correctly b/c u learned something the 1st time.

Refactoring = code transformation based on what you’ve learnt from the past Over-engineering = code transformation based on the speculation for the future.