Damian is an experienced software developer, architect, trainer, and agile engineering consultant.
In his 20 year career he has built high performance “fire fighting” teams for projects gone wrong, been a CTO for early stage startups, built and run high profile and high traffic websites, mentored and trained hundreds of developers, and consulted on software architecture for companies of all sizes.
Throughout this he has developed strong opinions on the architectural patterns, engineering techniques, and team dynamics needed to make successful software.
When he’s not in front of a laptop, you’ll probably find him riding a bike around Brisbane.
Typing is not the bottleneck
What does good enough look like right now for your product, team, or project? Are you investing in features you think you’ll need in the future because going back and changing things is too hard?
As individuals and as teams, we often deliberate for days (or longer) on the perfect solution, because we can’t decide on the “right way” to build something.
However, typing code is rarely the slowest part of delivering software.
We also often get caught by surprise near the end of a project by things we didn’t anticipate. Too often the lesson we learn from this is to spend longer analysing requirements and design.
This talk will explore how optimising for learning, and having a bias for action will help you iterate towards a better solution faster.
Damian will discuss some concrete patterns, techniques, and strategies that software teams can take to get working software in the hands of users earlier, and help you build the right thing.