I finally realized what's been on my mind for the past 15 months.

What happens to team members when transitioning from a legacy Big Ball of Mud to a modernized architecture and transformed digital enterprise? Think in terms of building autonomous, cross-functional teams, such as by applying Team Topologies. The most capable and eager members should be placed on a stream-aligned, enabling, or platform team as soon as possible. Different skillsets will favor different teams. Although this may seem unfair to some "left behind" on the legacy, it can lead to at least a few favorable outcomes for everyone. The placement of skilled and eager are no-brainers. Still, there will be plenty of work to go around. Some may not feel confident to join the new team from the get-go. They can wait to see a successful outcome and then join a successful stream-aligned team for ongoing value delivery. This can give them time to ramp up. Others may not want to remain in the forefront of software delivery. Those have likely spent a long time working on the legacy and know it very well. They would likely be an ideal fit to serve as domain experts on the new efforts that include transformation and modernization.

@iam_ijaz @conways_law I suggest watching the video training all the way through. That will save me time restating a lot of the content that's included in the training.

People ask why I authored. I wrote "Implementing Domain-Driven Design" with the idea that I could possibly influence my future prospects to do work that I could get excited about. I was a consultant and contractor and made plenty of money doing that. I just wanted to be able to influence with documentation 🤩

@iam_ijaz @conways_law How many people are on that one team dealing with all subsystems?

RT @iam_ijaz: @VaughnVernon Now I am going through the accompanying video course, highly recommended guys

RT @iam_ijaz: @VaughnVernon I was going through this book online, what a great read. Well done. I do have one ques…

It never ceases to amaze me how so many people think that tech authors write to make money. Repeat after me: Tech authors very rarely recoup their investment in the books they write directly from book sales. Please stop insulting book authors. Write your own book and find out. Case in point: Before Susanne's book is published, there has been nearly five years of part-time effort in her writing. She has worked painstakingly to complete her final draft. And now there's the production process.

If you want to understand the significance of Susanne Kaiser's profile background, you'll read her upcoming book. I am certain that I am now working on my final series editor reviews. This is a 100% winner, just like everything Susanne does. Now on: @suksr.bsky.social

@dan_s30 BTW, the above is just code for "You are better than that, Dan."

@stefan_renz That's the My-Other-Brother-Darryl of comparisons.

@dan_s30 And so on and so forth.

If you have the opportunity to see the incredible “Kodo One Earth Tour 2025: Warabe” taiko drum performance, do it. They performed last night at the Mesa Arts Center in Mesa, Arizona, and are pounding their way around the US.

"The grass is always greener..." they fall in, and there's no beach. Walking through farm open spaces in Colorado with irrigation ditches, we saw this regularly, with and without water.

99.999% of humans don't like chess or care anything about it. Software chess opponents can rip through thousands of moves and counter moves and choose the best outcomes. That's array processing, not intelligence or "playing," and has existed long before current "AI" models.