20

Wasted a total of 4 plus hours. Realized one of the windows registry keys I created wasn't working due to a typo. "comand" instead of "command". FML

Comments
  • 2
    Welcome to multiple frustation and confusions of a developer.
  • 1
    I ranted about how I lost a day and 3 hours trying to fix a compatibility issue that was just a typo.
  • 1
    What was the error it spat out?
  • 0
    @electrineer Windows just gave a generic message since it couldn't find the appropriate key it was looking for.
  • 1
    @KushagraKarira I'd much rather deal with pointers. At least that way I can debug it. Windows is not helpful at all for letting you know *what* went wrong...it either completely works, or completely fails.
  • 0
    @BobbyTables and it took you 4 hours to find out that a key was missing?
  • 2
    @electrineer It took me that long to realize I had mistyped it (though to windows it looked like it was missing). Part of the problem was I wasn't even sure if I was doing it the correct way since I was piecing together information from like 8 different sites.
Add Comment