realizing now that i've learned so much in the past decade that i never thought i'd be able to after reaching adulthood. i think things can become harder to learn when you're not a kid anymore, but you also start learning in different ways than before
i also think we get caught up in loops we tell ourselves about "learning the right way to do things" and "creating something you can sell" that it stifles our ability to get to those "aha" moments. at least it feels that way for me
instead of just throwing together as much absolute nonsense as i can get away with to get where i wanna be, i find myself being very slow and methodical to ensure that i'm not creating a ton of re-work for myself. something i never considered when i was younger
and this results in me starting a lot of things but struggling to stay interested or engaged long enough to complete it or get to the place i originally wanted to be with an idea. start/stop/start/stop a bunch of times until i'm proficient enough at starting to let me take off
i also learn more and more about the things that go into every smaller aspect of a process, so the number of branching paths to consider gets pretty painful quite fast. lots of horizontal productivity and much less vertical growth over time
no real major point to make here. i start a lot of things and don't really know where they're gonna end up going. maybe thats the point :P
@soup_reviews i can relate to that. what seems to work for me (if anything works) is keeping my various projects in a state where I can hop in, make a little progress, then hop back out. I can't throw myself into my latest obsession for weeks the way I did in my teens and early twenties, so having bite sized pieces means I can still enjoy things when the fancy strikes me and have it not feel like a waste
@2ck i dunno if i just need to change my approach or what, but typically when i reload a saved project from where i was at, i am more lost than if i'd have just started over again
@soup_reviews something I got from Test-Driven Development (TDD) is have something that shows you what the last problem was. It works kinda like a cliff hanger, I guess, in that it persists longer in your memory, but also it's something you can immediately start to do something about next time without having to recapture *all* of your past mental state.
I guess you work with music synths a lot? I know nothing about that, but maybe there's something like having some sample you run through your patches (right term?) that helps orient you? or maybe leave yourself detailed notes when you come to a stopping place
@2ck last-problem flagging might be a good idea. or i should build a logger than keeps track of all the things im doing when im working so i can follow the flow back to where i was