Lessons
35 articles
- What being an expert looks like
- Hard work doesn’t scale
- Move the rock
- Why write
- Avoid spooky action at a distance
- When to throw away your code
- A backend service nobody can grok
- Own the outcome, not the work
- DRY vs SoC, a difficult choice
- Coding is the easy part
- Clever technical hackery can't solve the wrong design
- My biggest React App performance boost was a backend change
- Why PATCH endpoints matter
- How better data modeling fixes your code
- A work ritual that keeps me sane
- Write abstractions, not just code
- Coding forces you to understand the problem
- A lesson on expertise from a great mafia movie
- Writing software is like kicking a can
- The Italian foods theory of bad software design 🍝
- Learnings about the future of the web from Reactathon
- The role of a senior+ engineer
- Saving time in UTC doesn't work and offsets aren't enough
- A quick lesson in writing resilient code
- Immutability isn't free
- How I used indie hacking to sponsor my own greencard
- What to do when bugs are whack-a-mole
- The Passion Paradox
- When it’s okay to work overtime
- Why null checks are bad
- How defensive coding leads to bloat
- Your luck & opportunity surface area
- Different medium, different mindset
- Variants – a quick tip for better React components
- Lessons from migrating a 14 year old blog with 1500 posts to Gatsby