/Career Advice

How To Work Hard

- Paul Graham tl;dr: "Working hard is a complicated, dynamic system that has to be tuned just right at each point. You have to understand the shape of real work, see clearly what kind you're best suited for, aim as close to the true core of it as you can, accurately judge at each moment both what you're capable of and how you're doing, and put in as many hours each day as you can without harming the quality of the result."

featured in #238


Should You Estimate Bugs?

tl;dr: There are a few methods of bug estimation, e.g.: (1) Dedicated time per sprint (2) Default estimation, e.g. 1 day/bug (3) Estimation with historical data (4) No estimation. Author argues that company size should affect which approach to go for.

featured in #238


How To Review Code As A Junior Developer

- Emma Catlin tl;dr: (1) "If something is not clear to you, it probably isn’t clear to everyone," so ask questions. (2) Calibrate feedback - "work to cater recommendations to the individual." (3) Emulate others "by observing how your coworkers review code, you can learn what to pay attention to when you’re writing code.

featured in #238


What I learned From Software Engineering At Google

- Swizec Teller tl;dr: This post discusses: (1) The difference between engineering and programming. (2) Hyrum's Law - "all observable behaviors of your system will be depended on by somebody" so write tests on the code you like. (3) The earlier you find a mistake, the easier it is to fix, and more.

featured in #238


The 10 Most Valuable Lessons I Learned As A Developer

- Oliver Jumpertz tl;dr: With over 21 years of experience, Oliver cites the following: (1) You will never know everything. (2) A good team doesn't scale your capabilities linearly but exponentially. (3) Code should be written for humans. (4) Patience is your best friend, and more.

featured in #237


Write Good Examples By Starting With Real Code

- Julia Evans tl;dr: Start with real code that you wrote and then "remove irrelevant details to make it into a self-contained example, instead of coming up with examples out of thin air." Julia runs through two types of examples - (1) realistic examples that sell the concept and (2) surprising examples that change someone's mental model.

featured in #236


Amazon's Bezos Says Three Good Decisions a Day 'Enough' (Video)

tl;dr: As a senior exec you get to make a few decisions a day so getting 8 hours of sleep and organizing "high IQ" meetings earlier both help to make good a few decisions.

featured in #236


Attitude and Behavior

- Ed Batista tl;dr: We assume attitude drives behavior but, in fact, our behavior also shifts our attitude. A misalignment of behavior and attitude i.e. you should do something but don't feel like it results in cognitive dissonance. Ed outlines strategies to counter this (meditation, journaling, etc...) but states they should come from a sense of authenticity and agency.

featured in #235


Clever Vs Insightful Code

- Hillel Wayne tl;dr: Hillel draws a distinction between clever code, which "conventional wisdom says is bad," and insightful code which finds a way of exploiting a problem to make code "faster, simpler, and safer," and is often necessary to make things work. Hillel highlights these with examples.

featured in #233


Questionable Advice: “What Should I Say In My Exit Interview?”

- Charity Majors tl;dr: Charity is asked how to handle this by someone reputable leaving due to a toxic management culture. The issue with being candid isn't retribution, it's apathy. The key is to try and be effective. Put it in writing, keep it short and go through the incidents and issues, and tie them to material consequence (people quitting, etc...).

featured in #233