Good coding standards makes it so you can find code faster, read and understand it easily, and increase reusability. One hour of forethought and planning can prevent literally hundreds of hours of unnecessary upkeep, straining for interpretation, and possible future bugs.
On average programmers spend 10 hours reading code for every 1 hour of actual coding. If Coding Standards are used properly this can be reduced significantly. Imagine having to work 11 hours and knowing 10 of those hours will be reading and deciphering code so you can do one hour of coding and inserting it into the proper locations. If Coding Standards and Naming Conventions are strictly adhered to it is completely possible to change that so in an 8 hour day you spend only 4 hours reading code and the other 4 hours actually coding. Work 3 hours less and be 4 times more productive!
Did you know 70% of all software projects fail or never reach completion?
This video shows how to manage a software project and avoid the common pitfalls that doom a project to failure. In addition to project managers, software developers should also know this because in many companies there are no project managers.
Follow these guidelines in the PDF above or in this video and your Project Management skills will improve dramatically.
What do you do when the server crashes? Or data is corrupted? Some technology problem has taken your entire company offline?
This video outlines the 9 steps I have used which work every time, regardless of what kind of IT disaster has happened. Stop it from getting worse and how to handle it in the most effective and least stressful way.