Office of Strategic Software (OSS) is an initiative comprised of individuals concerned with not only tactical but also strategic transformation of businesses.
On 24 July 2020 we will be streaming live "Microservices from A to Z: Myth Busting and Proven Practices", an online discussion with @suksr @vladikk @thinkb4coding @VaughnVernon@jbogard and @tjaskula
Checkout for event details on https://t.co/dTTph6ZKWk
Developers want recipes for #DDDesign solutions. The problem is when one recipe looks like a solution to problems that don't have the context of the recipe. For example, a context sending a command downstream rather than upstream.
@pdevito3@ardalis Steve has a great post on using a v.o. to STORE a collection. (Just thought I'd mention). @tjaskula has an example of a generic class designed for a collection OF VO in this repo: https://t.co/YEEAOqbOvN
If OSS wasn't free, specifically for commercial/production use, then companies would HAVE to pay, as there wouldn't be free alternatives.
As an industry, we need to renormalize charging money for software.
Event sourcing helps to model state transitions explicitly, so that we can fully understand the state changes that have happened.
Hear more from @tjaskula in episode 66.
https://t.co/UGu8H9lNc1
Time is important for business, and we can use temporal modeling to model it explicitly.
Hear more from @tjaskula in episode 66.
https://t.co/UGu8H9lNc1
To implement DDD properly requires both the strategic and tactical parts. You shouldn't focus on just the tactical part.
Hear more from @tjaskula in episode 66.
https://t.co/UGu8H9ml1z
A new and super fresh addition to my collection of top content from @VaughnVernon and @tjaskula, looking forward to dig in! And of course looking forward to get it signed like the other two when the earth comes back into rotating and more planes to flying to Barcelona 😉
"Software Architect" can still be a relevant role if the person fulfilling it, is facilitating and organizing the communication and collaboration leading to a sound architecture.
"Software Architect" is just one of the many stakeholders having an impact on the architecture.
If your organization considers software development as a cost center there will be very few opportunities for investments and innovation. It is not about making manual operations faster but about finding new business opportunities and strategies.
If you want to use #DDDesign effectively, do more than name things.
Discovery-based learning is essential, and experimentation with failure expectations toward refinement is the safest and quickest way to learn together.
Team over individual
Critical thinking over echo chamber
There's a thread on LinkedIn regarding @suksr's new workshop "Building Adaptive Systems for a Fast Flow of Change" that includes comments by Susanne and a few others. It's a nice setup for the topics of the workshop.
https://t.co/DeH0RUb76p
Register for "Building Adaptive Systems for a Fast Flow of Change" by @suksr.
Why you need to attend: There's no better opportunity to learn #WardleyMaps, #DDDesign, and #TeamTopologies for strategic business innovation.
https://t.co/y6fFzWvj2D