A day in the life of a reactionary programmer

submitted by fschmidt from self.programming

sorted by:
top
newinsightfulfun
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 insightful - 2 fun2 insightful - 1 fun3 insightful - 2 fun -  (4 children)

https://linux.die.net/man/8/logrotate

[–]fschmidt[S] 2 insightful - 2 fun2 insightful - 1 fun3 insightful - 2 fun -  (3 children)

I need to write a post on why configuration files should be banned. Maybe next shabbat.

[–][deleted]  (2 children)

[deleted]

    [–]fschmidt[S] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (1 child)

    Then log rotate handles all the business logic seperate from my code, and I get to "code" the log storage behavior in a "language" designed for that task.

    Pointless separation is one big source of complexity. There is no reason for an end-user to ever configure logging. The app code should do that. And so it might as well do it purely through code, so no need for logrotate.

    [–]trident765 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (0 children)

    Pointless separation is one big source of complexity

    I was just thinking about this the other day. It's the thing people say to sound smart. People say to keep X and Y separate because it makes them look like they had the foresight to prevent some bad thing from happening if you mix X and Y. So people are stuck maintaining this pointless separation because if they were to question it they would look like stupid people who didn't have the foresight to understand why you have to keep X and Y separate.