What I'm Reading: July 1
- Ben Leibowitz
- Jul 1, 2023
- 2 min read
Updated: Jul 9, 2023
Tech
For example, when you ask a doctor, "What medication should I take to stop my stomach pain?," a good doctor will think about the original problem, X: "I have stomach pain, and I want to stop feeling stomach pain"
The way out of the XY problem: provide context when communicating and asking for help, and think in terms of goals, not solutions
Tools, monitoring, automation, plenty of excess computing capacity, an architecture that minimizes the blast radius of problems, guardrails preventing bad things from happening in the first place, and general good SRE work (there's probably a lot of overlap there...)
Improper monitoring can be confusing and expensive - here are some ways to rethink it
Most logs are never accessed, so sample where possible (and store audit-required logs in as cold storage as you can)
Think holistically about logs, metrics, and tracing, rather than jus trelying on logs
Bruce Schneier on his firsthand experience breaking the Snowden NSA story, 10 years later
Especially impactful in customer service, software engineering, marketing / sales, and R&D
Half of today's work could be automated between 2030 and 2060
Will accelerate the pace of labor force change, and will require investments to support workers shifting jobs and learning new skills
An open-source backup tool (haven't tried it yet, but looks interesting)
Make space to do whatever at work, and how to prioritize and plan for it
Make time to work on things that energize you, allow you to learn, or pique your curiosity
Encourage engineers to take ownership, make priorities clear, plan for regular time to work on whatever