Ticking clock

Ever stop to listen to a ticking clock? It’s one of those things you don’t hear unless you think about it, or someone asks you, ”ever stop to listen to a ticking clock?”

That seems to be much like some software deployments I been evolved with over the years. The software goes out into production and no one pays attention until the alarm goes off.

As devs pushing bits into the hands of our beloved customers, why don’t we take some time to listen to the tick of the clock. You can do this by checking the logs after a deployment, monitor cpu / memory usage or my personal favorite get a tool like newrelic and see what the impact of what you just pushed really is.

the take away: just because it was deployed to ”production” does not mean it’s done or you’re done - take time to look at what your software is doing after a release it WILL pay off.