Enforce coding standards on build (CI).Use tools that can automate but do not depend on them (phpcs, CI).Debugger provides full context in your IDE, and you keep looking at the code. It avoids print - refresh - delete flow (and also avoids to let debug message in your code). Use your debugger, it saves a lot of time at short term.Have a good IDE: it knows much than you and you have to know it.Let printed cheatsheets close to you, they will not take space on your desktop.Work on a clean desk, avoid a cluttered desktop, just get the windows you need to code.Also disable as many notifications as you can (mail, Slack, Trello. Avoid interruption: recovering a 5 minutes interruption = 1h to get back to full code productivity. Do not depend on your colleagues too much, one day they will leave, and it is much more valuable to solve your issues without relying too much on the others. Explain your issues… even to a rubber duck : ) phrasing issues will help to solve them partially.Keep it simple: any new feature must be tested and can introduce bugs.Plan the implementation, a good preparation is half the work done.Do not make assumptions: know what you have to do or don’t do it.Educate your client to phrase requirements.I will begin from the more general (attitude) and end by the more specific (coding with D8).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |