问HN：你如何判断一个工具是否解决了一个真实的问题？
嗨，HN，
我正在构建一个系统，位于应用事件和下游消费者（分析、决策系统、人工智能等）之间。
目标是使原始产品事件更加结构化和规范化，从而更容易提取模式、洞察和更高层次的信号。
在深入之前，我想先对这个问题进行一些理性检查：
* 你如何验证这样的工具是否真的需要？
* 你是否在事件模式、分析或遥测方面感受到过真正的痛点？
* 目前有哪些工具已经很好（或不好）地解决了这个问题？
* 什么因素会让你尝试新的解决方案？
我并不是在推销，只是想避免构建一些没人需要的东西。
很想听听你的经验。
谢谢！
查看原文
Hi HN,<p>I’m building a system that sits between application events and downstream consumers (analytics, decision systems, AI, etc.).<p>The goal is to make raw product events more structured and canonical, so deriving patterns, insights, and higher level signals becomes easier.<p>Before going deeper, I’m trying to sanity check the problem itself:<p>* How do you validate whether a tool like this is actually needed?<p>* Have you felt real pain around event schemas / analytics / telemetry?<p>* What tools already solve this well (or badly)?<p>* What would make you try a new solution here?<p>Not pitching, just trying to avoid building something nobody wants<p>Would love to hear your experiences.<p>Thank You