iamnader · November 5, 2015 21:53 · Nov 5, 2015 · Jul 21, 2015 · Jul 21, 2015 · May 18, 2015
diff --git a/gistfile1.md b/gistfile1.md
@@ -3,7 +3,7 @@ originally put together by @alexmcpherson
 **Practical / Tactical**
 
 
-Be on time to meetings or alert an hour ahead of time if you'll be late
+Be on time to meetings
 
 Meetings need a goal and a runner to get that goal accomplished
 
@@ -43,7 +43,7 @@ Watch your **air time** during conversations and meetings. Engineers in particul
 
 Don’t be a jerk. Don’t assume you’re not a jerk. You might be.
 
-Help your coworkers get better! For more serious matters HR can be involved.
+Help your coworkers get better! 
 
 --------
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -1,3 +1,5 @@
+originally put together by @alexmcpherson
+
 **Practical / Tactical**
 
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -5,6 +5,8 @@ Be on time to meetings or alert an hour ahead of time if you'll be late
 
 Meetings need a goal and a runner to get that goal accomplished
 
+Defend your time from distractions and use it effectively on moving product forward
+
 Prefer **Slack** over **email** over **in person interruptions** over a **set block of time**
 
 Plan and communicate WFH/remote working days at least the day before when possible

diff --git a/gistfile1.md b/gistfile1.md
@@ -1,9 +1,9 @@
 **Practical / Tactical**
 
 
-On time to meetings or alert an hour ahead of time
+Be on time to meetings or alert an hour ahead of time if you'll be late
 
-Meetings need a goal and a runner to get that goal accomplished
+Meetings need a goal and a runner to get that goal accomplished
 
 Prefer **Slack** over **email** over **in person interruptions** over a **set block of time**
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -52,7 +52,7 @@ QA is your responsibility
 
 Be the CEO of the feature. Proactive running back.
 
-Write code to account for **happy**, **sad**, **evil**, and **weird **cases
+Write code to account for **happy**, **sad**, **evil**, and **weird** cases
 
 -------
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -5,7 +5,7 @@ On time to meetings or alert an hour ahead of time
 
 Meetings need a goal and a runner to get that goal accomplished
 
-Prefer **slack** over **email** over **in person interruptions** over a **set block of time**
+Prefer **Slack** over **email** over **in person interruptions** over a **set block of time**
 
 Plan and communicate WFH/remote working days at least the day before when possible
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -5,7 +5,7 @@ On time to meetings or alert an hour ahead of time
 
 Meetings need a goal and a runner to get that goal accomplished
 
-Prefer **slack** over **email **over **in person interruptions** over a **set block of time**
+Prefer **slack** over **email** over **in person interruptions** over a **set block of time**
 
 Plan and communicate WFH/remote working days at least the day before when possible
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -1,5 +1,6 @@
 **Practical / Tactical**
 
+
 On time to meetings or alert an hour ahead of time
 
 Meetings need a goal and a runner to get that goal accomplished
@@ -8,8 +9,11 @@ Prefer **slack** over **email **over **in person interruptions** over a **set b
 
 Plan and communicate WFH/remote working days at least the day before when possible
 
+------
+
 **Working with each other**
 
+
 10 minute rule: don’t get stuck on anything for that long, someone else can help you solve it faster
 
 [Ask questions well](http://stackoverflow.com/help/how-to-ask)
@@ -24,8 +28,11 @@ Be assertive AND flexible. Strong opinions, weakly held
 
 Pairing is healthy for our minds and products and we should try to do it for an hour a day
 
+-------
+
 **Being a good person**
 
+
 Learn about [well-actuallys](http://tirania.org/blog/archive/2011/Feb-17.html), [drive bys](https://www.recurse.com/manual#no-backseat-driving), and [feigning surprise](https://www.recurse.com/manual#no-feigned-surprise). And don’t do them.
 
 Watch your **air time** during conversations and meetings. Engineers in particular can be quiet or slower to speak
@@ -34,8 +41,11 @@ Don’t be a jerk. Don’t assume you’re not a jerk. You might be.
 
 Help your coworkers get better! For more serious matters HR can be involved.
 
+--------
+
 **Code Quality**
 
+
 Take responsibility for outcome of projects
 
 QA is your responsibility
@@ -44,8 +54,11 @@ Be the CEO of the feature. Proactive running back.
 
 Write code to account for **happy**, **sad**, **evil**, and **weird **cases
 
+-------
+
 **Career**
 
+
 Be able to set goals for your career
 
 Meta-cognition about your learning style, working style, communication challenges, strengths and weaknesses
@@ -54,6 +67,9 @@ Constant learning and industry awareness, even outside the scope of our product
 
 Seek to understand the entire product you are working on, not just the scope of your features.
 
+-------
+
+
 **Signals of a poor team fit**
 
 Ignoring or shifting problems that are hard

diff --git a/gistfile1.md b/gistfile1.md
@@ -1,54 +1,73 @@
 **Practical / Tactical**
 
 On time to meetings or alert an hour ahead of time
+
 Meetings need a goal and a runner to get that goal accomplished
-Prefer **Slack** over **email **over **in person interruptions** over a **set block of time**
-Plan and communicate WFH/remote working days at least the day before when possible
 
+Prefer **slack** over **email **over **in person interruptions** over a **set block of time**
+
+Plan and communicate WFH/remote working days at least the day before when possible
 
 **Working with each other**
 
 10 minute rule: don’t get stuck on anything for that long, someone else can help you solve it faster
+
 [Ask questions well](http://stackoverflow.com/help/how-to-ask)
+
 Seek out criticism on your designs and code
-- What could I be missing?
-- Where will this _not_ work?
+
+     What could I be missing?
+
+     Where will this _not_ work?
 
 Be assertive AND flexible. Strong opinions, weakly held
-Pairing is healthy for our minds and products and we should try to do it for an hour a day
 
+Pairing is healthy for our minds and products and we should try to do it for an hour a day
 
 **Being a good person**
 
 Learn about [well-actuallys](http://tirania.org/blog/archive/2011/Feb-17.html), [drive bys](https://www.recurse.com/manual#no-backseat-driving), and [feigning surprise](https://www.recurse.com/manual#no-feigned-surprise). And don’t do them.
+
 Watch your **air time** during conversations and meetings. Engineers in particular can be quiet or slower to speak
-Don’t be a jerk. Don’t assume you’re not a jerk. You might be.
-Help your coworkers get better! For more serious matters HR can be involved.
 
+Don’t be a jerk. Don’t assume you’re not a jerk. You might be.
+
+Help your coworkers get better! For more serious matters HR can be involved.
 
 **Code Quality**
 
 Take responsibility for outcome of projects
+
 QA is your responsibility
+
 Be the CEO of the feature. Proactive running back.
-Write code to account for **happy**, **sad**, **evil**, and **weird **cases
 
+Write code to account for **happy**, **sad**, **evil**, and **weird **cases
 
 **Career**
 
 Be able to set goals for your career
+
 Meta-cognition about your learning style, working style, communication challenges, strengths and weaknesses
+
 Constant learning and industry awareness, even outside the scope of our product’s technology choices
-Seek to understand the entire product you are working on, not just the scope of your features.
 
+Seek to understand the entire product you are working on, not just the scope of your features.
 
 **Signals of a poor team fit**
 
 Ignoring or shifting problems that are hard
+
 Blaming users or PMs or QA for bugs
+
 Focus on the letter of the tasks assigned, not the spirit
+
 Taking code review personally
+
 Sowing discontent, gossiping
+
 Thinking you’re the smartest person in the room
+
 Being a jerk
+
 Being unwilling to learn, grow, and explore
diff --git a/gistfile1.md b/gistfile1.md
@@ -1,11 +1,13 @@
 **Practical / Tactical**
+
 On time to meetings or alert an hour ahead of time
 Meetings need a goal and a runner to get that goal accomplished
 Prefer **Slack** over **email **over **in person interruptions** over a **set block of time**
 Plan and communicate WFH/remote working days at least the day before when possible
 
 
 **Working with each other**
+
 10 minute rule: don’t get stuck on anything for that long, someone else can help you solve it faster
 [Ask questions well](http://stackoverflow.com/help/how-to-ask)
 Seek out criticism on your designs and code
@@ -17,26 +19,31 @@ Pairing is healthy for our minds and products and we should try to do it for an
 
 
 **Being a good person**
+
 Learn about [well-actuallys](http://tirania.org/blog/archive/2011/Feb-17.html), [drive bys](https://www.recurse.com/manual#no-backseat-driving), and [feigning surprise](https://www.recurse.com/manual#no-feigned-surprise). And don’t do them.
 Watch your **air time** during conversations and meetings. Engineers in particular can be quiet or slower to speak
 Don’t be a jerk. Don’t assume you’re not a jerk. You might be.
 Help your coworkers get better! For more serious matters HR can be involved.
 
+
 **Code Quality**
+
 Take responsibility for outcome of projects
 QA is your responsibility
 Be the CEO of the feature. Proactive running back.
 Write code to account for **happy**, **sad**, **evil**, and **weird **cases
 
 
 **Career**
+
 Be able to set goals for your career
 Meta-cognition about your learning style, working style, communication challenges, strengths and weaknesses
 Constant learning and industry awareness, even outside the scope of our product’s technology choices
 Seek to understand the entire product you are working on, not just the scope of your features.
 
 
 **Signals of a poor team fit**
+
 Ignoring or shifting problems that are hard
 Blaming users or PMs or QA for bugs
 Focus on the letter of the tasks assigned, not the spirit

diff --git a/gistfile1.md b/gistfile1.md
@@ -0,0 +1,47 @@
+**Practical / Tactical**
+On time to meetings or alert an hour ahead of time
+Meetings need a goal and a runner to get that goal accomplished
+Prefer **Slack** over **email **over **in person interruptions** over a **set block of time**
+Plan and communicate WFH/remote working days at least the day before when possible
+
+
+**Working with each other**
+10 minute rule: don’t get stuck on anything for that long, someone else can help you solve it faster
+[Ask questions well](http://stackoverflow.com/help/how-to-ask)
+Seek out criticism on your designs and code
+- What could I be missing?
+- Where will this _not_ work?
+
+Be assertive AND flexible. Strong opinions, weakly held
+Pairing is healthy for our minds and products and we should try to do it for an hour a day
+
+
+**Being a good person**
+Learn about [well-actuallys](http://tirania.org/blog/archive/2011/Feb-17.html), [drive bys](https://www.recurse.com/manual#no-backseat-driving), and [feigning surprise](https://www.recurse.com/manual#no-feigned-surprise). And don’t do them.
+Watch your **air time** during conversations and meetings. Engineers in particular can be quiet or slower to speak
+Don’t be a jerk. Don’t assume you’re not a jerk. You might be.
+Help your coworkers get better! For more serious matters HR can be involved.
+
+**Code Quality**
+Take responsibility for outcome of projects
+QA is your responsibility
+Be the CEO of the feature. Proactive running back.
+Write code to account for **happy**, **sad**, **evil**, and **weird **cases
+
+
+**Career**
+Be able to set goals for your career
+Meta-cognition about your learning style, working style, communication challenges, strengths and weaknesses
+Constant learning and industry awareness, even outside the scope of our product’s technology choices
+Seek to understand the entire product you are working on, not just the scope of your features.
+
+
+**Signals of a poor team fit**
+Ignoring or shifting problems that are hard
+Blaming users or PMs or QA for bugs
+Focus on the letter of the tasks assigned, not the spirit
+Taking code review personally
+Sowing discontent, gossiping
+Thinking you’re the smartest person in the room
+Being a jerk
+Being unwilling to learn, grow, and explore
Original file line number	Diff line number	Diff line change
		@@ -1,3 +1,5 @@
		originally put together by @alexmcpherson

		Practical / Tactical