Removing notes

diff --git a/chapter04.md b/chapter04.md
index 6e81e577c7356a0989dbd1159be0c5d081b084f0..0b3548ab1de4f528ac6e7b9ed75bff7a5d91f33d 100644 (file)
--- a/chapter04.md
+++ b/chapter04.md
@@ -1,8 +1,6 @@
 # The inns we stayed at
 
-Discuss the different communities and how there's something to be learned from programming in languages that aren't considered good languages. Discuss how there's no such thing as a truly bad language.
-
-## Fellow travellers
+## Fellow travelers
 
 Whenever we think of programmers we think of a person working in solitude entering code into a computer. Usually that programmer is alone, although there are methodologies that utilize more than one programmer at a time ("pair-programming" for instance). During those coding sessions there isn't' a lot of contact with other programmers and it can feel isolating to be in the company of yourself for most of the day. Granted this may be a good feeling (there are times when I really enjoy being by myself at the computer) but there are other times when we need to feel like we're not alone in this. This is especially true when we're learning and pushing ourselves into uncomfortable territory. Finding others who are in a similar situation can help us with our learning process by fielding questions and reviewing our progress. Finding a good community that is supportive of our learning is vital to our programming journey. When we have a good community we have somewhere that we can learn and help others learn. We can grow in the community  and find friendship.
 

diff --git a/chapter05.md b/chapter05.md
index 36674dbe78282cf8a6185fb3452fc0ab0cc6bed7..6855e248e516eaa229ce701c0a5bb4b889e1ed59 100644 (file)
--- a/chapter05.md
+++ b/chapter05.md
@@ -1,7 +1,5 @@
 # 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.
-
 ## Riding until dawn
 
 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.

diff --git a/chapter06.md b/chapter06.md
index 23d25992c81398146409c440fb4de22be5f5a20d..1bf2b8068c1c49d59dc8f2d8a32cc24b19035a59 100644 (file)
--- a/chapter06.md
+++ b/chapter06.md
@@ -1,6 +1,5 @@
 # The map is not the territory
 
-Discuss the ever-changing facets of programming and how keeping current with it all is both a challenge and a myth
 ## The changing landscape of programming
 
 The one constant about the field of programming is that it is always in flux. Programming languages come into prominence and the fade away over time. What once was a given is now considered obsolete (or even "harmful", as many essays will point out).