Issue #530

Issue #530


Tuesday 9th July’s issue is presented by QA Wolf

🤯 Get 80% Automated E2E Test Coverage By October


More than 2/3rd of dev teams test less than 50% of their workflows, causing bugs to sneak out. QA Wolf gets your organization to 80% automated E2E test coverage in less than 4 months.


They create and maintain your test suite in open-source Playwright. Plus, they provide unlimited parallel test runs on their infrastructure (24-hour maintenance included).


The results? With QA Wolf, Drata’s team of 80+ engineers achieved 4x more test cases and 86% faster QA cycles.

The Right Kind Of Stubborn

— Paul Graham


tl;dr: Paul compares persistence and obstinance. “When you look at the internal structure of persistence, it doesn't resemble obstinacy at all. It's so much more complex. Five distinct qualities — energy, imagination, resilience, good judgement, and focus on a goal — combine to produce a phenomenon that seems a bit like obstinacy in the sense that it causes you not to give up. But the way you don't give up is completely different.”


Leadership Management

Standups: Individual → Teammate

— Kent Beck


tl;dr: Kent discusses his reasoning behind standups. “Treating standup meetings as a technical solution to a technical problem — we need to communicate this many bits of information to this many people as efficiently as possible — misses the real point. We’re people. With needs. The better those needs are met, the better we can meet the needs of others.”  


Leadership Management

Drata Secured 86% Faster QA Cycles


tl;dr: QA Wolf is delivering QA at DrataSpeed: (1) Regression testing is 90 minutes faster than before, and includes 4x more test cases. (2) Quickly onboarded and gave Drata’s QA resources space to work on new features, saving more than $500,000/year. (3) Went from overnight deploys to multiple times daily.


Promoted by QA Wolf

Tests Management

Notes For New Hires

— Clinton Blackburn


tl;dr: “I’m onboarding new engineers at Vori, and finally took some time to write a few ideas I’ve been kicking around and sharing internally. I have personally found these practices helpful over the past few years, and think others might, as well. This isn’t applicable to only junior engineers, or new hires. I didn’t learn some of these lessons until I was eight years into my career as a tech lead at edX, or a couple years later at Stripe.”


CareerAdvice


“Technical problems can be remediated. A dishonest corporate culture is much harder to fix.”


— Bruce Schneier


Solving A Math Problem With Planner Programming

— Hillel Wayne


tl;dr: “Suppose that at the beginning there is a blank document, and a letter "a" is written in it. In the following steps, only the three functions of "select all", "copy" and "paste" can be used. Find the minimum number of steps to reach at least 100,000 a's. If the target number is not specified, and I want to get the exact amount of a, is there a general formula?”


Design

Building A Hybrid Sign-Up / Subscribe Form With Stripe Elements

— Brian Morrison


tl;dr: A practical guide on how to use custom flows, webhooks, and user metadata to build a single form that automatically subscribes new users using Stripe Element 


Promoted by Clerk

Guide

Reverse Engineering TicketMaster's Rotating Barcodes


tl;dr: “I recently purchased tickets to a concert from TicketMaster. If they had issued me normal, printable PDF tickets I could save offline to my phone, this article would’ve never been penned. But of course this is 2024: Nothing we do online can be simple anymore.”


ReverseEngineering

8 Versions Of UUID And When To Use Them
— Nicole Tietz-Sokolskaya


tl;dr: “I was onboarding a friend into one of my side project codebases and she asked me why I was using a particular type of UUID. I'd heard about this type while working on that project, and it's really neat. So instead of hogging that knowledge for just us, here it is: some good uses for different versions of UUID.”


UUID

Writing Tips for Improving Your Pull Requests

— Jeff Mueller


tl;dr: “I’m going to show you how to purposely write less by using the techniques below.” Tips are: (1) Make it scannable. (2) Speak plainly. (3) Avoid adverbs. (4) Simplify your sentences. (5) Avoid a passive voice. Jeff adds examples to each.



Git Tips

Most Popular From Last Issue

Notable Links


GPT4All: Chat with local LLMs on any device.


GS Quant: Python toolkit for quantitative finance.


Pongo: Mongo on Postgres with consistency benefits.


Public APIs: Collective list of free APIs.


Termino: Web based terminal on any website.


Click the below and shoot me an email!


1 = Didn't enjoy it all // 5 = Really enjoyed it


12345