Pro tip: Setting up auto backups took me 6 hours because of one word

I lost a client file last month and decided to finally set up automated cloud backups. I spent 4 hours digging through settings and watching tutorials that didn't match my drive model. Turns out I was searching "external backup" instead of "external drive sync" the whole time. The difference was just one word in the software's menu and it took me 2 more hours to stumble across it. Has anyone else wasted hours on a simple search term mismatch?

3 comments

3 Comments

thomasgonzalez7d agoOG Member

Man I feel that. One wrong word and you're lost in the weeds for half a day.

the_oliver7d ago

Friend of mine spent three hours debugging just because he typed "then" instead of "than" in a condition check. Lol. Made me feel way better about my own screwups.

spencer_gonzalez17d ago

Honestly I used to think these little typos were no big deal, like computers are smart enough to figure it out. But then last week I spent two hours chasing a bug in my own code and it turned out I wrote "if x then y" instead of "if x than y" in a comparison. Felt like such an idiot. @the_oliver your friend's story made me realize it's not just me. That tiny swap of letters can completely flip what the code does and throw everything off. Now I triple check every time I write a condition. It's crazy how one letter can waste hours of your life.