There are periods in a programmer's life when most communication seems to be with the computer. More precisely, with the programs running on that computer. This communication is about expressing ideas in a machine-readable way. This is an exhilarating prospect: Programs are ideas turned into reality, with virtually no physical substance involved.

+

There are periods in a programmer's life when most communication seems to be with the computer. More precisely, with the programs running on that computer. This communication is about expressing ideas in a machine-readable way. This remains an exhilarating prospect: Programs are ideas turned into reality, with virtually no physical substance involved.

Programmers need to be fluent in the language of the machine, whether real or virtual, and in the abstractions that can be related to that language via development tools. It is important to learn many different abstractions, otherwise some ideas become incredibly hard to express. Good programmers need to be able to stand outside their daily routine, to be aware of other languages that are expressive for other purposes. The time always comes when this pays off.

Programmers need to be fluent in the language of the machine, whether real or virtual, and in the abstractions that can be related to that language via development tools. It is important to learn many different abstractions, otherwise some ideas become incredibly hard to express. Good programmers need to be able to stand outside their daily routine, to be aware of other languages that are expressive for other purposes. The time always comes when this pays off.

Line 9:

Line 9:

Beyond communication with machine, self, and peers, a project has many stakeholders, most of whom have little or no technical background. They live in marketing and sales, they are end users in some office (or store or home). You need to understand them and their concerns. This is almost impossible if you cannot speak their language &mdash; the language of their world, their domain. While you might think a conversation with them went well, they probably didn't.

Beyond communication with machine, self, and peers, a project has many stakeholders, most of whom have little or no technical background. They live in marketing and sales, they are end users in some office (or store or home). You need to understand them and their concerns. This is almost impossible if you cannot speak their language &mdash; the language of their world, their domain. While you might think a conversation with them went well, they probably didn't.

-

If you talk to accountants, you need a basic knowledge of cost-center accounting, of tied capital, capital employed, et al. If you talk to marketing, [http://en.wikipedia.org/wiki/AIDA Aida] should be familiar to you. All these domain-specific languages need to be mastered by someone in the project, ideally the programmers. Programmers are ultimately responsible for bringing the ideas to life via a computer.

+

If you talk to accountants, you need a basic knowledge of cost-center accounting, of tied capital, capital employed, et al. If you talk to marketing or lawyers, some of their jargon and language (and thus, their minds) should be familiar to you. All these domain-specific languages need to be mastered by someone in the project - ideally the programmers. Programmers are ultimately responsible for bringing the ideas to life via a computer.

-

And, of course, life is more than software projects. If you want to relate to people beyond the software industry, it may worth appreciating that this can be harder than passing a camel through the eye of a needle. To know when to listen rather than talk. To know that most language is without words. To be.

+

And, of course, life is more than software projects. If you want to relate to people beyond the software industry, it may worth appreciating that this can be harder than passing something through the eye of a needle. To know when to listen rather than talk. To know that most language is without words.

Revision as of 16:29, 23 July 2009

Programmers need to communicate. A lot.

There are periods in a programmer's life when most communication seems to be with the computer. More precisely, with the programs running on that computer. This communication is about expressing ideas in a machine-readable way. This remains an exhilarating prospect: Programs are ideas turned into reality, with virtually no physical substance involved.

Programmers need to be fluent in the language of the machine, whether real or virtual, and in the abstractions that can be related to that language via development tools. It is important to learn many different abstractions, otherwise some ideas become incredibly hard to express. Good programmers need to be able to stand outside their daily routine, to be aware of other languages that are expressive for other purposes. The time always comes when this pays off.

Beyond communication with machines, programmers need to communicate with their peers. Today's large projects are more social endeavors than simply the applied art of programming. It is important to understand and express more than the machine-readable abstractions can. Most of the best programmers I know are also very fluent in their mother tongue, and typically in other languages as well. This is not just about communication with others: Speaking a language well also leads to a clarity of thought that is indispensable when abstracting a problem. And this is what programming is also about.

Beyond communication with machine, self, and peers, a project has many stakeholders, most of whom have little or no technical background. They live in marketing and sales, they are end users in some office (or store or home). You need to understand them and their concerns. This is almost impossible if you cannot speak their language — the language of their world, their domain. While you might think a conversation with them went well, they probably didn't.

If you talk to accountants, you need a basic knowledge of cost-center accounting, of tied capital, capital employed, et al. If you talk to marketing or lawyers, some of their jargon and language (and thus, their minds) should be familiar to you. All these domain-specific languages need to be mastered by someone in the project - ideally the programmers. Programmers are ultimately responsible for bringing the ideas to life via a computer.

And, of course, life is more than software projects. If you want to relate to people beyond the software industry, it may worth appreciating that this can be harder than passing something through the eye of a needle. To know when to listen rather than talk. To know that most language is without words.