We're only going to solve the problem we have in front of us, we're not going to anticipate the future.
Vector magic kickass code#
This is the idea that we're only going to build code for what we need to do today. You may have heard the phrase, "You aren't going to need it." (YAGNI) That was one of the big catch phrases of extreme programming in the early days. And, his take on solving only the problems that are right in front of us hit me hard in the feels! In the podcast, James Shore talked about early Extreme Programming and the birth of Agile development and, he talked about how "evolutionary design" has gotten lost in translation over the years. Epilogue on James Shore And Evolutionary DesignĪ couple of months ago, I listened to an old episode (from 2016) of Ruby Rogues featuring James Shore. But, we have accepted the things we cannot change and, it has truly given us the strength to move mountains.
We are pragmatists and, we are passionate and, we bias towards action. With fewer options on the table, we spend less time worrying about whether or not those options are optimal and, more time just getting stuff done. That's not to say that all limitations are inherently a strength but, rather, with limitations that are beyond our control, we are forced to look at each limitation and figure out how it empowers us to make decisions and to move forward.
And, in that trade-off - amidst the balance-sheet of calculations - my team is constantly fighting to find an area in which it can chew bubblegum and kick-ass. Because, in the world of web application development, the reality is, everything is nuanced. Not about team size specifically but, more generally, about how my team embraces its weaknesses as a strength. I've been thinking a lot about this lately.
0 kommentar(er)
