DEV Community

Discussion on: What are the big differences between working for a "tech company" and being a dev for a "non-tech company"

ben profile image
Ben Halpern Author

Any communication strategies for situations like this?

arschles profile image
Aaron Schlesinger

I like to start by boiling it down as much as possible.

Managers all want to know when it's gonna be done & how much it will cost (even the highly technical ones!), so I like to start with those two messages in mind, and then expand as necessary from there. I usually don't expand at all from there, to be honest. It's nicer and easier for both parties to let them ask the questions after you present the facts.

srleyva profile image
Stephen Leyva (He/Him) • Edited

Principle: Consider the audience.

Pragmatic programmer talks about this but essentially tell them how new developments affect bottom line, availability, security of service in ways they understand and care about. The board doesn’t care if if you’re running Kubernetes, Docker, microservices, monelith, Linux, Windows, etc. All that matters (or really should) is it works, is cost effective and allows you to viably get to market. In a non-tech company, your tech leadership should be able to communicate that back to management in a clear way. Though, the DevOps handbook hypothesis’s that every company will be a tech company in one way or another and business side will need to understand the technology side as they are too tightly coupled.