4 ms·
> Your application doesn't need logging until you have a problem that is solved by logging. It's possible that you never have such a problem. If that's so, then
by davidbanham 6y ago
> Your application doesn't need logging until you have a problem that is solved by logging. It's possible that you never have such a problem. If that's so, then building a logging subsystem is a waste of time.
Your application doesn’t need logging until _right before_ you have a problem that is solved by logging.
I don’t use frameworks these days. I’m glad I was exposed to their ideas in the past. I’m glad that exposure shaped my current approach. A framework is one of the ways that experienced developers can pass their knowledge on to less experienced ones.
- tlarkworthy 6y agoLogging is a weird one because now platforms (e.g. k8s) often offer that and it's a PITA getting your framework to stop persisting logs.
- dreamcompiler 6y ago> A framework is one of the ways that experienced developers can pass their knowledge on to less experienced ones. This. If you could hire a team of brilliant developers you wouldn't need a framework. Frameworks capture the design requirements of brilliant developers...but they're not your developers and they may not be your design requirements. The trick is to know when the framework's design requirements differ from yours so much that it's a better business decision to roll your own code than to change your requirements to match the framework. I kinda think far too many businesses change their requirements for reasons of short-term MVP and then paint themselves into a framework corner.