Developers can often be a little too keen to start cutting code, but we can save a lot of time and headaches if we do a little work up-front to clear the way. Jason discusses what he might do before he starts writing code to visualise high-level design, choose and prove a technical architecture, and get the delivery pipeline up and running so he can start delivering working software straight away.
Jason Gorman
Jason's been writing software for four decades, and been a professional developer for three. He's cut code, led teams, and architected solutions for a wide range of companies in banking, retail, logistics, media and CAD. He's been championing Agile technical practices for 20 years, teaching and mentoring teams and promoting practices like Test-Driven Development and refactoring online, at conferences, and across many software developer communities.
- https://twitter.com/jasongorman
- https://twitter.com/codemanship