Julio Biason .Me 4.3

This is a cynical, clinical collection of things I learnt in 30 years working with software development. Again, some things are really cynical, others are long observations on different jobs. If you don't know what you're trying to solve, you don't know what to code. Write something specifying how the application works before writing any code. "Without requirements or design, programming is the art of adding bugs to an empty text file." -- Louis Srygley Sometimes, even an "elevator pitch" -- up to two paragraphs that describe what the application does -- is enough. The times I stood longer looking at my own code wondering what to do next were when we didn't have the next step defined. It is a good sign that it's time to stop and discuss it with your coworkers -- or maybe rethink the solution. If you have no idea how to start, describe the flow of the application in high level, pure English/your language first. Then fill the spaces between comments with the code. Better yet: think of ev

This is a cynical, clinical collection of things I learnt in 30 years working with software development. Again, some things are really cynical, others are long observations on different jobs. If you don't know what you're trying to solve, you don't know what to code. Write something specifying how the application works before writing any code. "Without requirements or design, programming is the art of adding bugs to an empty text file." -- Louis Srygley Sometimes, even an "elevator pitch" -- up to two paragraphs that describe what the application does -- is enough. The times I stood longer loo