Learnings

<p>Fix tomorrow’s problems by fixing today’s problems: </p>

<p>Debugging Tips And Techniques: </p>

<p><em>Sent by Jota</em>&gt; Professional Programming: The First 10 Years </p>

<p>Notes on debugging: </p>

<p>Which Kinds of Tests Should I Write? </p>

<p>HN discussion on how to improve as a struggling junior swe </p>

<p>One Way Smart Developers Make Bad Strategic Decisions: </p>

<p>Precision In Technical Discussions: </p>

<p>Commoditized Trust: </p>

<p>Trojan Source: Invisible Vulnerabilities </p>

<p>"Don't take down a fence until you know why it was put up." </p>

<p><em>Reflections on 10,000 Hours of Programming:</em> </p>

<p>Glue: the Dark Matter of Software: </p>

<p>Python Design Patterns: </p>

<p>Those pesky pull request reviews: </p>

<p>"Sometimes, programming feels like magic: you chant some arcane incantation and a fleet of robots do your bidding. But sometimes, magic is mundane. If you’re willing to embrace the grind, you can pull off the impossible" </p>

<p>Write code. Not too much. Mostly functions: </p>

<p>Small Functions considered Harmful :eyes: </p>

<p>Why did a fix of two lines of code take two days to complete? </p>

<p>The epistemology of software quality: </p>

<p>The Product-Minded Software Engineer: </p>

<p>Why software projects take longer than you think – a statistical model: </p>