-
It's still easier for me to start with "what" and then move backwards to the "why". Sometimes the why isn't the best, yet it's good enough to keep us moving. 1/3On twitter.com
❤️ 2 Favorites Mood +6 🙂
-
X: Why should we implement this feature? Which is the business goal? Me: We are copying as this company does so you can be familiar with the code base and architecture. It's a good enough boarding process and it just helps us to start gaining some momentum. 2/3Permalink On twitter.com
-
Does it matter what we do when it's 2 hours of pairing? No, we can delete that at any time The purpose isn't the business relational behind a feature but the outcomes you have while developing Challenging why we do something is good, sometimes the why isn't what you expect 3/3Permalink On twitter.com
-
Plus, when the idea isn't well formed yet, be careful about asking why too much You need to move to find the why along the journey If a "why?" reduce your movement, care about the implications It needs drive intentional action (like discover while doing) vs preventing movementPermalink On twitter.com