If you complain for being bothered in Slack or other real time communication tools outside of normal working hours, it’s your fault. When you have a remote, distributed team, you have two approaches before you talk to a colleague. You either have to check their timezone every single time before you ping them to see … Continue reading It’s your fault people bother you
At GitHub, we rely on Issues heavily. Not only for bug reports, or for tracking feature implementation. We use them for almost everything. This includes, but is not limited to, discussions, announcements, ideas, tracking projects, capturing thoughts or pieces of documentation that will become pull requests, and many more. The problem with having an abundance … Continue reading How I avoid zombie GitHub Issues
If you follow me, you know by now that me and my team (4 people in total) started working remotely. I was wondering what to write for Blog Action Day. I decided it would be cool if I could calculate some numbers that showed how we affect our environment in a positive way.
One of the tools I really appreciate because it helps me enhance my communication is Jing. Jing has a free edition that supports both screen captures with annotations and video captures with voice!
In my previous post, I mention that we started working remotely in order to improve our productivity. I chose “remote work” because I believe it solves some issues. Most of the times, however, when you try to solve a bunch of problems, you may create a bunch of new ones. In the end you may … Continue reading How to avoid alienation while working remotely
It all started 6 months ago. I was pressed by management to improve our team’s productivity. We are a team of 4 programmers with me as a leader. I identified some factors that in my opinion influenced our productivity and I reckoned working remotely could eliminate them. As a result we could increase our productivity.
Recently, I discovered something about myself. One way to actually do something worth throughout the course of a day, is break down my tasks into very small units of work. Then, start working on one unit of work at a time.
After reading Jeff Atwood’s post The Programmer’s Bill of Rights, where Jeff suggests programmers should have a fast PC, I checked out the comments. Of course I found a lot of people agreeing but some disagreed with that specific item. They suggested that a programmer should have a slow PC in order not to write … Continue reading Should programmers have a fast PC?
A large part of my current activities is organizing a software development department. I am beginning a series of posts where I am going to share how I have decided to tackle each aspect of the software development process. First let me tell you that I am greatly influenced by Joel Spolsky and his articles … Continue reading Organizing development: Introduction