The tensions at technology choice (new shiny vs old stable) is only part of the problem. Even more important is to build a common understanding of development and operations needs. By having such rapport technology choice becomes secondary issue.

An excellent example is logging and monitoring of an application. Quite often developers (myself included) feel the need to log everything, even on production. Something that is completely fine and useful at development and testing phase can became quite burdensome at production. It often combines with leaving framework defaults, which can generate lots of noise.

Huge amount of logs are difficult to transmit and store, not to mention are very hard to reason about. Just imaging yourself being called up in the middle of the night for emergency situation. You’re being sleepy, while other people are already nervous, because situation is serious. In such stressful state you have to figure out what happened by looking at the mess in logs.

I understand that making log messages useful is difficult. Clarity and brevity are hard to achieve, but well worth it. It is a path to becoming better developer and better person.

--

--

--

Father. Husband. Solutions developer profesionally (software quite often). Arsenal supporter. Cyclist.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adam Brodziak

Adam Brodziak

Father. Husband. Solutions developer profesionally (software quite often). Arsenal supporter. Cyclist.

More from Medium

Six Super Ways For Language Development In Kids

Your emotions, your power

9 Enlightening Things That Med School Has Taught Me (Besides Anatomy Of The Upper Limb)

Parts of Speech: Don’t Drown in All these Nouns