Code doesn’t have to be a mess
I think this is terrific advice.<p>Over decades I have compiled my own list which contains all these and bunch of other behaviours that are needed for successful project.<p>I would add one or two very important thing missing from the list.<p>One, not explicitly mentioned but covered in other points is to <i>plan for simplicity</i>. Make simplicity an explicit goal of the project and set up process to remind of it at various important points in the process. For example, I have a checklist for adding a new technology which has a very long list of things you have to think about before adding new tech of any kind (like &quot;is it possible to replicate it with couple pages of code&quot;). My goal is to have tech stack so simple that newcomers can feel right at home and productive immediately.<p>Even if I (we, me and my team, whatever) screw up, then the future owner will tend to have much easier time fixing it if we tried to keep it simple. My hardest challenges were not difficult technical problems (most backend applications tend to be very simple problem from technical point of view) but rather past teams that were very smart and created a monster so complex they themselves ground to a halt after some key people left.<p>And connected to it (part of the checklist) is to be aware of when you are about add things to the project for intellectual gratification rather than practical purpose -- and cut it mercilessly out.<p>Engineers tend to really dislike working same technology all over again, but this is what is needed to become really proficient. It seems exciting, but every time you add or change something in the stack you need to learn that thing (and accept being less productive for some time), you accept risk of new problems (and risk is a cost) and, finally, you cause the same to every team member and any future hire.<p>And while it is easy to see the benefits of something, the costs and risks are usually much less understood before you have invested enough in it. And, additionally, frequently the benefits are much overvalued.