As developers, when building new projection from the ground up, we have a tendency to shoot first and ask questions after. Facebook popularize this posture with their old motto, & quot; Move Fast and Break Things, & quot; and it & # x27; s a notion that seems to have been firmly embedded into startup culture. Unfortunately what oft happens is that once things get separate, we fix them with Band-Aids and duct tape in order to keep up the fast footstep we & # x27; ve established. While we often put a premium on the end result, the foundation we build to achieve that result is just as important. For every line of hacky codification we write, still if it does what it & # x27; s conjecture to, we are compound the amount of employment that future developers on a project will have to do when you feel your company is finally in a place to & quot; do it right. & quot; In the face of legacy code, we will always be pushed to compromise quality for speed, but it is important to communicate the true impact code debt has on the hereafter of a project. Eventually, Facebook memorise this lesson, changing their slogan last yr to & quot; Move Fast with Stable Infra (construction). & quot; By putting an emphasis on stability, Facebook essentially enacted a speed limit on development to encourage bug-free codification. So, how do we balance speed and calibre? The response, unsurprisingly, is by establishing a set of prescript and processes for you and your team to postdate. Before start any work on a new covering, it is important to lay the proper groundwork. This is the time to set up your deployment processes, variant control management workflow, and unit exam frameworks. In addition, you should be utilise this time to make out your code fashion guidebook and project your application architecture. Over time, a well thought-out development operation can provide exponential benefits; the most crucial of which is reduction of the time it takes to onboard new developer. I am a big proponent of utilizing strongly supported third-party imagination for this accurate reason. A new developer is go to be generative far earlier when he or she is confront with an launch deployment workflow, a well-documented development architecture, and commonly utilized third-party resources. Don & # x27; t consider me? Then ask yourself which new developer is going to be better set up for success: The one working with an architecture that is built 100 % in-house, or the one working with a system built on top of established frameworks like CodeIgniter, Bootstrap, and AngularJS? This sparks a whole different conversation about when to use frameworks and when to start from dough, but the same underlying rule of productivity and dependability applies. The more decisions you can get up front to normalize your development processes, the low the fortune you get of dealing with code debt in the futurity. While enacting a proper set of guidelines will specify your evolution zip a slight bit, it will greatly trim the amount of bad codification that acquire put into production, and limit the code debt you will have to deal with in the future. Additionally, the more forethought you put into planning the future of your workflows, the more convinced and successful every member of your team will be, which will not only cut the clip it takes to onboard a new developer, but also provide more constancy and proportionality to both the codebase, and your working hours.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Zachary Flower (@ zachflower) is a independent web developer, author, and polymath. He has an eye for simpleness and usability, and strives to make products with both the end user, and occupation end, in mind. Zach takes a potent stand against needlessly reinvent the wheel, often urge for well prove third-party services and solution to improve the efficiency and reliability of a maturation project.