Hackystat 仅在学术上有趣吗？
发现了 Hackystat，并惊讶地发现这个项目
- 自 2001 年以来已经存在了
- 50 个公开版本
- 我偶然 积极开发
……但 StackOverflow 上没有任何关于它的问题。
是否有人出于非学术（即“现实世界”）原因而使用任何传感器或系统本身？有人有什么经验吗？
I stumbled across Hackystat and was surprised to see this project has
- been around since 2001
- 50 public releases
- pretty active development
...but there is not a single StackOverflow question about it.
Does anyone make use of any of the sensors or of the system itself for non-academic, i.e. "real-world" reasons? Any experiences at all anyone?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我愿意相信我们的系统和文档的质量是如此之高，以至于不需要 Stack Overflow 问题，但这可能不是原因。 :)
我认为 Hackystat 的主要用户群确实是学术界。我相信这是因为如果您只对流程/产品的相对简单的属性感兴趣，那么有很多软件流程/产品工具的安装和使用要简单得多。如果您只想了解覆盖率或其他方面的基本趋势，那么可能有一个 Hudson 或 Maven 插件可以很好地完成这项工作，并且比 Hackystat 的配置和安装开销更少。
当您想要做一些更复杂的事情时，Hackystat 开始看起来不错，例如通过将开发人员的开发行为与 TDD 基于规则的操作定义进行比较来推断开发人员是否正在进行测试驱动设计。这种“复杂”的问题使用 Hackystat 比使用 Hudson 或 Maven 插件能更好地解决，但超出了大多数公司的典型分析需求。
另一个因素是，虽然 Hackystat 的架构与语言无关，但绝大多数传感器设计为仅收集基于 Java 的系统的数据。这对用其他语言编写的系统造成了进入障碍：要利用分析，必须首先为新语言实现传感器。
I would like to believe that the quality of our system and documentation are so high that there has been no need for Stack Overflow questions, but that's probably not the reason. :)
I think it's true that Hackystat's primary user base is academia. I believe this is because there are a lot of software process/product tools that are much simpler to install and use if you are only interested in relatively simple attributes of your process/product. If you just want to know basic trends in coverage or whatever, then there's probably a Hudson or Maven plugin that will do the job just fine with less configuration and installation overhead than Hackystat.
Where Hackystat starts to look good is when you want to do something more complicated, such as inferring whether or not your developers are doing Test Driven Design by comparing their development behaviors to a rule-based operational definition of TDD. This kind of "complex" question is much better addressed with Hackystat than with a Hudson or Maven plugin, but goes beyond the typical analysis needs of most companies.
Another factor is that while Hackystat's architecture is language-independent, the vast majority of sensors are designed to collect data only for Java-based systems. This creates a barrier to entry for systems written in other languages: to make use of the analyses, one would have to first implement sensors for the new language.
我相信有一家名为 6th Sense Analytics 的公司对 Hackystat 进行了商业分叉，该公司随后被 Rally software。因此，Hackystat 的某些风格可能会以不同的名称在工业中使用。
I believe there was a commercial fork of Hackystat by a company called 6th Sense Analytics, which was subsequently bought by Rally software. So some flavor of Hackystat may be in use in industry under a different name.