How To Work With Developers - A Guide for Non-Developers

Kate Travers on April 27, 2018

Software developers, have you ever felt misunderstood by your non-developer teammates? It happens to most of us, which is why I wrote this post t... [Read Full]
markdown guide

This was an awesome read, and I plan to re-read it a few more times for clarity.

Engineers are just as social as your average co-worker. We’re just very protective of our precious (and limited) attention span.

This is super well articulated. Definitely going to share.


Yes, we value focussed attention time but there's also a myth that programmers somehow ned more focussed attention than other knowledge workers. We propagate this myth because it makes us feel special. But most of that need for focus is caused by not breaking the problem into small enough chunks, so we have to keep a bunch of stuff in our head. If you're always in the middle of something massive, any interruption is incredibly irritating. If you break your work into small enough chunks, you have many natural breaking points where you can make time for interacting with coworkers.

This talk goes into that problem, ad it's my favorite programming-related talk right now.


Though this article has a lot of useful information I can't agree with the general tone of developers being different. It paints a broad stereotype of what ultimately is an individual.

A lot of the issues I've seen in companies are directly due to how teams handle each other as foreign entities. Identifying as a class of person inevitably leads to a break down of job roles and puts up walls between the teams.

If you treat a programmer, just like anybody else in a company, with respect, you should be fine. Understand that programmers, just like all people in the company, have interests, have good/bad days at work, have issues with management, and don't like the new coffee machine. The amount of similarity between workers is far more significant than the differences.


Awesome ! I had so much fun reading it, I wonder if some people actually need it ..


Loved almost all of this and will be sharing it to my team (we've had some of the communication issues mentioned here!)

One tiny thing is: some of this is culture specific. If you told our team that the product owner (who is also an engineer by trade went down the PO path) was going to assign work, there would be a small revolt (PO included)! We've found the best way to increase engagement is to let engineers assign themselves work based on their interests and the PO simply watches out to make sure no one gets in over their heads. Works for our team, but ymmv. Working this way with my last two teams has built a strong dislike for anyone who wants to hand out assignments haha! :D


Great article with lots of good advice. I also think this is something that will help dev teams. We run a 1 day workshop on working with developers for companies who employ Devs and want to understand them better.


Amazing, the same problems everywhere :) I bookmarked this page so i can show it to some colleagues later.
Here are a few more tips:


Easily one of the best articles I read this year. 👏👋👌✌


This is an amazing read, but being just out of college and creating simple web apps to apply for jobs, I got confused at some points to many degree :D


Oh god, it's was a increíble/amazing/great read.

You has a great research, thanks very thanks for sharing.

I've truly needed i usually talk of my 'cool algorithms' Haha. Oh thanks.

It is was a read very gratifying.


I've truly needed i usually talk of my 'cool algorithms' Haha. Oh thanks.

You and me both 😉😊


Folks, the next time the alarm goes off, leave you effing laptops there. That picture and paragraph drove me mad.


This is just.... incredibly accurate. I think everyone could learn a few things by reading this.


Still in the office at 5:30? then still working?

Sounds like hell to me.

code of conduct - report abuse