Extras · 1 of 4

A typical day

A short stand-up call in the morning where everyone says what they are working on. Then long blocks of writing and reading code, broken up by reviewing someone else's changes and being asked questions in chat. Something breaks in the afternoon and you spend two hours finding out it was a stray character in a configuration file. You ship, you write the notes, you close the ticket. Most of this happens from home.