Re:A theory of how developers seek information
by sethammons on Thursday April 29, 2021 @09:44AM
(#26981069)
Love it. The same strategy was used by a colleague with a struggling team member. For that case, it was: show me a diagram. For nearly every question. The struggling dev just wanted to solve the issue so much, they were not stopping to understand the issue. Slow down to go faster.
[ Parent
| on HN ]
Re:A theory of how developers seek information
by plumsempy on Thursday April 29, 2021 @12:23PM
(#26983139)
> Slow down to go faster
yes! I had a similar problem with bigger projects. I used to start coding too early before understanding the problem completely.
I have decided to write an essay since, about everything I am about to do. This slows me down and makes me look at every detail that might be crucial in the project execution.
These docs then become some sort of a data lake about the process of building this project, from which later I can derive documentation or slides for presentations from or send people there when they ask me why I did something the way I did.