If u dev in practical stages, u set up a minimum viable code to show that it's working then expand & reiterate w each test. The more frequent the tests, the less code u have to examine to determine the error. Your jump around method seems rife w errors that u will have a hard time tracking down.
Boxing is different than game dev in that they practice over here in the gym and perform over there in the ring.
Unless you're taking an educational class (like GDQuest), your performance & practice are overlapping. You have a practical need for x result so now u gotta practice different methods to get it.
I've heard of this before - the idea to stop doing something while it still interests you, which makes it more likely you'll look forward to picking it back up again.
If u dev in practical stages, u set up a minimum viable code to show that it's working then expand & reiterate w each test. The more frequent the tests, the less code u have to examine to determine the error. Your jump around method seems rife w errors that u will have a hard time tracking down.
That is a very interesting point, you're making. I'm curious how will that work out :-D
Boxing is different than game dev in that they practice over here in the gym and perform over there in the ring.
Unless you're taking an educational class (like GDQuest), your performance & practice are overlapping. You have a practical need for x result so now u gotta practice different methods to get it.
I've heard of this before - the idea to stop doing something while it still interests you, which makes it more likely you'll look forward to picking it back up again.