featured in #525
I've Been Thinking About Tradeoffs All Wrong
- Hillel Wayne tl;dr: “Normally I think of tradeoffs as framing two positive things, like saying "SQS has better control while SNS is easier to add new services". Instead the speaker framed it as two wholly negative things, and the tradeoff is which negative thing you want less of. We can do this with any tradeoff, because any positive quality about X can be turned into a negative quality of Y. Instead of "X is faster, Y uses less space", we can say "X uses more space, Y is slower.””featured in #524
How To Build Anything Extremely Quickly
tl;dr: (1) Make an outline of the project. (2) For each item in the outline, make an outline. Do this recursively until the items are small. (3) Fill in each item as fast as possible. Do not perfect as you go. This is a huge and common mistake. (4) Finally, once completely done, go back and perfect.featured in #523
How To Build Anything Extremely Quickly
tl;dr: (1) Make an outline of the project. (2) For each item in the outline, make an outline. Do this recursively until the items are small. (3) Fill in each item as fast as possible. Do not perfect as you go. This is a huge and common mistake. (4) Finally, once completely done, go back and perfect.featured in #522
How I Give The Right Amount Of Context (In Any Situation)
- Wes Kao tl;dr: “Giving the right amount of context helps teams move faster. Too much context? Your manager can’t tell what’s important. They’ll need to wade through details, trying to sort information into a pile of what’s important vs what to ignore. Too little context? Your manager has to follow up and pull information out of you that you should have mentioned proactively. There is such a thing as being too concise.”featured in #521
featured in #519
Using A Dev Diary Seems To Be Worthwhile
- Mike Hogan tl;dr: “An experiment for devs to try. I started keeping a "dev diary". It was prompted by a statement by Stuart Ervine when I asked how others keep broader context of decisions behind code that are not visible in code, tests or comments. He said that at Apple, developers on teams keep diaries, and each team member can browser what others are thinking.” Mike shares his diary.featured in #519
How Does AI Impact My Job As A Programmer?
- Chelsea Troy tl;dr: “It’s how human programmers, increasingly, add value. Figure out why the code we already have isn’t doing the thing, or is doing the weird thing, and how to bring the code more into line with the things we want it to do. Chelsea argues that this “conveniently comprises most of the job these days: read code. Analyze it. Understand it. Repair it.”featured in #519
Three Laws Of Software Complexity
- Mahesh Balakrishnan tl;dr: Mahesh discusses the implication of each: (1) A well-designed system will degrade into a badly designed system over time. (2) Complexity is a moat filled by leaky abstractions. (3) There is no fundamental upper limit on software complexity.featured in #519
Three Laws Of Software Complexity
- Mahesh Balakrishnan tl;dr: Mahesh discusses the implication of each: (1) A well-designed system will degrade into a badly designed system over time. (2) Complexity is a moat filled by leaky abstractions. (3) There is no fundamental upper limit on software complexity.featured in #518