The beauty of working on performance problems is that they are the simplest to measure – code still does what it was supposed to do before AND goes faster.


The problem is, we always do this after the fact, after the customer reported it, after we deployed it to QA and it blew up.  After everything went wrong.

We don’t do it before.

And that’s where we need to start bundling the work into what we do, from the beginning, from the moment we start, from the first day.

It will be a change to our coding and process, but once we start doing it, once we start ingraining it into everything that we do, that’s when we’ll see start to avoid the value in our customers not reporting it for us but instead providing that story that everything we write – is performant and can scale.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.


Write A Comment