Ask HN: Which everyday skill is important to master as a software developer?

Listening/observing because you really need to understand why you build what you build and depending on what you are building you'll only figure out the "why?" if you listen / observe deeply without preconceived notions. I've tried to improve this skill for years and still struggle with it!

Writing because once you've absorbed the information, you need to synthesise it and there is no better way to challenge your own thinking than writing. I always thought I was good at writing until I read a few books about writing skills and then read a few books (both fiction and non-fiction) and assessed the quality of writing with these basic ideas in mind. Only then did I realise that I suck at writing. It's really hard to write well, but if you can write well you have the most powerful tool at your disposal as it can scale the thoughts and ideas of one individual to millions or even billions of people. It might also just convince a bunch of teammates to follow your lead :)

You make money by being able to do things other people can't do, or won't do. Most programmers won't or can't learn to do these well, so those that do get a very big leg up. When execs and owners try to figure out who should become dev leads, managers, CTOs, etc, they will be looking for these skills in addition to technical chops.

In regards to learning itself.

- Trying to be open to any language, stack or technology concept or paradigm. And be devoid of fanboyism. Pick no favourites but trying really to look at the broad spectrum of software development. See what different paradigms bring to the table.

- Be good at discussing technology with people and listening to them. Learn to communicate in an open manner, ask 'Why', 'How would you solve X' instead of 'That won't work' when you are unsure of the ideas of others.

- Try not to search for affirmation but try to find honest discussions.

- Leave your ego behind

- Become good at selecting which whom you discuss with, and divide your energy and attention accordingly. I.e I usually have more meaningful discussions with people that tried a lot of different paradigms, technologies and finally settled at some stack.

- Understand that sometimes you choose a lesser technical thing or solution, because the team can't work with it yet. - Become good at dissecting hype, but be open minded and not bitter.

- If you want to grow hang out with people that are better then you and learn a lot from them.

- Learn how to learn.

- Keep a learning log/diary for yourself. For reference and to see how far you've become.

- Find the right attitude and motivation for learning. Try not to think I can't do this. But think. In 3 years I'll be able to do X y z. I can still suck a little for 2 years hurray!