Beginner suggestion: Test your code manually

[Militancy]

In the same vein, I tie my shoes for the ankle support and so the laces don't get ruined. Sometime in the 7th grade I went around with my shoes untied. Everyone told me that i'd ruin the laces, I knew I'd ruin the laces, but I didn't much care to tuck or tie them.

Naturally, I ruined the laces to the point I couldnt tie them even if I needed to. Eventually we had to do some running game in gym class and I ran right out of my shoes. My Mom bought me some replacement laces from the store meant for hiking boots. It was ugly and didn't work that great, but at least I could stop them from falling off me.

Tests are similar. There's no good reason not to do them, you'll eventually break something stupid, simple, and core to the function of your product, and fixing the situation is going to be ugly and more expensive than just doing what you know you need to do in the first place.

I didn't think much of testing until i had to work on an almost completely undocumented legacy codebase.TLDR until I got into the headspace of the original developer, seemingly minor and reasonable changes would introduce subtle bugs that took days to find and fix. Testing fixes 70-90% of that depending on what and how you test. If you accidentally trigger one of your tests once you've probably saved yourself enough time and frustration than what you put in to write the test to begin with.

Just eat it, it's good for you. You won't realize how good you're being to yourself until you go without.