New
#280
Hi,
That 'splains it then. :)"Any attempt to debug a program invariably introduces new bugs which are even harder to find".
Cheers,
Well, Happy New Year to all you insiders and may there be many more unstable buggy versions of Win10 next year
Believe me guys. troubleshooting can get dicey in other areas. Imagine a half ton machine part and a wrong thread pitch on a 1/2" bolt and you find out about that only after final assembly with few hundred parts.
Than you may run into a 3 door machine relay logic control cabinet with few hundreds of relays, each one with 12 NO/NC mixed contacts. Miles of wires crisscrossing all over the place and no schematic. One of the wires doesn't make contact or is broken in unknown place. Troubleshoot that !!!
So if a OS is buggy it shouldn't be debugged because it's going to create more bugs? If a piece of machinery is broke down it shouldn't be fixed because it going to be complicated to repair? I don't get it. In my opinion it would be easier(not easy) to fix any problems as they arise instead of letting them accumulate.
The problem with debugging is, One messpelling, one typo and Pffffft! It is hard, to find the typo, because our brain(not our eyes) sees what it expects to see, and not what is.
Did you notice I wrote mes-pelling instead of mis-spelling?