3 ms·
Yes. Your userbase will not give a single shit about how thoroughly tested your game is or how elegant your code is. Mainly since you'll give up on it long befo
by jstarfish 3y ago
Yes. Your userbase will not give a single shit about how thoroughly tested your game is or how elegant your code is. Mainly since you'll give up on it long before they ever see it.
It's a game. Treat it like one.
TDD is great for your day job, where you ship bulletproof software for work. Nobody does work for fun. Look at how many games are written in Java.
For a personal project, only write unit tests to ensure specific bugs get fixed. No more. This ensures you do the least possible amount of Work.
In the end, you'll say holy shit, I have a ton of bugs to fix-- that guy was full of shit. But you'll have a functional game to fix the bugs on within a year, rather than a pile of exquisite code that does nothing after a decade.
- unlikelytomato 3y agosounds very similar to the arguments made against tests in a work setting. Test as appropriate for your needs and goals. Adjust over time. There is no need to artificiality skew the balance in either setting.
- jstarfish 3y ago> sounds very similar to the arguments made against tests in a work setting I tried to be clear about that. Sloppiness at work could kill someone or bankrupt the company. You're being paid to be a professional, so be a professional and write tests. You only have so much free time to achieve your dreams. Cut every corner you can to make it happen.