Friday Facts #366 - The only way to go fast, is to go well!

[hyperman]

Hi,

While I like this game, I'm going on a tangent here:

I'd like to both thank kovarex for and ask some more things about the ancient blog post https://www.factorio.com/blog/post/fff-366 (The only way to go fast, is to go well!)

Both the beehive analogy and the productivity graph are things I've demonstrated a few times already in multiple companies. They are great tools for demonstrating to non-technical management and customers why spending time on reorganization is not always wasted. The dev graph with near-linear code growth for 8x dev salay cost in particular tends to make managers slightly sick. The fact that it's real world data combined with the honesty of the FFF posts makes it very convincing.

So that's why I come with an ask: Is it possible to re-touch this subject in a future FFF? Some examples that might be interesting:

* Markers on the lines of code over time graph when new people started working in the code.
* A demonstration of code added (new features) vs code replaced (bug fixes) over time.
* A graph of users vs bug reports over time.
* Maybe you notice some signals indicating what the ramp-up time for a new developer is?

Apart from that, the non-development lessons from a developer are very welcome.

I understand it if you say no to any of this, or take the axis away and blur the graphs a bit. I re-awaken a 3 year old blog post , ask for potentially sensitive data, and take time away from your real work. Feel free to remove this post from the forum if it bothers you in any way.