minus-square@[email protected]linkfedilink37•7 hours agoHmmm command not found, let me just try the same command a couple more times, this time it will work right? In IT teaching users to actually read and understand errors is always an uphill battle.
minus-square@[email protected]linkfedilink56•7 hours agoTbh I’d try it multiple times too, just because the concept of cd not being there is horrifying and cannot possibly be the case
minus-square@[email protected]linkfedilink15•6 hours agoVery true, I would do the same and feel my stomach drop farther each time.
minus-square@[email protected]linkfedilinkEnglish13•6 hours agoI learned early in my software engineering career these two beautiful rules of debugging: Read all of the words Believe them
minus-square@[email protected]linkfedilink1•1 hour agoUntil you write a compiler error in some deeply templated C++ code, in which case just reading every word takes all day /s but not too much
minus-square@[email protected]linkfedilink6•edit-25 hours agoUnless you were the one writing the program and its error messages - then check, that you didn’t mess up there…
minus-square@[email protected]linkfedilink4•6 hours agoWhere is the Windows ‘help’ button, did you try that?
Hmmm command not found, let me just try the same command a couple more times, this time it will work right?
In IT teaching users to actually read and understand errors is always an uphill battle.
Tbh I’d try it multiple times too, just because the concept of cd not being there is horrifying and cannot possibly be the case
Very true, I would do the same and feel my stomach drop farther each time.
I learned early in my software engineering career these two beautiful rules of debugging:
Until you write a compiler error in some deeply templated C++ code, in which case just reading every word takes all day
/s but not too much
Unless you were the one writing the program and its error messages - then check, that you didn’t mess up there…
Where is the Windows ‘help’ button, did you try that?