It’s one thing to have openness, but it’s another to be productive while doing so.
The problems that you encounter in software are as innumerable and random as the placement of the stars in the sky. Many folks will over-emphasize the science of software and become rigid with numbers, proof, and evidence in order to work through the problems. Meanwhile some people resort to the art of software and find themselves using instincts for how they solve problems.
Neither of those is inherently wrong. But they also are not always correct. And it’s this dichotomy that presents itself in software and very few other crafts, that makes it uniquely fitting for the mindset of “I don’t know, let’s find out together”. Some may consider this a recasting of the beginner’s mindset. Others may identify this as scientific method, and that is why it is such a perfect tool for us to improve our daily experiences building software.
To read more, signup for the Attainable Newsletter:
Attainable Newsletter | Substack
Healthy Software Development - articles and information about Attainable's professional coaching, as well as profiles in software. Weekly content, and monthly profiles. Click to read Attainable Newsletter, a Substack publication. Launched 3 months ago.
newsletter.attainable.engineer
To read this article:
I don't know, now what? - Attainable Newsletter
It’s one thing to have openness, but it’s another to be productive while doing so.
newsletter.attainable.engineer
Top comments (0)