Have you ever been confused by the Event Storming notation? Then read my most recent blog post. In addition to providing an overview of the notation, it explains its logic and how it can be used to map out business processes. #ddd https://t.co/tToSBIqQDU
@Morl99@InnerSourceOrg @dbsystel I absolutely share the idea of sharing is caring when it comes to Inner Source but you should be aware of the reusability tradeoff. There is a great article series about it from @ufried : https://t.co/tAOIzFNVRO
I’ve been using these diagrams for so long I forget that other people don’t know the notation.
When we are understanding systems it helps to understand how one effect affects another. Sometimes more of one effect causes more of another (more errors causes more fear).
@derDoubleD @dbsystel Laut dem Wikipedia-Artikel zur sozialen Resonanz gibt es dennoch kritische Sichtweisen zu diesem Thema. Was Du beschreibst, klingt für mich nach: wir wollen alle geliebt werden, was in der Tat ein Allgemeinplatz ist.
Many of the software engineers I talked to told me that they practice TDD out of guilt.
That's not right, we need a different way to think about TDD.
I've been practising TDD for almost a decade, here's how I currently think about it:
Did you know there was a "Destruction Oriented Era" 💣 in software testing history?
Published a brief post about the history of softwaretesting: https://t.co/s4YdVhXDB6
#SoftwareTesting#TestAutomation
Talking with a senior engineer I noticed a pattern. There were bugs. Nobody knew how many. They weren't on anyone's roadmap.
So the engineer dug in. Discovered curious & horrifying facts. Discovered a lack of organizational urgency. Fixed stuff. Encouraged others to fix stuff.