> Writing messages on Slack isn’t what engineers get paid for, though. Writing code to solve problems is.

Perhaps I'm being picky, but... that's also not what engineers get paid for, either.

I think engineers get paid to do things that solve problems. Sometimes that involves writing code, but sometimes it absolutely involves writing a Slack message, having a call, or just thinking a little more.

A Slack message might be, "Got a minute to chat?" to start a voice call that will clarify some requirement that's been bogged down in a quagmire of too much writing or conflicting ideas. Requirements are clarified, maybe not a single line of code is needed to be written, thanks to a better understanding of the customer's desires.

A Slack message might ask, "Does this change work instead?" with an image attached of a simpler approach.

I wouldn't typically respond to one line from a blog post, but since this was up so high in the post, I felt I needed to gently encourage a little rewrite of this sentence :)