It's akin to praising people for generating many lines of code. But truly good programmers are the ones that write efficient, concise, and, hence, readable code.
Similarly, more planning and less typing is probably a good thing.
They wake up, judiciously hit the "{" key on their keyboard, taking a leisurely 500 msec to do so.
Immediately the floorboards start to creak. A framed cat picture shakes itself loose from its position on the desk and drops to the floor as a clinking, rattling sound of metal-on-metal builds. A deluge of gold coins is extruded from the bare earth itself as gaia supplicates herself to the 21st century god of productivity, the 100x developer. Now the sky can be seen to darken, as a tornado of 100 dollar bills sweeps over the area, hovering up the gold coins.
As the money maelstrom recedes in the distance, headed due west towards silicon valley, the 100x developer inhales deeply.
This will make a fantastic piece of motivational broetry for my linkedin, they think.
Double plot twist: after the 100x dev had left for greener pastures, nobody understands the system anymore and of course the initial afternoon of coding had no time for documentation or design reviews. The system has to be re-built and this time it will be built in-house with due attention to knowledge sharing and design documentation.
Triple plot twist: Several years later someone realizes that the in-house system is overly complex and maintenance heavy, then replaces it with some glued-together open source libraries on a Friday afternoon. The cycle continues.
Hey, that's just what I was thinking.
I interpret that as being implicit. If 3 minutes of planning are needed for 1 minute of coding, it's still alarming that half of a developers hours are going to...less important work.
I don't consider that less important work, but it does change the ratio for myself and other more senior members of my team to more like 1:6