|
|
|
|
|
by Sebb767
1267 days ago
|
|
There's definitely a lesson in prioritization in there, as these task are mostly not dependent on each other. Hal already had the light bulb in his hand when he noticed the loose shelf and he already had the tools to fix the shelf when noticing the squealing. The only dependency in there was fixing the car to get WD40 and fix the drawer. From a business perspective, he could have finished the first two tasks before going to the next one - the total time to completion would be the same, but the business would have had 2/4 tasks completed and therefore a better product earlier. The fact that this is an article written by a software engineer that completely ignores the missing dependencies bears some irony :-) |
|
I don't think this is the case as the author mentions he assumes Hal follows the boyscout rule:
> at each step of the process leave the camp site a little bit nicer than it was when arriving
Which is the only way to get tech debt under control when tech debt is not a dedicated project (and thus receives no allocation)
It kind of punts on the dependency thing, the idea being that if you notice some small fixable thing then you might as well do it right now.
Which in turn makes the parallel with tech debt all the more on point, the joke being not so much about a singular chain of issues but about the household being absolutely drowned under a gajillion independent issues that keep making everything demoralisingly slow.