Issue #144

6 June 2019

Issue #144
tl;dr: Larson shares his system for gauging size and state of engineering teams - ratios and frameworks to structuring team size, combining and spinning up teams, and assessing and accelerating team progress. 

Ethical Dilemmas in Software Engineering (Video)
Bryan Cantrill
tl;dr: 45 mins talk on the new dilemmas faced by software engineers, as software "eats the world", technology decision come with increasing pressure and responsibility. 

Becoming A Bad-ass Engineering Leader: 5 Tried And True Lessons From A Woman Of Color
- Rukmini Reddy

tl;dr: Reddy highlights the challenges she faced as she took on a lead engineer role, as both a female and person of color, along with the lessons she learned along the way. 

The Style Of A Leader
Alex MacCaw

tl;dr: The importance of showing vulnerability to your team and not ruling through authoritarianism. Most importantly, sharing fears and concerns creates a genuine sense of trust. 

Four Magic Numbers For Measuring Software Delivery
Dave Lush

tl;dr: (1) Lead Time  - time it takes to validate, design, implement and ship a new valuable thing (2) Deployment Frequency  - The no of times per developer per day we ship to production (3) Change Failure Percentage  -  When you deploy to production so regularly, do you keep breaking it? (4) Mean Time to Recovery / Resolution .

Click through the link here if you're paywalled. 

tl;dr: Pertinent Stack Overflow question for all of us - turns out that "sorting" is not actual the answer. 
#Management #Agile
tl;dr: How to develop accessibility practices into your agile processes (1) create central team to manage the transformation (2) Execute an ongoing empathy program (3) Curate a set of high-quality learning resources and integrate into onboarding (4) Form a team of accessibility coaches to coach teams (5) Create an accessibility dashboard. 

Building The Most Inaccessible Site Possible With A Perfect Lighthouse Score
- Manuel Matuzovic
tl;dr: Author shows how he hacked the system concluding that we shouldn't trust Lighthouse numbers blindly, automatic testing is a first step in understanding what's wrong with our overall system.


Why Haskell
- Hector Jusforgues

tl;dr: Semantic is a Haskell library and command line tool for parsing, analyzing, and comparing source code. This goes through why GitHub chose Haskell for Semantic's implementation language.

Rethinking Visual Programming With Go
- Martin Tournoij

tl;dr: Blog version of a talk given at GopherCon Europe on why Visual Programming Languages have failed and an experiment visualizing Go code. 

Enabling Modern JavaScript On NPM
Jason Miller

tl;dr: Author presents the fact that modern JS syntax lets you do more with less code, but how much of the JavaScript we ship to users is actually modern?

Tomomi Imura

tl;dr: Dog pics that represent HTTP statuses. Status 502 may be my fave. 
Notable Developer Conferences 2019
Full Stack Fest
September 4 - 6
Sitges, Barcelona

A 3-day, single track conference with topics ranging from GraphQL, WebAssembly, the JAMStack & Progressive User Interfaces to HTTP/3, Automation Testing, Serverless and the P2P web.

No matter if you consider yourself a backend, frontend developer, or anywhere in-between, Full Stack Fest is for you.
Microsoft Build 
May 6-8
Seattle, Washington, USA
May 21 - 23
Atlanta, Georgia, USA
May 22-23
Broomfield, Colorado, USA
July 17-18
Portland, Oregon, USA
Open Source Summit 
July 17-19
Tokyo, Japan
July 24-27
San Diego, California, USA
Sept 9–12
Las Vegas, Nevada, USA
Strange Loop 
Sept 12-14
St. Louis, Missouri, USA 
DjangoCon US 
Sept 22-27
San Diego, CA
Oracle CodeOne 
Sept 16–19
SF, California
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