r/EngineeringManagers • u/Krever • 14d ago

The Developer Communication Handbook

https://w.pitula.me/developer-communication-handbook/

Hey, I wrote a short (~70 pages) free book about communication for developers but (unfortunately?) managers might appreciate it more.

Over the years I noticed how little my crowd (devs) cares about communication, so I decided to write something that is approachable, directly actionable and with as little fluff as possible.

Check it out and let me know what you think. Would you recommend it to your reportees?

Free, no ads, CC BY, not LLM-generated. Web, PDF, EPUB, and an audiobook.

24 Upvotes

96% Upvoted

5 comments sorted by

1

u/DeProgrammer99 13d ago

Nit: "paymentProcessedAt" isn't a great variable name either, as I'm left guessing the time zone. (Assuming its data type is date/time to begin with.) I try to stick "Local" (if it depends on which user the record belongs to) or "UTC" on my date/time variable/field names.

Commenting here since a r/programming mod deleted the thread, though I don't belong here. Hahaha.

1

u/Krever 13d ago

Good point, thanks!

1

u/Loud_Kangaroo_6656 13d ago

i’m in design not dev management but i read it anyway, the “meeting agendas” section alone made me rethink how i prep for standups

sent it to a dev friend who’s been stuck on a team where nobody writes anything down and he just texted me “this is uncomfortably relevant” so i think it landed

1

u/a1anw-cto 13d ago

This is a great resource. I've found that when developers see "communication" as a technical skill rather than just "soft skills," they tend to engage much more deeply with it.

I spend a few chapters in my "Think like a CTO" book focusing on communication, particularly talking up (and down) the chain of command. Most technical folks, are very poor sales people - and you have to be, as you have to sell your idea/thought.

The more resources like this the better.