Daily Edition · Page 4

THE DAILY INDEX

Technology, AI, software, security, crypto and business

ARTICLES & TUTORIALS

TLDR Web Dev

FROM 20S DOWN TO 1S: HOW WE SHAVED OFF 19S FROM OUR GRAPHQL API QUERIES

A team was looking to optimize GraphQL query time and explored several options like pagination, reducing the number of nested queries, caching, filtering, and more. However, one approach was the most effective and reduced large GraphQL query time from 20 seconds to 1 second. They did this by optimizing SQL queries against the database and it’s very simple - instead of using SELECT *, specify the columns you want. This will reduce payload size and reduce database overfetching.

HOW I WRITE HTTP SERVICES IN GO AFTER 13 YEARS

This article covers in-depth service testing, optimizing startup and shutdown, avoiding global state, handling common request types, and controlling the environment through flags, and environment variables. When writing HTTP services in Go, the author only uses one HTTP handler per service and relies on HTTP routes to divert traffic to the right handlers within each service. Functions are used as handlers and dependencies are passed as arguments.

FINDING A NEW SOFTWARE DEVELOPER JOB

After being laid off, this author had trouble finding a new job. He detailed all the ways he made himself open to new opportunities, utilizing LinkedIn, job ads, and specialized platforms. Throughout the process, he maintained meticulous tracking of applications and learned to navigate salary negotiations and technical assessments. The author details his entire journey from start to finish, with transparency and tips along the way.

IT'S TIME TO BREAK FREE FROM CORPORATE AGILE

Agile methodologies in corporate environments ("Corporate Agile") commonly have bloated processes and misplaced priorities, shown by excessive meetings and too many middle managers. A return to "Basic Agile," with an emphasis on principles over rigid processes, will allow teams to self-organize and adapt under uncertainty. Basic Agile done right has a focused, quick daily meeting to discuss potential blockers, short sprint planning sessions, and immediate issue resolution.

FIGURE OUT WHO'S LEAVING THE COMPANY: DUMP, DIFF, REPEAT

A system called "epitaphs" at a company this author worked at had entries for departed employees. The company’s employees also created their own system to track changes in the employee directory, allowing for insights into departures and other events. The author provides technical details for implementing similar systems which can be created informally at other companies to help employees have a better sense of layoffs and departures.

TLDR IndexPage 4