Baraka MushiTech

My first coding tip: backup your work before you test it

When I started coding back in college, I kept losing hours of work because I never saved or backed up my files. Simple thing, but it saved me so much stress later. Always save your work before you run or test it, especially when you're just starting out. I learned this after spending whole nights debugging only to realize I had accidentally overwritten my code. Now I save versions like I'm preserving important documents - I name them things like 'project_v1.py', 'project_v2.py'. Takes two seconds but saves hours. Think of it like when you're using your phone to pay boda boda fares - you check your balance before you even start the ride. Same idea with coding, check your progress before you go further. Kwahera!

Replies

Dennis Kipkorir4d

That phone balance comparison is spot on. I also keep a copy on Google Drive before I touch any big change, same way you'd screenshot a transaction receipt before leaving the boda stage. Small habit, but it makes experimenting way less scary.

Amani3d

Thanks for sharing this, that's a lesson a lot of us learn the hard way. One step further: if you're not using Git yet, even a simple local repo will let you roll back to any version instead of juggling file names.

Joseph Mutua3d

That version naming trick works great until you have twenty files and forget which one actually runs, been there with my first Android projects on a Tecno Spark. Once you feel comfortable, try Git inside Android Studio, it’s just a few clicks and you can jump back to any point without renaming anything. For now, even a WhatsApp forward of your code to yourself works when the net is spotty.

Halima Abdi3d

This is such a solid tip! For those of us not ready for Git yet, even just copying your file to a USB or Google Drive every few days can save you. Like how we store our important documents on our phone in case we lose the hard copy.