how to make a computer program run faster

What every programmer wants, especially in the era of DevOps, is flow. So what do you really want when you say you want to 'go faster?' I'll tell you. They’re much more difficult to turn into action. The more specific tips don’t apply to everyone, but general tips are too, well, general. The utility of tips falls off as a function of specificity.

You must make strategic and tactical choices, and be prepared to take advantage of opportunities when they arise. The mechanical stuff is pretty easy to optimize the options are limited. While some of the mechanical things that work for me will probably work for you, many of the domain and pattern choices I made may be of no use. Many of these fall into the “personal journey” or “what worked for me” categories. Most of the tips I read only apply at certain points along my journey, and don't necessarily apply to everyone. What you need to go faster will change over time. This is the knowledge and wisdom that experience builds. To think faster, you have to learn more patterns and relationships. But most of our work as programmers isn’t typing, or compiling-it’s thinking. This can mean everything from typing to tools to thinking. To code faster, one has to be efficient that is, no wasted effort or motion. But, before I tell you what I found, I need to explain what I mean by 'programming faster,' and 'tips.'

Here are 53 tips representing the very best advice I've found out there. The problem is, there are far more out there than anyone has time to read, so I've boiled them down for you. Want to know how to program faster so that you can deliver software faster? Sure, who doesn't? The internet is full of tips for developers-hundreds, thousands, perhaps even millions of them.

How to make a computer program run faster