Issue #149

2 August 2019

Issue #149
Weekly Reading For Technical Leaders
- Bob Nystrom, Engineer at Google
tl;dr: Code at Google is reviewed for readability, engineers tend to create name that are too long & verbose. A name has two goals - clarity and precision. The author provides examples and suggestions on how to shorten and improve naming. 
- Craig Mod, Writer and Photographer
tl;dr: When you experience software, apps that perform quickly build trust. When applications are bloated, take time to load or function a command, we tend to distrust them and we lose our "flow". Aim to build fast, light, software. The author cycles through many examples of what he likes and doesn't.  
- Jess Frazelle, Engineer
tl;dr: Some of the weak points of Kubernetes - it's not to be used for stateful data, often the control dashboard is unsecured leading to vulnerability, consistent issues around upgrading, and others. "With the good, comes the bad". 
Goodbye Docker: Purging is Such Sweet Sorrow
- Ian Miell, Open Source Coder & Speaker
tl;dr: Docker daemon was using 100% CPU on multiple cores, prompting the author to ask why does Docker need a Daemon at all. He runs through several substitutes and differences between them. 
- Shahin Sorkh, Full Stack Web Dev
tl;dr: Sanctions and censorship make it challenging to find and read necessary documentation for technologies, googling an issue becomes a challenge. Obviously, there are VPNs, proxies and other strategies to bypass the above issues but each come at a cost and risk.  
- J Cole Morrison, Cloud Architect & Software Engineer
tl;dr: Company was hacked though a "misconfigured firewall" allowing the hacker to use the EC2 IAM roles and act as the server, giving them access to all the S3 Buckets where the hacked info was stored.  
tl;dr: While a user of Go, the author feels it's on dangerous grounds as it's "bolting on" features, something seen as a common anti-pattern in language evolution. There's also an analysis of what defines a "perfect" language. 
- Alexandre Omeyer, CEO at Stepsize
tl;dr: A guide on when and how to take on tech debt, and a strategy on how much to take on or pay down. Identify files in your codebase with weak ownership because code ownership is a leading indicator of your codebase's health.
- Ian Lance Taylor, Google AI
tl;dr: What it would mean to add generics to Go. Generics enables the representation of functions and data structures in a generic form, with types factored out. Examples included. 
Postgres Tips For The Average And Power User
- Craig Kerstiens, Head of Cloud Team at Citus Data 
tl;dr: Some specific tips, some general ones, and some useful for debugging internals. 
- Carie Fisher, Senior Accessibility Consultant at Deque Systems
tl;dr: Inclusivity in tech is still a challenge, and that streams down to the way in which sites are designed. Making them inclusive for others is paramount, here are steps on how you should think about that. 
- Chad Hansen, Python Developer
tl;dr: Tutorial allows you to make sense of the next traceback you see, recognize some of the more common tracebacks and log a traceback successfully while still handling the exception. 
Notable Developer Conferences 2019
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