Abhi Hiremagalur | Blog

Asana gives everyone a sabbatical at four years.

## I.

There's a particular sadness to a missed connection between a question and its answer.

Amongst [Asana's values](https://asana.com/resources/company-values-examples), "Reject False Trade-offs" was the one I struggled with most when I first started in early 2022.

> TL;DR: Like racing teams making strategic pit stops, software teams must master the art of planned technical investments.

There’s a moment in the water, right after my first few strokes, when everything clicks.

Understanding the needs of another person is immensely helpful in tuning our behavior to them, and in predicting or even influencing their behavior around us.

When designing organizations much effort can be put into defining individual roles.

When I arrived at Coach Stuart McDougal's [swim workshop](https://www.mindbodyandswim.com/workshops.html) yesterday, all thoughts about my family, parents and work ceased.

This week a few colleagues and I, software engineers and managers at [VMware Tanzu](https://tanzu.vmware.com/), attended the third installment of [LeadDev Together](https://leaddev.com/course/together).

What follows is a note to some of my colleagues in early 2014, as we transitioned from writing mainly Ruby to writing Go.

# Move 1: Describe interactions with roles [Go's](http://golang.org/) interfaces are [satisfied implicitly](http://nathany.com/good/#toc_8), making it incredibly easy to create [role interfaces](http://martinfowler.com/bliki/RoleInterface.html).