Cloudy with a chance of Event Storming
<p>Joining a brand new squad can be the most blissful experience, especially here at the LEGO® Group. Squads here have a funky team name, mascots carefully crocheted for them, and really cool missions. I was twice as lucky as to join “Pirates,” a newly-formed squad working on a dedicated repository and AWS account.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:630/1*Iv21Y_M0k3FQXNe-j4izzg.png" style="height:525px; width:700px" /></p>
<p>Pirates’ mascot and “Pirate Adventure Ride” set — photo by me</p>
<p>Having the opportunity to develop a solution on a new codebase can lure one into thinking it will be simple to make everything perfect this time. State-of-the-art only, best practices, a fresh Jira board… The stage is set for coding nirvana.</p>
<h2>Plot Twister </h2>
<p>This drive to attain perfection can soon be overtaken by a sudden existential crisis when it is time to start placing those metaphorical 0s and 1s. I mean, where do we start building? Have the other squads understood where we are going with this? Why do I feel like we have forgotten something major that will inevitably break prod when we least expect it?</p>
<p><a href="https://medium.com/lego-engineering/cloudy-with-a-chance-of-event-storming-73817afe10c2">Read More</a></p>