As developers, sometimes we think if think “if I just knew more about x technology, then my job would be easier”.
So we spend years of our lives reading documentation, practicing syntax, and learning more about the systems we work with.
That is wonderful.
But oftentimes, the technical part is not the hardest part.
It’s figuring out what to build and how to build it.
The internet has vast resources to help you actually code the thing. This makes each tactical coding decision relatively easy.
But the “who”, the “what”, and the “how” of software development is more fuzzy. Questions like -
- Why is our product failing? What do we need to build to make it more successful?
- What tools, paradigms, and architecture should we use? What is overkill now vs. what should we build out now to help us long term?
- How maintainable is this solution we’re building? What are the latest trends we should incorporate?
As a technical team member, invest time in understanding the human processes and systems you’re embedded in, independent of your technical deliverable.
Oftentimes that’s the next step to greater growth.