From f5261bf5bfd684259d0f87de5aca539b93511d22 Mon Sep 17 00:00:00 2001 From: Craig Maloney Date: Fri, 29 Jun 2018 09:00:33 -0400 Subject: [PATCH] Starting the chapter on productivity --- chapter05.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/chapter05.md b/chapter05.md index 5452292..dc605c0 100644 --- a/chapter05.md +++ b/chapter05.md @@ -1,3 +1,9 @@ # A day's journey Discuss productivity for developers and how programming can be exhausting. Discuss the myth of always being on as a developer and the need for downtime and rest. + +## Productivity + +Programmers are always trying to find new ways to be productive. Different editors, scripts, compilation tweaks, automation; the list goes on and on for how programmers want to maximize their time coding. We also tend to add that to the rest of our lives, thinking that we should always be on, coding. Any moment not coding is a moment that our projects get behind. And that can lead to other problems: missed deadlines, others getting to market before us, collisions with others work because they made a breaking change before we could smooth it out. We're constantly worrying that we're not doing enough. We've heard the stories: developers waking up at their computers to the strange sound of beeping because the keyboard auto repeat can't handle anymore input with their face resting on the keys. + +I think there's this tendency that because we work with machines that are tireless and ready for more work that we need to be the same way; we need to constantly utilize these resources. We become like the machine, and the better we get the better we'd better get (because our boss or colleagues will notice that we've completed something and more work will come our way). -- 2.31.1