Re: Talk, Then Code

1 min read

My response to Talk, then code by Dave Cheney:

I cannot emphasize how important communication is in today's IT industry. In fact, if they paid me a penny for every time I have hurt someone's ego over code, I would be a millionaire. It is not pleasant. I know, I have been on the opposite site as well. 99% of the arguments in today's software projects are not because of lack of skills, but due to miscommunication. Our industry killed the one thing that makes us human beings - meaningful verbal communication. Covered by our headphones, hiding from what it seems a myriad of meaningless meetings, we often spend time developing stuff that does not fit into the final picture. And then, ego prevails, and feelings get hurt.

The underlying cause of all these issues is a lack of communication. The goal of the talk, then code philosophy is not to impede or frustrate, but to ensure that a feature lands correctly the first time, without incurring significant maintenance debt, and neither the author of the change, or the reviewer, has to carry the emotional burden of dealing with hurt feelings when a change appears out of the blue with an implicit “well, I’ve done the work, all you have to do is merge it, right?”

via Talk, then code

Previous article


The first signs of Spring are here. Perhaps, too soon, but for whatever it's worth, enjoy the ☀️ while you can!

Next article


Blog style update: This morning, I changed a few of the styles that display micro-posts. Thanks to reader feedback, I realized that people would often

Related Articles

Elixir Tip: Case vs. With
3 min read
Elixir Is Not Ruby. Elixir Is Erlang
2 min read

Is Roam Research Worth It?

Probably not, if you ask my opinion. Whether you like it or not, Roam is a glorified outliner, similar to

1 min read

Write Stupid Code

This is very much a re-interpretation of a post by Thorsten Ball, written back in 2015. Like him, I too

1 min read