20 months, 2K hours, 200K € lost. A story about resilience and sunk cost fallacy

Re:20 months, 2K hours, 200K € lost. A story about resilienc... by burnthrow on Monday January 04, 2021 @04:08AM (#25629077)

First, great blog post.

> The net result is data consistency across components/screens (which is great)

You probably don't need to be told this, but... how badly was the data really going to drift during a session? If a user notices that part of the UI is stale, they just hit reload, not a big deal. This could be improved later.

[ Parent | on HN ]

Re:20 months, 2K hours, 200K € lost. A story about resilienc... by dSebastien on Monday January 04, 2021 @05:21AM (#25629523)

Yep, good point. I do see it now. I absolutely didn't back when I started working on that.

I had just delivered & supported an enterprise front-end framework (https://stark.nbb.be/) for which we HAD to help fix issues with state management.

But of course, I just looked at it from the wrong point of view... The point of view of a technical guy, and not the one of a founder.

I'm learning.. ;-)

[ Parent | on HN ]