When I began writing during LaunchX, I wanted to talk about something that is easy to overlook in technical discussions: software development is a human activity. We write code with other people and for other people. The quality of that work depends on how well we listen, explain, and collaborate.
Beyond the developer stereotype
There is no single personality that makes someone a good developer. Some people are quiet; others think aloud. Some enjoy games, music, or security challenges. What matters on a team is whether people can bring their different perspectives to the work and treat one another with respect.
I value colleagues who share what they know without making someone feel small for asking a question. I try to do the same when I can. A clear explanation, a thoughtful code review, or an honest account of a mistake can save someone else hours of confusion.
Think about the person using the product
An implementation can be technically elegant and still be frustrating to use. I admire engineers who ask what a person is trying to accomplish, what might go wrong for them, and whether the design makes their next step clear. Those questions belong in technical conversations, not only in design meetings.
I also appreciate leaders who stay connected to the craft and listen to people regardless of their title. Satoru Iwata’s career in games has long reminded me that leadership and technical curiosity can coexist. The lesson I take from that example is simple: understand the work, and remember the people it serves.
A principle I still use
I wrote this at the start of a learning journey. My experience has grown, but the principle remains: be generous with knowledge, stay curious about other people’s perspectives, and build with the user in mind. Technical skills matter. So does the way we use them together.