Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@polaroidkidd I guess it’s mostly because a log file often can reveal bugs and alike, that only occured in the backend - not visible to the frontend. It rends to also reveal lazy programmers, who don’t care about quality and warning signals.
Nowadays with all the data protection nonsense, it might also be useful to check for sensitive data stored in the log files. Although I would not guess that it was one of the reasons in this case.
I’m sure other people could add to this list. Any other ideas why checking log files after demoing would be beneficial? -
fleka286yThanks for your comments. Just some clarification: she is our backend dev, great one, but was not attending the demo. So after it we were happy that everything went well, at least in the front, but she immediately brought this up about the logs. It was a good laugh in a positive way.
I would do the same if I were her.
“I do trust you, just let me see the logs”
- our colleague after we present to her good feedback from the demo just passed ok
rant