[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"issue-564":3},{"favorite":4,"culture":16,"peopleware":46,"inspirational":67},[5],{"listName":6,"listNumber":7,"listDate":8,"cardDate":9,"label":10,"title":11,"url":12,"domain":13,"summary":14,"timeToRead":15},"Issue 564 - 15th Sept. 2023",564,"15th Sept. 2023",1694717325,"favorite","Aging Code","https:\u002F\u002Fvadimkravcenko.com\u002Fshorts\u002Faging-code\u002F","vadimkravcenko.com","Vadim Kravcenko's framing of \"Aging Code\" and comparing it to Old Money > New Money (don't spend what you just earned) is powerful: \"Why should you consider aging your code? Because the longer your code has been around, survived different cataclysms (read: business pivots), and evolved, the more robust it is. The team that has built it before you had time to debug, to optimize, to improve — the code has accumulated years worth of bugfixes that are in places you cant even imagine.\" -- The last section on \"Asking the hard questions\" can provide a good baseline for your team to consider where and why you should refactor the code and what would be the benefit of it.",6,[17,25,33,40],{"listName":6,"listNumber":7,"listDate":8,"cardDate":18,"label":19,"title":20,"url":21,"domain":22,"summary":23,"timeToRead":24},1694717481,"funny!","Me When It’s Still Way Too Early but the Kids Start Screaming for Me to Get Up","https:\u002F\u002Ftwitter.com\u002FpackyM\u002Fstatus\u002F1701921660448755901","twitter.com","My humble effort to help you start the weekend with a smile on your face.",1,{"listName":6,"listNumber":7,"listDate":8,"cardDate":26,"label":27,"title":28,"url":29,"domain":30,"summary":31,"timeToRead":32},1694718139,"culture","The Silent Killer of Your Operating Practice: Fear","https:\u002F\u002Freview.firstround.com\u002Fthe-silent-killer-of-your-operating-practice-fear","review.firstround.com","Amanda Schwartz Ramirez shares excellent advice on how to level up your executive team to push it further: \"But at a fast-growing company, it's very easy to become hyper-focused on your piece of the puzzle, rather than how the constellation of pieces fit together. This is why team-building exercises, like ropes courses and escape rooms, are a favorite on leadership team offsite agendas: to remind you that you’ll accomplish much more together, versus going about it alone.\"",14,{"listName":6,"listNumber":7,"listDate":8,"cardDate":34,"label":27,"title":35,"url":36,"domain":37,"summary":38,"timeToRead":39},1694112863,"Shreyas Doshi: Better Teams, Better Products (Video)","https:\u002F\u002Ffs.blog\u002Fknowledge-project-podcast\u002Fshreyas-doshi\u002F","fs.blog","When Shane Parrish (of The Knowledge Project) and Shreyas Doshi (one of the best product leader thinkers) meet for an interview, I know there will be so much value to receive.",89,{"listName":6,"listNumber":7,"listDate":8,"cardDate":41,"label":27,"title":42,"url":43,"domain":44,"summary":45,"timeToRead":15},1694717041,"Your Customers Hate MVPs. Make a SLC Instead.","https:\u002F\u002Flongform.asmartbear.com\u002Fslc\u002F","longform.asmartbear.com","\"Simple, Lovable and Complete (SLC). We pronounce it “Slick.” As in: “What’s the ‘Slick’ version of your idea?” [...] With SLC, the outcomes are better and your options for next steps are better. If it fails, that’s OK; it’s a failed experiment. Both SLCs and MVPs will sometimes produce that result because the whole point is to experiment. But if a SLC succeeds, you’ve already delivered real value to customers and you have multiple futures available to you, none of which are urgent. You could build a v2, and because you’re already generating value, you have more time to decide what that should look like.\" -- Slick (SLC) is a healthier way to treat your customers while ensuring you can build a sustainable business.",[47,55,60],{"listName":6,"listNumber":7,"listDate":8,"cardDate":48,"label":49,"title":50,"url":51,"domain":52,"summary":53,"timeToRead":54},1694775296,"peopleware","1 Trick to Finish Your Next Talk in Style","https:\u002F\u002Fdavidnihill.com\u002F1-trick-to-finish-your-next-talk-in-style\u002F","davidnihill.com","Never ending the talk with Q&A is a brilliant advice I never considered: \"As you approach the end of your talk, say, “Okay, I am going to take a few questions before I make my conclusion.” This lets the audience know that you are not quite finished, keeps the Q&A shorter, and allows you to finish in a way that the audience knows it’s over. When they know it’s over they will applaud in unison. In leaving them with your main takeaways as a summary, you are also more likely to be remembered.\"",3,{"listName":6,"listNumber":7,"listDate":8,"cardDate":56,"label":49,"title":57,"url":58,"domain":22,"summary":59,"timeToRead":54},1694717621,"What Is One Belief or Strategy You Have Adopted That Has Made Your Life Easier? (Thread)","https:\u002F\u002Ftwitter.com\u002FJamesClear\u002Fstatus\u002F1702053326609957105","I love the answers in this thread, for example \"Telling my time where to go instead of wondering where it went (planning). I don’t wing it. I plan it.\" I'm not sure yet what I'd answer to this question, thinking of maybe \"Crafting habits and working on ideas I'd be proud to do for decades, not years.\"",{"listName":6,"listNumber":7,"listDate":8,"cardDate":61,"label":49,"title":62,"url":63,"domain":64,"summary":65,"timeToRead":66},1694719187,"My Approach to Coding Interviews: Optimize for Iteration","https:\u002F\u002Fsurma.dev\u002Fthings\u002Fspreadsheet\u002F","surma.dev","\"Optimizing for Iteration also means to write code in a way that allows you to switch out parts easily as new constraints come in. My general advice to keep code flexible is to not hard-code constants, to use many small, well-named functions and to keep code DRY. Keeping functions small makes it easier to verify just by reading that a function does what it’s supposed to do. If constrainst change, it’s often a matter of augmenting or replacing a single function, without having to touch any of the other parts. Another nice side-effect is that a good function name is basically docmentation and helps the interviewer understand what you are doing.\" -- Surma's approach to focus on “make it work, make it right, make it fast” while asking the interviewer what he should optimize for (e.g. accuracy? performance? accessibility?) is a healthy and mature approach that most interviewers will appreciate.",13,[68,74],{"listName":6,"listNumber":7,"listDate":8,"cardDate":69,"label":70,"title":71,"url":72,"domain":22,"summary":73,"timeToRead":24},1694717515,"inspirational","Companies die a death by thousand group decisions","https:\u002F\u002Ftwitter.com\u002FShaanVP\u002Fstatus\u002F1701968075484971430","",{"listName":6,"listNumber":7,"listDate":8,"cardDate":75,"label":70,"title":76,"url":77,"domain":22,"summary":73,"timeToRead":24},1694717804,"debugging is the art of increasingly understanding the divergence between what you thought you want and what you actually want","https:\u002F\u002Ftwitter.com\u002Fgdb\u002Fstatus\u002F1700327166930534731",1786100464347]