|
|
|
|
|
by brudgers
236 days ago
|
|
I'm a solo developer To a first approximation, monitoring tools are built for teams, projects running at scale, and for systems where falling over matters at scale. And monitoring as a "best practice" is good engineering practice only in those contexts. You don't have that context and probably should resist the temptation to boilerplate it and considering it as moving the project forward. Because monitoring doesn't get you customers/users; does not solve customer/user problems; and nobody cares if you monitor or not (except assholes who want to tell you you are morally failing unless you monitor). Good engineering is doing what makes sense only in terms of the actual problems at hand. Good luck. |
|