this is an issue I haven't found a good approach to yet. How much work should I put into testing an idea before I commit to the project?
On the one hand it can be more benefitial to do less testing and just take the hit when a project goes south, on the other hand doing too little testing might result in sinking alot of time in projects that crash and burn.
Some ideas I don't think aren't even that testable, if you don't just do the whole thing, or tests would be so time intensive that you might just as well do the project without testing.
Another problem I encounter is that if I start to calculate such things too much I kind of start to freeze up and end up with not starting anything, because my mind is too occupied with juggling factors.
Not to speak of the me constantly miscalculating and not grasping what I am getting myself into alot of times. I hope to avoid string catastrophies in the future.
https://www.youtube.com/watch?v=mKG26GZs5pM