Western Wilsonhttps://westernwilson.com/tags/communication/Recent content in Communication on Western WilsonHugoenWed, 18 Mar 2026 00:00:00 +0000Developer dynamicshttps://westernwilson.com/reflections/2023-10-28-developer-dynamics/Sat, 28 Oct 2023 00:00:00 +0000https://westernwilson.com/reflections/2023-10-28-developer-dynamics/Full disclosure, I first heard of these architypes from a workshop run in 2020 by FLINT Wellington Types of Developers in the Workplace In a dynamic and collaborative workplace, you’ll encounter various types of developers, each driven by different motivations and approaches to their work. Understanding these developer archetypes can help foster a more effective and harmonious team environment. Full disclosure, I first heard of these architypes from a workshop run in 2020 by FLINT Wellington

Types of Developers in the Workplace

In a dynamic and collaborative workplace, you’ll encounter various types of developers, each driven by different motivations and approaches to their work. Understanding these developer archetypes can help foster a more effective and harmonious team environment.

1. The Detective

Drive: Detectives love to investigate. They thrive in messy situations, dissecting problems, and fixing them. Their analytical minds excel at uncovering the root causes of issues and implementing solutions. They’re the team’s problem-finders, and a lot of the time, problem-solvers.

2. The Cowboy / Go-getter

Drive: Cowboys or Go-getters are known for their speed. They push code out the door quickly, often impressively so. However, they might leave a bit of a “dirty sink” behind, sacrificing some cleanliness for speed. They’re the team’s high-velocity coders.

3. The Artist or Creative

Drive: Artists or Creatives focus on the aesthetics of code. They’re meticulous about making sure their code is not just functional but also visually appealing and highly readable. While they may code more slowly, their work introduces less technical debt. They’re the team’s code beautifiers.

4. The Mad Scientist

Drive: Mad Scientists are tech enthusiasts. They eagerly embrace the latest technologies and enjoy experimenting with new libraries and features. Their adventurous spirit leads to innovation and pushing the boundaries of what’s possible. They’re the team’s tech trailblazers.

In a balanced development team, these diverse types of developers can complement each other, fostering creativity, efficiency, and problem-solving. Recognizing and valuing these different approaches can lead to a more well-rounded and successful team.

]]>Talking Tech, to Non-Techhttps://westernwilson.com/reflections/2020-08-17-tech-to-non-tech/Mon, 17 Aug 2020 00:00:00 +0000https://westernwilson.com/reflections/2020-08-17-tech-to-non-tech/Early in my career, I attended a workshop where the goal was to bridge the gap between technical and non-technical people when discussing technical concepts. The session emphasized the use of analogies to explain concepts and catering to different learning styles, such as visual aids. Simplifying Technical Jargon To communicate tech concepts to non-technical individuals, analogies are invaluable. Early in my career, I attended a workshop where the goal was to bridge the gap between technical and non-technical people when discussing technical concepts. The session emphasized the use of analogies to explain concepts and catering to different learning styles, such as visual aids.

Simplifying Technical Jargon

To communicate tech concepts to non-technical individuals, analogies are invaluable.

The Barrier of Technical Jargon

In the tech world, complex terminology and buzzwords are commonplace. While they serve a purpose among peers, they can hinder communication with non-technical individuals.

Harnessing the Power of Analogies

Analogies act as bridges, simplifying intricate tech concepts for the non-technical. They make the unfamiliar more accessible, fostering better understanding and collaboration.

Striking the Balance

Balancing the use of technical jargon and analogies is key. Precision is vital in technical discussions, but in broader contexts, simplification enhances communication, collaboration, and innovation.

Types of Applications

Applications can be web-based (run in browsers), desktop (run on a computer), or mobile (run on phones). Examples like Netflix, Spotify, and Instagram show the diversity of platforms.

In simplified terms, an application’s Stack includes a Client (the end-user with a Laptop or Mobile device), a Server (handles requests, processes data, and communicates with the Database), and a Database (stores information). Think of this stack like a person withdrawing money from a bank:

  1. Front-end -> Person/Client
  2. Server -> Bank Teller
  3. Database -> Money Stash

Understanding APIs

APIs (Application Programming Interfaces) are communication tools for technology. Think of ordering fast food: the client orders, the server takes the order, and the chefs in the kitchen fulfill it. An API is like the menu, specific to the restaurant you’re at.

If you go to Burger King and order a Big Mac, the server will not understand that request as it is not on their Menu.

Team Dynamics

Different types of team members, including detectives, cowboys, artists, and mad scientists, each have distinct work styles and motivations. Recognizing these differences can improve team collaboration.

Click here to read the full article on these archetypes here.

The Coding Process

Developers need uninterrupted time to code effectively. Minimize interruptions by scheduling meetings in blocks, improving productivity.

Future Technology

Full-stack development offers efficiency by using one language across all stack components. Libraries like React can translate web apps into desktop and mobile versions. Distributed technology, like blockchain, shares data across a network, reducing the risk of single points of failure and enhancing security.

]]>