Make Things Simpler Than Possible
- Arthur O’Dwyer tl;dr: Donald Knuth presents a particular system in a specific way. “He first presents an oversimplified version of the system — so oversimplified that it is, in fact, incorrect — to give the student the general gist of the system. Seeing a consistent general plan up front, even though it errs in some particulars helps the student understand the final version.”featured in #540
featured in #539
What's Hidden Behind “Just Implementation Details"
- Nicole Tietz-Sokolskaya tl;dr: “Here is a quick survey of some of the hard-and-maybe-impossible parts of getting things into production that I've run into in my own work.” Nicole discusses: (1) Getting started. (2) Creating a maintainable design. (3) Making it robust, and observable. (4) User experience and user interface design. (5) Acceptable performance.featured in #539
featured in #539
How To Understand / Retain Complex Concepts 10x Better
tl;dr: (1) Pretend you’re having an imaginary conversation where you are explaining the concept to someone else. (2) While explaining the concept, focus on making it easier for them to understand. (3) Repeat this over and over, iteratively refining your explanation of the concept to give increasingly compressed and effective explanations. Over several repetitions, you will end up with a significantly simpler understanding of the concept than when you started.featured in #538
featured in #537
40 Life Lessons I Know at 40 (That I Wish I Knew At 20)
- Peter Yang tl;dr: (1) Find the torture that you’re comfortable with. (2) Look for the intersection i.e. the work that satisfies what you want, what you’re good at, and what the market wants. (3) Stop waiting for permission. (4) Maximize your luck surface area. (5) Don’t be the best, be the only.featured in #535
40 Life Lessons I Know at 40 (That I Wish I Knew At 20)
- Peter Yang tl;dr: (1) Find the torture that you’re comfortable with. (2) Look for the intersection i.e. the work that satisfies what you want, what you’re good at, and what the market wants. (3) Stop waiting for permission. (4) Maximize your luck surface area. (5) Don’t be the best, be the only.featured in #534
featured in #533
Lessons Learned In 35 Years Of Making Software
- Jim Grey tl;dr: (1) Do things in the most straightforward way possible. (2) There is no substitute for working software in Production. (3) Relationships matter if you want to advance. (4) Relationships matter if you want to see your vision come to life. (5) Never be invisible. And more.featured in #533