Who remembers the comic story about how bachelor, master and PhD carry out projects?

Question

Project management

I had a dispute about how detailed you need to think through a new project. Usually this is a double-edged sword, on the one hand, you run the risk of thinking through the project forever and never start anything. On the other hand, quickly nagovnokodit and get a working draft with a bunch of architectural errors. I remember at the university we were told a comic story about how a bachelor, master and PhD took on the same task (something like screwing in a light bulb). Unfortunately, I remember only the essence, but I don’t remember the story itself. It is somewhat reminiscent of this story bash.im/quote/420672.
The conclusion from this story is that a bachelor, not knowing about potential problems, is not afraid to just write a project. But having almost no experience, he will not write anything sensible. The master, having experience, but still not understanding all the problems, not realizing all his ignorance, writes the project. And he succeeds, albeit with problems and errors. PhD "understands that he does not understand anything", realizes the depth of the problems. And as a result, either does not start the project at all, or does it for too long.
I have two questions

1. Does anyone remember the whole story?
   
2. Are there any articles on Habré where you can read about such reasoning?
   

Answer 1

The one who dropped out of university after 1st year and 7 years in production writes better than all of them.

Answer 2

I saw two judgments (opposite).
First (structural programming method): write a ready-made program right away (like begin end), use stubs instead of non-working pieces, the main thing is that the program works right away. I’ll add on my own: the task must be written in English, so that later this phrase can be replaced with a function (ready from the library or your own, which will have to be written). I also saw advice: use classes (and interfaces) more. Then there is only step-by-step detailing. Although I saw another piece of advice: work out the structure in advance, for example, in UML.
The second advice from the MIPT courses on Arduino: do not start a project without detailed study. The host is a practitioner, so he will not advise bad.

Answer 3

https://geektimes.ru/post/268802/
About "complicators".
In general, it is impossible to say "how detailed to describe" in general.
Everything is individual, and the main thing is adequacy, that is, the ability to prioritize and correctly assess your qualifications in order to understand where you can describe in more detail, where not to get involved in the implementation and describe your vision of a working product, and where to seek advice.