Issue #156

10 October 2019

Weekly Reading For Technical Leaders
The Early Disciple Of Remote Startups
- Tomasz Tunguz, Managing Director at Redpoint
#Remote #Management

tl;dr: "Remote forces you to do the things you should be doing anyway earlier and better." As a virtue of being remote, you establish and commit to core values and other HR functions much sooner. 
- Leah Neukirchen
tl;dr: Leah found some old files that contained passwords of previous computer scientists including Ken Thompson, which she tried to crack for fun. She cracked all except Ken's. It took 4+ days to finally crack and realize what his password was. ♛
- Gergely Orosz, Engineering Lead at Uber
tl;dr: Guide on approaching a promotion - (1) do your preparation (2) set your sight on the promotion (3) get help & frequent feedback (4) put in the work (5) stay grounded (6) help others.
- Chris Zacharias, Founder at imgix, Ex-YouTuber
#PageWeight #YouTube
tl;dr: Chris was tasked with YouTube page from 1.2MB to under 100KB. When his code went into production, latency of requests increased. Why? He had unlocked users in new geographies that could finally watch YouTube, albeit with slower connections. 
 #Career #Management #Etsy
tl;dr: How the Etsy team define their career ladder for engineers, and what it actually looks like, here. The key is to "be clear enough, and flexible enough, to provide direction for any engineer at the company."
- Christina Marfice
#Productivity #DeepWork
tl;dr: Tools and tips for developers to achieve deep work, including ways to incorporate it into your schedule, how to build a routine, time management ⏰ and communication tips.  
 Thanks for reading. please complete these 3 questions to give me feedbackor just hit reply.
- Eric Khun, Infrastructure Engineer at Buffer
tl;dr: Benefits are (1) work on something you care about (2) make money on the side (3) potential for a full-time business 💼 (3) improve skills (4) easier to find jobs (5) learn about yourself. 
- Jacob Herrington, Senior Software Engineer at Dev
tl;dr: A good message should be able to allow the readers to understand (1) what was done at a glance (2) why the change was necessary (3) the details about what was done (4) any useful details concerning the change. You can see the template here
- Stuart Langridge, Web Consultant & Custom Developer
#Javascript #Video
tl;dr: "At some point everything changed: the tail started to wag the dog instead and development became JS-first." You shouldn't rely on JS as much, plus practical strategies for building without a JS framework. 
- Core PG Team
tl;dr: "PostgreSQL 12 enhancements include notable improvements to query performance, particularly over larger data sets, and overall space utilization."
#CPython #Python #HashTables
tl;dr: Post about "what hash tables are, why you would use them, and how they’re used to implement dictionaries in the most popular Python interpreter - CPython"
- Kent Dodds, Software Engineer and Teacher
tl;dr: Guide on "how to use the React DevTools and React's profiling build to properly profile a production app". 
Notable Developer Conferences 2019
React Day Berlin 
Nov 30
Berlin, Germany
Microsoft Ignite 
Nov 4-8
Orlando, Florida, USA
Dec 5-6

Paris, France
December 6-7

Riga, Latvia

or subscribe with