Issue #708
Essential Reading For Engineering Leaders
Friday 17th April’s issue is presented by Wealthfront
Earn Up to 4.05% APY On Your Cash
Most high-earning engineers leave their liquidity in low-yield legacy accounts — I used to do the same.
Optimize your finances with Wealthfront’s Cash Account: 3.30% APY + an extra 0.75% boost on your uninvested cash for Pointer readers when you open your first Cash Account (total 4.05% variable APY). APY that is 10x the national average. Zero monthly fees and instant transfers to eligible accounts. Checking features built-in.
15 Principles For Managing Up
— Wes Kao
tl;dr: “Wes gives phrases of how to verbalize each: (1) Embrace managing up. (2) Focus on the punchline. (3) Show your thought process. (4) Flag potential issues. (5) Bring solutions, not complaints. (6) Use information hierarchy. (7) Keep your manager in the loop. (8) Are you being micromanaged, or do you need to communicate better? (9) Over-communication might be the right amount. (10) Proactively assert what to do. (11) Don’t only ask questions. Share your point of view too. (12) Anticipate questions. (13) Know when to get out. (14) Be explicit about what you need. (15) Expect to manage up forever.”
Management Communication
The Impact Of AI On Software Engineers In 2026: Key Trends
— Gergely Orosz
tl;dr: “We’ve dug into your 900+ responses to look for trends in AI tool usage among software engineers and engineering leaders. This article surfaces insights that are less about specific tools, and more about the effect these tools have on tech professionals.”
DeveloperProductivity AI
Earn Up to 4.05% APY On Your Cash
tl;dr: “Most high-earning engineers leave their liquidity in low-yield legacy accounts. Optimize your finances with Wealthfront’s Cash Account: 3.30% APY + an extra 0.75% boost on your uninvested cash for Pointer readers when you open your first Cash Account (total 4.05% variable APY). APY that is 10x the national average. Zero monthly fees and instant transfers to eligible accounts. Checking features built-in.”
Promoted by Wealthfront
Compensation
Mechanical Sympathy
— Vicki Boykis
tl;dr: “Something that’s been floating around in my head lately is the idea that I don’t know any truly good engineers who are also not good at product design. Product design can roughly be designed as the contract between the creator and the user, where the contract is designed by a set of affordances, or actions that the product allows the user to take.”
CareerGrowth BestPractices
“Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.” — Steve Jobs
The Peril Of Laziness Lost
— Bryan Cantrill
tl;dr: “Of these virtues, I have always found laziness to be the most profound: packed within its tongue-in-cheek self-deprecation is a commentary on not just the need for abstraction, but the aesthetics of it. Laziness drives us to make the system as simple as possible (but no simpler!) — to develop the powerful abstractions that then allow us to do much more, much more easily.”
BestPractices TechDebt AI
AI Isn’t Waiting For Your Infrastructure To Catch Up
tl;dr: “Join us at IaCConf and get practical advice from engineers who’ve actually figured out what it takes to let AI touch your infrastructure safely. These speakers are walking through it live & sharing the hard-won lessons that took years to earn.”
Promoted by Spacelift
Infrastructure Event
Things You Didn’t Know About Indexes
tl;dr: “Database indexes are more nuanced than most engineers realize. The author walks through composite index ordering, why functions defeat indexes, and lesser-known Postgres features like partial, functional, and covering indexes — with practical examples and EXPLAIN output throughout.”
Database DeepDive PostgreSQL
Adding Correctness Conditions To Code Changes
— Jessica Kerr
tl;dr: “Today I looked at the first PR on our new project repo. It added a new run script, but the README didn’t mention it. The proposed change was incomplete, because the documentation was out of sync. Did I comment on the PR? heck no. I want to fix this problem for all PRs, not just this one. We can automate this stuff now.” Jessica shares how.
DeveloperProductivity BestPractices Agents
Flat Error Codes Are Not Enough
— Dmitrii Aleksandrov
tl;dr: “Most error-handling advice says to keep things flat: one error type, one enum of codes. Dmitrii argues this breaks down for libraries doing real IO work, where callers need structured detail.”