But if (for eg) you do what Salvatier recommends and look into the surprising amount of detail in "boiling water", it's both surprising how complex it is, and kinda boring unless you find a way to get interested in say convection physics and heat transfer in uneven metal plates.
-
-
Reality doesn't care whether a missing comma means millions in lost revenue because a website is down, or no-big-deal because it's an obscure site nobody visits. Reality doesn't care whether a bug manifests to you as a mystery taking 10 hours, or obvious 2 second fix.
Show this thread -
All it cares about is: you eventually get to adding that missing comma whether you get there in 2 seconds via luckily happening to notice it, or in 10 hours after spending hours and thousands of dollars exploring the wrong troubleshooting branch. It doesn't care if you're 8 or 80
Show this thread -
And this isn't even the hardest case since debugging in programming still means working within the minds of other humans who wrote the compilers and operating systems. It is possible to get weirdly efficient at debugging code. Not so much reality as in atoms stuff.
Show this thread -
Unlike code, nuts-and-bolts stuff has properties, features, and behaviors that weren't explicitly designed in by someone. So troubleshooting it is basically science. Leave your efficiency/productivity expectations based on delusions behind.
Show this thread -
Note... not always true. There have been cases of weird software bugs in history that arise from strange hardware/software coupling effects. Especially at scale, when for eg. you're dealing with hundreds of hard-disks.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.