i guess i should probably have a better development methodology than "make lots of functions and then try to staple them together into one coherent program"
posts provided without warranty of any kind
av by @AviYinglet
i guess i should probably have a better development methodology than "make lots of functions and then try to staple them together into one coherent program"
only way to learn this stuff is to do it, in my experience. like i've tried to teach people design stuff at work but trying and failing (or rather, not succeeding completely) is a crucial part of it
i have to think "what problem do i, as the user of this program, want to solve?". i'm starting to mock up everything UX wise, then sitting down and actually coding it
my first one i ended up not doing that, and "make small chunks, test, make another small chunk" ended up with user interaction after every step rather than my desired thing of giving it some params and letting it chug through files for 6 hours.
(to be fair, some of those steps took like ten minutes before needing intervention, but it's still more babysitting than i like)