How software logs can save your company time, money, and team morale

Software logs are not solely technically important, but it can also save your company time, money, and team morale. Why?

Read story below between developers and their manager.

Photo by cloudvisual.co.uk on Unsplash

Point #1: Time lost

Dev-1: “Hey, I don’t think the bug is on web, it must be from the app”
Dev-2: “Can you prove that it’s indeed on the app?”
Dev-1: “I tested it, nothing change from the web, variable control is app, and last result with last app build, it does not work!”
Dev-2: “Hmm yeah, but it could be possible that your phone not working well, right?! Or even you forgot to connect to the internet or internet connection is not stable at the time you tested, possible right?!”

This happens quite often in development team. Each party pointing to others stating that he is not wrong. This kind of conversation can go on for several days and if sum up, in total it took hours, not included unnecessary testing time done by both sides.

Point #2: Hurt team morale

The worse thing, depends on how mature they are, each developer can take this personal. Making working relationship suffers and collaboration between them ruined.

Story continue to the other day next week…

Manager: “Hey dev-1, so how about the bug, what’s the progress? Have you sorted it out?”
Dev-1: “It’s still stuck because app fails to record the data”
Dev-2: “I think you don’t understand the expectation, can you tell me how it should work?”
Dev-1: “Yeah, it will not add any new data unless a user moves beyond 100 m radius, right?”
Dev-2: “Right. You know the time interval?”
Dev-1: “3–5mins”
Dev-2: “Right.”
Manager: “Dev-1, how many times you tested and can you tell me what’s the result?”
Dev-1: “I tested 2 times using different app builds. First one, can record data properly and precisely. Second one not recording at all.”
Dev-2: “But looking from backend data, it’s recorded”
Dev-1: “It’s not. That was the data when I tested using the first app build!”
Dev-2: “Yeah, but you have no proof!”
Manager: “Alright, can you send us your log dev-1”
Dev-1: “I didn’t know how to get that. Have asked other devs but haven’t got answer for that”
Manager (a little bit upset): “Hey team, what’s so difficult on letting other know how to get logs?”
Dev-3 then tells Dev-1 how to get the log.
Dev-1: “Alright, will send it to you the logs, Dev-2”

Turned out that Dev-1 is right, clearly shown on logs that app failed to send recorded data on the new app build.

If only they discuss things with logs from the beginning, they can save much hours not to end up in arguments and unnecessary testing comparing different things. Moreover attacking colleagues relentlessly will not be a good option. You will still need their help, soon or later.

There are several lessons on this story.

1. Does not matter what you are saying, when other does not trust you, only logs can be your last weapon. And we should use and discuss technical thing with it, always. As it works as technical proof for both arguing sides.
2. Logs can prevent unnecessary debate and can save team morale.
3. Being helpful to colleagues, since the first time they need help, can help you and your company save a lot of time.
4. If other points the bug to you, try to listen. And… position yourself as a good man who wants to solve this problem quickly. Instead of pointing back to other and start a long debate.

This story is only one case where software logs can help us a lot. In some cases, logs can help us figuring out difficult bugs. In other cases, talking in bigger picture, logs indeed drives and becomes the source of that “big data” that we keep hearing these days. Big data can benefit businesses from the real, massive, and detailed info on how a product is being used by users and then relate it with next business decision. Or… in the other way to say it: logs could be the next source of profits for your company, if you know how to make use the most of it.

So, if you still don’t care with logs, I hope after reading this, you can be wiser on treating logs. We need to create or design logs in a way all information that would be needed is captured. This could include software version, timestamp, server transaction, processes, etc until the tiny little bit that you might need.

We at Forstek take care of logs seriously. We believe being productive should be in all aspects, not only how we design and craft the products technically and how team work together, but also from all sides like these logs thing also treated carefully. That way, we don’t cause clients lose money to spend on “unnecessary development hours”.

Thanks for reading!