If you only write tests for things that won’t fail, you’re doing it wrong. Are you anticipating some other feature coming soon? Write a failing test for it. Did you find untested code that might run soon with a little work? Write a test for it. Did a nonessential feature break while adding an essential feature, let the test fail and fix it later.

My favorite messages are “Don’t touch this file unless you talk to Gary. Don’t import this file unless you talk to Gary. Don’t even think about this file until you talk to Gary!” And Gary has moved on and hasn’t worked there for years.

“Costs more to repair than it’s worth” is a useless distinction. You’re not buying your car again, so that number doesn’t mean anything. The only metric for how much a car costs is how much it would cost to repair versus the cost of a new car. Almost always, a new car is more expensive than continuing to repair an old car.

Do you have a car payment? If so, don’t buy anything until it’s paid off. Are repairs costing you more than a new car’s payment? If so, look into replacing it.

You definitely shouldn’t consider switching to a completely new mode of transportation to replace your car without first trying it out and keeping the car as a backup. Make a list of all your transport needs, where have you gone in the past year? Is there a viable car alternative for all of those things?

There was never an original with “kid named paint”, it was always “kid names finger”, and r/OkBuddyChicanery just had so much brain damage this became the top meme of all time.

All yaml is just sparkling JSON.

As someone who just switched, this isn’t something you should sleep on. I tried another instance and it was insanely slow in comparison. You might need to try a couple of places to get it right.