Browser not supported. Please use Google Chrome or Microsoft Edge to access Ringle.
ringle-logo
Business
Talking to Developers
A few guidelines
Updated: 2022.06.22
4 min read · Intermediate
material_image

Software developers are artists in the modern world; it is without argument that the roles that they play in any given company are critical. The language of computing work is often described as objective, straightforward and without subtlety, but the work is without doubt one that is as much art as [1] it is science. When it comes to communicating with non-technical team members and colleagues, however, the sorts of difficulties that someone might run into might be as challenging as the work itself.

Let’s look at communications between developers and user experience team members as an example. User experience teams are responsible and interested in ensuring that the user experience is optimized, and these teams often work in conjunction with marketing to explore and experiment on new and different projects. They might then request the developers to help implement these projects, say, by changing the position of a graphic or repositioning a button on a website. While this is easy in theory, in practice that isn’t always the case. In these moments, developers may have to rely on the use of metaphors to capture and explain the difficulties encountered when handling old or a quickly-designed code base, one that was written without the future in mind [2]. It is also the unique responsibility of the devs to communicate that a quick fix today has the potential to cause problems tomorrow.

Cross-team communications (communications with different teams) require the balancing of different interests; this is especially notable when it comes to communications between developers and non-developers. While the goals and general interests of marketing are to increase profits for the company (in most cases, by making changes and introducing new changes), developers have the responsibility of ensuring stability [3] within a given software system. Every single small, tiny, or seemingly insignificant change has the potential to ripple outwards, introducing instability throughout a system; these ripples may be predictable or unpredictable.

All said, in the course of communicating with software developers in your environment, it might be helpful to keep a few guiding principles in mind:

  • Do not make assumptions about what is easy and what is not; the outward appearance of a software doesn’t say anything about how the code looks underneath the surface.
  • As with all things, remember that balance is key: the balance between performance and profit, the balance between stability and instability in a given system, and most importantly, the balance between work and life.
  • Be flexible: as previously noted, ripples (impacts of changes in code) throughout a software system are not always foreseeable, and when working with older or rushed code bases (often the case in startups) they are even more likely.

At the end of the day, the most important component of communication is empathy; feel out what you can, and for what you cannot understand, listen with an open ear, open heart, and open mind.

*This material is designed for the exclusive use of Ringle students on the Ringle platform.