The Architecture of Agreement: Coding with a Mediator’s Mindset

21 Feb 2026

---

Is Code Just Syntax, or is it Communication?

In the world of software development, we often treat “clean code” as a purely technical requirement. We talk about DRY (Don’t Repeat Yourself) principles and performance optimization. However, coming from a background with a Graduate Certificate in Conflict Management and an MBA, I see code differently. To me, every line of code is a form of negotiation between the current developer and the person who will inherit that code six months from now.

Conflict often arises in technical teams not because of a lack of skill, but because of a lack of clarity. When code is “clever” instead of “clear,” it creates technical friction. As a trained mediator, I’ve learned that the best way to resolve a dispute is to prevent the misunderstanding from happening in the first place.

Applying Mediation to the Code Review

In my previous roles, such as serving as a mediator for personnel disputes at QDOBA, I had to utilize specialized communication techniques to find common ground. I apply these same techniques during code reviews and collaborative sprints. Instead of approaching a pull request as a critique, I approach it as a restorative process—ensuring the “architecture of agreement” is sound.

For example, when I developed my Quiz Game Web Application, I had to “negotiate” with the Firebase real-time database to ensure data was synchronized across multiple clients. The “conflict” here was latency. By utilizing a “single source of truth” logic, I mediated the data flow so that every player saw the same state at the same time.

Conclusion

Technical skills get you the job, but conflict management skills keep the project on track. By viewing web development through the lens of dispute resolution, I aim to build digital environments that are as harmonious as they are functional.