Issue #202

28 August 2020

Issue #202
A Reading Club For Software Developers - Sign Up Here
tl;dr: "There’s a huge mindset shift needed when you go from junior to senior. Writing code becomes a minor part of the job." Your focus becomes researching the problem, designing the solution and building consensus, each discussed here.
#Management #DevelopmentProcess
tl;dr: (1) "Learning as a team builds psychological safety: the feeling of being able to say what you mean without fearing judgment or negative consequences." (2) Retros are low hanging fruit (3) They put teams on the path to continuous improvement. Tim provides resources for facilitating retros. 
Why Johnny Won't Upgrade
- Jacques Mattheij
tl;dr: Why are users so reluctant to update software? Jacques believes "software vendors collectively royally messed it up," and has a list of specific reasons why software should be updated.
tl;dr: A framework for SLIs and SLOs, Elisa concludes with 6 things to remember, including (1) define SLIs and SLOs for specific capabilities at system boundaries. (2) Each logical instance of a system (for example, a database shard) gets its own SLO.
How To Read A Code
- Jonas Lundberg
tl;dr: With the end goal of building a mental model of an existing codebase, Jonas discusses useful techniques, such as the "generation effect" - making sure you are "forced to come up with an answer to a question pays off."
Computer Vision Consultation

If you have experience in CV & knowledge about the state of the technology, would love to chat with you for 20 mins to learn for a project I'm working on. 

Just reply to this email. 

#ComputerVision #MachineLearning
tl;dr: "How do we make optimal peanut butter and banana sandwiches? You take a picture of your banana and bread, pass the image through a deep learning model to locate said items, do some nonlinear curve fitting to the banana, transform to polar coordinates and “slice” the banana along the fitted curve..."
Web Browsers Need To Stop
- Drew DeVault
tl;dr: "At some point" browsers need to "stop adding scope and start focusing on performance, efficiency, reliability, and security at the scope" that already exists.
tl;dr: (1) Assimilation: languages that are able to intermingle with large existing language communities e.g. Typescript.(2) Security: Languages with built in security capabilities e.g. Kotlin (3) Versatility: ability to traverse a wide range of use cases e.g. Java.
tl;dr: "I find it fascinating to think about the world that might have been. Even more surprisingly, it happens that many of these other options include features which developers would love to see appear in CSS even today." Zack outlines some of the directions CSS could have taken.
tl;dr: "An aggregation of links that summarize RustConf 2020. Pull requests welcome!"

or subscribe with