“If anyone is remote, you’re all remote.” At Atomic Object, we value co-located teams. But not every team member can always be co-located. Larger project teams may have members from multiple offices. Some projects might involve working closely with other vendors. I experience this “remoteness” when I support the infrastructure needs of teams in our […]
This is part two of a two-part series on tools and practices for maintaining a healthy and effective remote team. In part one, I discussed infrastructure and tools for remote teams. In this second part, I’ll be focusing on day-to-day practices and attitudes. As with part one, this advice is not only for remote teams […]
In this two-part series, I’ll be writing about the day-to-day realities of working as part of a remote team, and some tools and practices you can use to help keep your team healthy and effective. Even if you’re not involved in a remote team, you’ll find much of this advice to be beneficial for co-located […]
Atomic works in close partnership with our clients, adopting their goals and becoming part of their internal team. This requires regular communication with the client’s product manager during every stage of the project — something we’ve very intentional about, especially when the client is too far from our office to have weekly in-person meetings. To […]
Since starting at Atomic, I’ve had to use remote pairing on several occasions to work with developers who were not co-located with me. I wanted to give an overview of some of the different tools I’ve used for remote pairing and what I like/don’t like about them. Skype Skype is hardly a sophisticated remote pairing […]
I have been looking at ways to simplify remote pairing. I was happy to find out about a new project called wemux. wemux is a script that simplifies the management of shared tmux sessions.