Why we are leaving Twitter - Team Topologies
Summary: we are leaving Twitter because Elon Musk is encouraging hate and division. See you on LinkedIn and Mastodon!
https://t.co/Mf5n4wOyeA
Struggling to implement change in your organization? Learn how you can design&evolve adaptive, socio-technical systems that are optimized for a fast flow of change w/ @TeamTopologies, Wardley Mapping, & DDD. Join @suksr at AmA this fall. https://t.co/L5fVfY4IJ3
The times when architects were siloed in ivory towers are gone. Change the dynamics of your organization by learning how "enabling teams" from @TeamTopologies work. @bitboss brings you both the theory and real-life examples. Save your spot at AmA. https://t.co/kHhrUnFAUf
Why we are leaving Twitter - Team Topologies
Summary: we are leaving Twitter because Elon Musk is encouraging hate and division. See you on LinkedIn and Mastodon!
https://t.co/Mf5n4wOyeA
The November issue of the @InfoQ Software Architects' Newsletter has been published -> https://t.co/e5tSFHKKYy
- DDD, Wardley Mapping, and @TeamTopologies (@suksr)
- Building High-Trust Teams at Shopify in a Remote World (@elsom25)
- The Engineer/Manager Pendulum (@mipsytipsy)
Well, there is a first for everything. I just received a signed copy of @TeamTopologies. Thank @manupaisable for great writing and for the gift! It is very much appreciated and I can only recommend @TeamTopologies to everyone working with software development and teams.
@tottinge@EB You're assuming there's only a single initiative that is flowing through these teams. You can't pull people out for every cross cutting initiative. This is why it doesn't work at scale. The best solution is to design your teams to reduce these tight dependencies. @TeamTopologies
"Developers are critical to delivering new software, and the developer platform offers critical support to your developers as they build and deliver software, ultimately enabling business growth." @thoughtworks
https://t.co/7ULS9pwmcQ
#platform#product
"By using AWS to scale their infrastructure, the cinch team was able to focus their cognitive load on improving the platform, quickly release new features, and re-build existing ones based on real world customer insight." @awsdevelopers
https://t.co/Cj1uMkptOz
#cognitiveload
Shout out to @TeamTopologies@matthewpskelton @manupaisable … you can’t go to a conference these days without Team Topologies getting a mention because it really is THAT GOOD. Go read it!
"It’s important that platforms are built and maintained in a way that responds to and mediates the needs of both technical teams and the wider organization." @thoughtworks
https://t.co/GrnxkSSVWq
#platforms
@_ggoran@allenholub@davefarley77 @tastapod @bakeraljc@nodosenlared@matthewpskelton The whole “let anyone change anything” model works fine for small groups of people (context is super important in all of this). At scale? It’s a hot mess, *especially* if you have aspirations for the “you build it, you run it” model.
Pivotal Events are events that represent a significant step in a business process. Pivotal events are usually a good indication of subdomains. Hear more in this free segment from the "Independent Value Streams with #DDD" course on @TeamTopologies Academy https://t.co/kZfrgazhrD