Was talking to my sister yesterday about how a lot of programming in practice involves iterative tweaking and hoping things will work, without necessarily taking a step back and thinking more deeply about the problem
This iteration will work, I swear
wait is it supposed to be like that
cause usually i deeply submerge myself in tons of theory work before i write something big dsfkgfdk
Oh I wasn't trying to say that iteration is necessarily good, just that it's common. I think thinking about a problem a lot before writing code is often fine, as long as you don't run into analysis paralysis
oh true yeah i didn't think that's what you were saying, more just like this kinda "that would be funny if most programmers are just winging it with constant iterations while i just sit here thinking through every major aspect in advance"
though yeah analysis paralysis is a thing i get a lot LMAO, but sometimes i manage to kick myself into actually Writing things, thankfully ^^
It's a better world in a lot of ways - like things not taking forever - but there are some issues like this where I kind of miss the days when building the application took so long (at one of my first jobs, the optimizing compiler ran over the weekend, and wasn't always done by Monday morning) that we couldn't just lean on interactive debugging.
