Morten Jokumsen @guidmaster

Software Architect Horsens, Denmark Joined March 2008

Tweets

3K
Followers

621
Following

817
Likes

279

James Hickey 🇨🇦👨‍💻 @jamesmh_dev

2 years ago

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

112 682 5K 512K 229

EventStorming @eventstorming

2 years ago

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

0 2 3 456 0

Download Image

Dave Farley @davefarley77

2 years ago

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

20 185 592 128K 485

Ryan Greenhall @ryangreenhall

3 years ago

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.

Dave Farley @davefarley77

3 years ago

7 13 55 0 24

Download Image

4 10 58 0 13

Uncle Bob Martin @unclebobmartin

3 years ago

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.

61 242 1K 0 73

Woody Zuill @WoodyZuill

5 years ago

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

1 20 52 0 2

Tim Ottinger @tottinge

5 years ago

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

6 63 178 0 3

Download Image

Houssam Fakih @houssamfakih

6 years ago

DDD versus Classic Approach. An introduction of DDD by @w3ltraumpirat at #socrates2019

0 27 45 0 2

Download Image

Manuel Bieh @ManuelBieh

6 years ago

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!

4 20 54 0 1

Tomasz @tjaskula

8 years ago

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

8 466 659 0 11

Jimmy Bogard is on Bluesky FYI @jbogard

6 years ago

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

Jeremy D. Miller @jeremydmiller

6 years ago

15 9 68 0 3

12 60 159 0 13

DLed @dmlled

6 years ago

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.

Vaughn Vernon @VaughnVernon

6 years ago

3 17 73 0 9

0 4 11 0 0

Sam Newman @samnewman

7 years ago

@joneaves @mrembach 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