Issue #462

Friday 3rd November’s issue is presented by FusionAuth

Don’t Build Your Own Auth. Try FusionAuth Today.

FusionAuth integrates with any tech stack and is deployable anywhere – cloud, on-premise, or even the server running under your desk.

You're less than five minutes from login/registration, social logins, SSO, MFA, passwordless, user management, passkeys, and much more.

Join the thousands of developers who trust FusionAuth for their identity needs.

Start For Free Today

Organize Your Week As An Engineering Manager

— Nicolla Ballotta

tl;dr: "What should my week look like, and what exactly should I be doing?" This question is particularly pertinent for those who have transitioned from a developer role, where their schedule was often tightly structured and well-defined. In this essay, I aim not only to provide answers to these questions but also to guide you through the process of creating a weekly calendar that reflects the typical responsibilities of an EM."

Leadership Management

Hire Better Managers: 35 Interview Questions For Assessing A Candidate

tl;dr: The first few questions are: (1) What are 1-2 questions you always ask your team members in one-on-one meetings, and why? (2) If I asked someone on your team about your leadership style, what would they say? (3) Tell me about a time when you delved into significant detail and got your hands dirty. (4) What ritual or practice have you found to be most effective for helping your team connect and collaborate? (5) Why did you leave IC work?

Management Hiring

Making Sure Your Auth System Can Scale

— James Hickey

tl;dr: The balance between authentication security and performance is a perpetual challenge. This article dives into the heart of this issue, emphasizing the trade-off between stringent security practices and system scalability. You'll find practical tips to maintain secure auth while meeting customer demands, and discover strategies to make sure your systems remain secure and efficient.

Promoted by FusionAuth

Management Scale

7 Types Of Difficult Coworkers And How To Deal With Them

— Jordan Cutler

tl;dr: Jordan interviews Raviraj Achar - tech lead at Meta for 5 years - about how he manages difficult co-workers. The following are the first 3 archetypes discussed, along with how to work with them: (1) Risk-Averse: They want to avoid risk at all costs and don’t want the system to break. (2) Risk-Taker: The opposite of the prior archetype. This person often feels the risk is justified or they will propose ideas without scoping out the risk. (3) The Stealthy Critic: They will have opinions but save them for the last minute before something is ready to ship. Or they will comment on your design doc and leave things in an ambiguous state. 

CareerAdvice

“Always remember, that there’s usually a simpler and better way to do something than the first way that pops into your head.”

— Donald Knuth

I Accidentally Saved Half A Million Dollars

tl;dr: "Let's start with some background, because it is fucking wild that an inefficiency that took me five minutes to solve in a GUI configuration panel was allowed to persist. We cancelled someone's contract the week before I did this. Someone lost their job because no one could get their act together long enough to click the button I told them to click."

Entertaining

The Five Principles Of Modern Developer Tools

— Chris Bell, Sam Seely

tl;dr: "Here are the principles of the modern developer tool that emerged from our own work solving customer challenges, and that we're seeing in other developer tools we use." The authors discuss the following: (1) Work with resources in code. (2) Source control management. (3) Rich type definitions. (4) Run tests locally and in your CI workflow. (5) Manage as part of your deployment lifecycle.

DevTools

My Muscle-Memory Git Toolbox

— Arthur O’Dwyer

tl;dr: "This post focuses on my basic muscle-memory git commands. There are at least two other major Git subtopics this post doesn’t mention at all: “branching discipline” (what is a release branch? what’s the difference between rebase and merge?) and “hygiene” (how big should a commit be? what does a good commit message look like?). That is — as usual for this blog — we’re talking tactics, not strategy."

Git

How To (And How Not To) Design REST APIs

— Jeff Schnitzer

tl;dr: "In my career, I have consumed hundreds of REST APIs and produced dozens. Since I often see the same mistakes repeated in API design, I thought it might be nice to write down a set of best practices. And poke fun at a couple widely-used APIs. Much of this may be "duh", but there might be a few rules you haven't considered yet."

API BestPractices

Notable Links

Bruno: Opensource IDE for exploring and testing Api's.

Local AI Stack: Starter kit to build local-only AI apps.

Payloads: List of useful payloads for web application security.

Smallchat: Minimal programming example for a chat server.

System Design Primer: Learn how to design large-scale systems.

Click the below and shoot me an email!

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

1 … 2 … 3 … 4 … 5