investigating strange 404 loop bug

episodes/036.md

@@ -10,6 +10,8 @@ _Tudor Girba builds tools and techniques for improving the productivity and happ
 
 <iframe src="https://omny.fm/shows/future-of-coding/36-moldable-development-tudor-girba/embed?style=cover" width="100%" height="180" frameborder="0"></iframe>
 
+---
+
 Programmers spend roughly [50% of their time reading code](http://www.humane-assessment.com/guide/assessment-costs/). But, as Tudor Girba likes to ask, "When was the last time you talked about _how_ you read code?" Likely never. Isn't that curious? We talk endlessly about static vs dynamic typing, agile vs waterfall methodologies, and unit vs functional vs integrated testing, but don't spare any breath on the single activity we spend most of our time on.
 
 Clearly we aren't reading code for pleasure. Our goal is to read the minimum necessary to understand enough to make a decision. Software engineering is  primarily a decision-making business, "rather than a construction business, which  we optimized for, for the last 50 years."
@@ -20,7 +22,7 @@ Yet code is data as much as the data in a database is data. It's highly structur
 
 > We shape our tools and thereafter our tools shape us. 
 >
-> -John Culkin / Marshall McLuhan
+> John Culkin / Marshall McLuhan
 
 The irony is we don't make this mistake with the tools we build for others. We build web _browsers_, data _analyzers_, customer-relationship _managers_ (CRM), content _managers_ (CMS), media _players_, music _sequencers_, and game _simulators_. "The systems we build actively prevent end-users from ever seeing the raw data. And yet those end users make better decisions for it. So we in software know how to transform data problems into decision-making problems. That's a skill we can utilize for rethinking the way we do our business."