My first job at college had schedules with high-level and detailed design, then coding, then integration and test. Coding was only 3-5% of the time. Also, I r

My first job at college had schedules with high-level and detailed design, then coding, then integration and test. Coding was only 3-5% of the time. Also, I remember learning to race. I tried to learn to go faster through the turns. But it turns out the way to be fast was to go a little faster on the straightaway and long turns. Trying to go faster through the tight turns doesn't help much. If you go 1 mph faster for 10 feet in the slowest turn, it doesn't make as much difference as going .1 mph faster in a long 500 foot turn. so... Are we trying to haphazardly optimize for the small amount of time we code, when we should spend it elsewhere?