Skip to content

Comment on Ask HN: How to turn off x86 Pipelining

Comments

I submit to you that there should have been a research spike of 8 to 13 points which was done first . The results of that spike would be your story and the preceding spike would have given you the implementation information. Even if the implementation is only 1 point, the documentation around why this is done would be more than 1 point. Because if you're not documenting in extreme detail on why this is done you're building tech debt because no one will remember.

The reason I say there needs to be a very detailed research spike is because this is almost always the wrong solution to whatever the underlying problem is. A 1 point story with no implementation details means this came about from some pontificating around theory without any actual a/b testing.

Sorry I don't have the answer to this specific thing other than you say it seems your entire process is broken here and you need a architect or sr engineer to push back on this. At minimum to provide implementation details but ideally to actually have the research to support it.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.