I don’t agree with Eisenhower. The wrong type of planning is useless. I planned around sub-goals, not individual programs.
I never had a problem with planning, even with the fastest developed app that I ever wrote (7.5 hours) which coordinated production between to plants. I had a short, but written plan before I started coding.
The last line of every plan was “Post implementation adjustments” because all programs have bugs and this prepared management, users and programmers for fixes in the first few days of use. Blame is a worthless concept. Just fix things.
Over a fifty year period, I never had a code review, partly because of smaller projects. I did code reviews for trainees, though. In one, I asked about a section of code, then pulled out one of my programs and added her code. I told her that I had been trying to solve that problem for a week.
I could have added it later, but I did it then to show her that the in-house expert could learn from the lowliest trainee.
I have no idea about the number of the lines of code in anything I wrote. Nothing counts until you put the app into production.
Finally, I explained things to my cat.