Issue #242

3 August 2021

Issue #242

Presented by Stream
tl;dr: 4 strategies outlined: (1) Live up to your word with deadlines and commitment. "Overdeliver." (2) Consider strategies to replace water cooler missed connections. (2) Come in to the office when necessary e.g. meet new hires, etc... (4) "Ensure you’re easy to work with."

tl;dr: (1) Define the project requirements thoroughly. (2) Review past project timelines to get a sense of accuracy for previous estimates, and how it might apply to your current project. (3) Breakdown tasks to assign points. (4) Talk to stakeholders and leverage the RACI framework, and more. 

Sponsored By Stream.

Heuristics For Effective Software Development: A Continuously Evolving List
- Allen Holub
#CareerAdvice #Management
tl;dr: An evolving list based off of the Agile Manifesto starting with: (1) "Without psychological safety, respect, and trust, none of the following is possible." (2) Process exists in service of people; the people come first. (3) "The best ways to work are collaborative...," and 24 more digestible points. 
Leaving Well
- Fred Wilson
#Management #Leadership
tl;dr: Leaving a company "well" is something leaders and companies should promote. Companies need to facilitate this process by reacting well to the news, perhaps providing a financial incentive to stick around during a transition. Fred believes it's best to set this culture up at the beginning as precedent is powerful, and people feel more comfortable being open and honest. 
#Performance #Algorithm
tl;dr: The author read a paper about implementing collaborative editing tools and one of the algorithms mentioned took over 3 seconds to process, which is slow. It was his own algorithm, and in this post he makes amends and shows hot to speed the tools up. 

A Note From Stream...

Free Chat & Activity Feed APIs for Qualifying Teams

Activate your free Stream Chat trial to start building today. Qualifying small teams and personal dev projects can also apply for the free-forever Stream Maker Account.
Pre-Mortem: Working Backwards in Software Design
-Seema Thapar
tl;dr: "Pre-mortem is a strategy in which a team imagines that a project has failed, and then works backward to determine what potentially could lead to the failure of a project." This encourages teams to "see the big picture", breaks down silos, requires teams to use their imagination and normalizes failure. Seema discusses how to execute one in this post. 
#Chrome #Performance
tl;dr: "This report investigates how 1000 of the most popular Chrome extensions impact browser performance and end-user experience." Key findings: (1) Extensions like Honey, Evernote Web Clipper, and Avira Browser Safety can have a significant negative impact on website speed." (2) On ad-heavy websites, ad blockers and privacy tools can greatly improve performance.
Why You Should Build On Kubernetes From Day One
- Max Horstmann
#Kubernetes #StackOverflow

tl;dr: It took a to get up: "provision virtual machines, install, configure, configure, configure." Once the cluster was up, "Kubernetes was great for us—but we wanted somebody else to run it." Max founds three benefits: (1) Managed Kubernetes does the heavy lifting. (2) You can mostly stay cloud agnostic. (3) Easily spin up new environments. 

#IndustryTrend #StackOverflow
tl;dr: Stack Overflow's 2021 developer survey. A key takeaway was "for the rising cohort of coders under the age of 18, online resources like videos and blogs are more popular than books and school combined, a statistic that doesn’t hold for any of our other age cohorts."
tl;dr: Optional chaining is used to manipulate an optional in a few ways, including "setting and retrieving the value of a property of the wrapped instance, setting and retrieving a value from a subscript on the wrapped instance, and calling a method on the wrapped instance." Khawer dives into how it works.

or subscribe with