diff options
| -rw-r--r-- | about/resources.html | 164 | ||||
| -rw-r--r-- | gemfeed/2024-10-24-staff-engineer-book-notes.html | 63 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 65 | ||||
| -rw-r--r-- | index.html | 2 | ||||
| -rw-r--r-- | notes/staff-engineer.html | 63 | ||||
| -rw-r--r-- | uptime-stats.html | 2 |
6 files changed, 274 insertions, 85 deletions
diff --git a/about/resources.html b/about/resources.html index 2796f546..3afd35a9 100644 --- a/about/resources.html +++ b/about/resources.html @@ -47,100 +47,100 @@ <span>In random order:</span><br /> <br /> <ul> +<li>Data Science at the Command Line; Jeroen Janssens; O'Reilly</li> +<li>Effective Java; Joshua Bloch; Addison-Wesley Professional</li> +<li>Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O'Reilly</li> +<li>Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press</li> +<li>DevOps And Site Reliability Engineering Handbook; Stephen Fleming; Audible</li> +<li>The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible</li> +<li>Raku Fundamentals; Moritz Lenz; Apress</li> +<li>Terraform Cookbook; Mikael Krief; Packt Publishing</li> +<li>Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers </li> +<li>Leanring eBPF; Liz Rice; O'Reilly</li> +<li>Java ist auch eine Insel; Christian Ullenboom; </li> +<li>Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O'Reilly</li> +<li>Higher Order Perl; Mark Dominus; Morgan Kaufmann</li> <li>DNS and BIND; Cricket Liu; O'Reilly</li> -<li>Modern Perl; Chromatic ; Onyx Neon Press</li> +<li>100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications</li> +<li>The Kubernetes Book; Nigel Poulton; Unabridged Audiobook</li> +<li>The Docker Book; James Turnbull; Kindle</li> <li>Concurrency in Go; Katherine Cox-Buday; O'Reilly</li> -<li>Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press</li> -<li>DevOps And Site Reliability Engineering Handbook; Stephen Fleming; Audible</li> -<li>Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers</li> -<li>Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O'Reilly</li> -<li>Funktionale Programmierung; Peter Pepper; Springer</li> -<li>21st Century C: C Tips from the New School; Ben Klemens; O'Reilly</li> -<li>Raku Recipes; J.J. Merelo; Apress</li> <li>C++ Programming Language; Bjarne Stroustrup;</li> +<li>Raku Recipes; J.J. Merelo; Apress</li> <li>Developing Games in Java; David Brackeen and others...; New Riders</li> -<li>Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O'Reilly</li> -<li>Data Science at the Command Line; Jeroen Janssens; O'Reilly</li> +<li>Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly</li> +<li>97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly</li> +<li>Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers</li> +<li>Effective awk programming; Arnold Robbins; O'Reilly</li> +<li>Polished Ruby Programming; Jeremy Evans; Packt Publishing</li> +<li>21st Century C: C Tips from the New School; Ben Klemens; O'Reilly</li> <li>Clusterbau mit Linux-HA; Michael Schwartzkopff; O'Reilly</li> -<li>Terraform Cookbook; Mikael Krief; Packt Publishing</li> -<li>Systemprogrammierung in Go; Frank Müller; dpunkt</li> -<li>Higher Order Perl; Mark Dominus; Morgan Kaufmann</li> <li>The KCNA (Kubernetes and Cloud Native Associate) Book; Nigel Poulton</li> -<li>The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible</li> -<li>100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications</li> +<li>The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress</li> +<li>Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press</li> +<li>Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson</li> <li>Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner</li> -<li>The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional</li> -<li>97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly</li> -<li>Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications</li> -<li>Leanring eBPF; Liz Rice; O'Reilly</li> -<li>The Pragmatic Programmer; David Thomas; Addison-Wesley</li> -<li>Polished Ruby Programming; Jeremy Evans; Packt Publishing</li> -<li>Effective awk programming; Arnold Robbins; O'Reilly</li> -<li>The Kubernetes Book; Nigel Poulton; Unabridged Audiobook</li> +<li>Modern Perl; Chromatic ; Onyx Neon Press</li> <li>Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall & Jon Orwant; O'Reilly</li> -<li>Pro Puppet; James Turnbull, Jeffrey McCune; Apress</li> -<li>Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt </li> -<li>Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson</li> +<li>Systemprogrammierung in Go; Frank Müller; dpunkt</li> <li>Ultimate Go Notebook; Bill Kennedy</li> -<li>Effective Java; Joshua Bloch; Addison-Wesley Professional</li> -<li>Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly</li> -<li>The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress</li> +<li>Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt </li> <li>Perl New Features; Joshua McAdams, brian d foy; Perl School</li> -<li>Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press</li> -<li>Raku Fundamentals; Moritz Lenz; Apress</li> -<li>The Docker Book; James Turnbull; Kindle</li> -<li>Java ist auch eine Insel; Christian Ullenboom; </li> +<li>The Pragmatic Programmer; David Thomas; Addison-Wesley</li> +<li>Pro Puppet; James Turnbull, Jeffrey McCune; Apress</li> +<li>The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional</li> +<li>Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications</li> <li>Site Reliability Engineering; How Google runs production systems; O'Reilly</li> -<li>Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers </li> +<li>Funktionale Programmierung; Peter Pepper; Springer</li> </ul><br /> <h2 style='display: inline' id='technical-references'>Technical references</h2><br /> <br /> <span>I didn't read them from the beginning to the end, but I am using them to look up things. The books are in random order:</span><br /> <br /> <ul> -<li>Relayd and Httpd Mastery; Michael W Lucas</li> -<li>Understanding the Linux Kernel; Daniel P. Bovet, Marco Cesati; O'Reilly</li> -<li>BPF Performance Tools - Linux System and Application Observability, Brendan Gregg; Addison Wesley</li> -<li>The Linux Programming Interface; Michael Kerrisk; No Starch Press </li> +<li>Algorithms; Robert Sedgewick, Kevin Wayne; Addison Wesley</li> <li>Groovy Kurz & Gut; Joerg Staudemeier; O'Reilly</li> <li>Implementing Service Level Objectives; Alex Hidalgo; O'Reilly</li> -<li>Algorithms; Robert Sedgewick, Kevin Wayne; Addison Wesley</li> +<li>BPF Performance Tools - Linux System and Application Observability, Brendan Gregg; Addison Wesley</li> +<li>Relayd and Httpd Mastery; Michael W Lucas</li> +<li>The Linux Programming Interface; Michael Kerrisk; No Starch Press </li> +<li>Understanding the Linux Kernel; Daniel P. Bovet, Marco Cesati; O'Reilly</li> </ul><br /> <h2 style='display: inline' id='self-development-and-soft-skills-books'>Self-development and soft-skills books</h2><br /> <br /> <span>In random order:</span><br /> <br /> <ul> -<li>The Off Switch; Mark Cropley; Virgin Books</li> +<li>The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books</li> +<li>Soft Skills; John Sommez; Manning Publications</li> <li>The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon & Schuster UK</li> -<li>The Joy of Missing Out; Christina Crook; New Society Publishers</li> +<li>Stop starting, start finishing; Arne Roock; Lean-Kanban University </li> +<li>Time Management for System Administrators; Thomas A. Limoncelli; O'Reilly</li> +<li>Ultralearning; Anna Laurent; Self-published via Amazon</li> <li>Ultralearning; Scott Young; Thorsons</li> -<li>Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion </li> -<li>The Power of Now; Eckhard Tolle; Yellow Kite</li> -<li>Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press</li> -<li>101 Essays that change the way you think; Brianna Wiest; Audible</li> -<li>Atomic Habits; James Clear; Random House Business</li> -<li>The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books</li> <li>Staff Engineer: Leadership beyond the management track; Will Larson; Audible</li> -<li>The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd</li> -<li>Never Split the Difference; Chris Voss, Tahl Raz; Random House Business</li> -<li>Digital Minimalism; Cal Newport; Portofolio Penguin</li> -<li>Ultralearning; Anna Laurent; Self-published via Amazon</li> -<li>Deep Work; Cal Newport; Piatkus</li> -<li>Soft Skills; John Sommez; Manning Publications</li> -<li>Psycho-Cybernetics; Maxwell Maltz; Perigee Books</li> <li>Slow Productivity; Cal Newport; Penguin Random House</li> +<li>Eat That Frog!; Brian Tracy; Hodder Paperbacks</li> +<li>101 Essays that change the way you think; Brianna Wiest; Audible</li> +<li>Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion </li> +<li>Never Split the Difference; Chris Voss, Tahl Raz; Random House Business</li> +<li>Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press</li> +<li>So Good They Can't Ignore You; Cal Newport; Business Plus</li> <li>The Good Enough Job; Simone Stolzoff; Ebury Edge</li> +<li>Deep Work; Cal Newport; Piatkus</li> +<li>Digital Minimalism; Cal Newport; Portofolio Penguin</li> +<li>Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing</li> <li>The Complete Software Developer's Career Guide; John Sonmez; Unabridged Audiobook</li> -<li>Stop starting, start finishing; Arne Roock; Lean-Kanban University </li> -<li>Influence without Authority; A. Cohen, D. Bradford; Wiley</li> -<li>Time Management for System Administrators; Thomas A. Limoncelli; O'Reilly</li> -<li>Eat That Frog!; Brian Tracy; Hodder Paperbacks</li> -<li>The Bullet Journal Method; Ryder Carroll; Fourth Estate</li> <li>Search Inside Yourself - The Unexpected path to Achieving Success, Happiness (and World Peace); Chade-Meng Tan, Daniel Goleman, Jon Kabat-Zinn; HarperOne</li> +<li>The Power of Now; Eckhard Tolle; Yellow Kite</li> +<li>The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd</li> +<li>Atomic Habits; James Clear; Random House Business</li> +<li>The Joy of Missing Out; Christina Crook; New Society Publishers</li> +<li>Psycho-Cybernetics; Maxwell Maltz; Perigee Books</li> +<li>The Bullet Journal Method; Ryder Carroll; Fourth Estate</li> <li>The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select</li> -<li>Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing</li> -<li>So Good They Can't Ignore You; Cal Newport; Business Plus</li> +<li>Influence without Authority; A. Cohen, D. Bradford; Wiley</li> +<li>The Off Switch; Mark Cropley; Virgin Books</li> </ul><br /> <a class='textlink' href='../notes/index.html'>Here are notes of mine for some of the books</a><br /> <br /> @@ -149,21 +149,21 @@ <span>Some of these were in-person with exams; others were online learning lectures only. In random order:</span><br /> <br /> <ul> +<li>The Ultimate Kubernetes Bootcamp; School of Devops; O'Reilly Online</li> +<li>Scripting Vim; Damian Conway; O'Reilly Online</li> +<li>Apache Tomcat Best Practises; 3-day on-site training</li> <li>Structure and Interpretation of Computer Programs; Harold Abelson and more...; </li> -<li>Protocol buffers; O'Reilly Online</li> <li>AWS Immersion Day; Amazon; 1-day interactive online training </li> -<li>Developing IaC with Terraform (with Live Lessons); O'Reilly Online</li> -<li>Ultimate Go Programming; Bill Kennedy; O'Reilly Online</li> -<li>Apache Tomcat Best Practises; 3-day on-site training</li> -<li>Functional programming lecture; Remote University of Hagen</li> <li>MySQL Deep Dive Workshop; 2-day on-site training</li> -<li>Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon</li> -<li>The Ultimate Kubernetes Bootcamp; School of Devops; O'Reilly Online</li> +<li>Protocol buffers; O'Reilly Online</li> +<li>Developing IaC with Terraform (with Live Lessons); O'Reilly Online</li> <li>Algorithms Video Lectures; Robert Sedgewick; O'Reilly Online</li> +<li>The Well-Grounded Rubyist Video Edition; David. A. Black; O'Reilly Online</li> +<li>Ultimate Go Programming; Bill Kennedy; O'Reilly Online</li> <li>Red Hat Certified System Administrator; Course + certification (Although I had the option, I decided not to take the next course as it is more effective to self learn what I need)</li> +<li>Functional programming lecture; Remote University of Hagen</li> <li>F5 Loadbalancers Training; 2-day on-site training; F5, Inc. </li> -<li>Scripting Vim; Damian Conway; O'Reilly Online</li> -<li>The Well-Grounded Rubyist Video Edition; David. A. Black; O'Reilly Online</li> +<li>Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon</li> <li>Linux Security and Isolation APIs Training; Michael Kerrisk; 3-day on-site training</li> </ul><br /> <h2 style='display: inline' id='technical-guides'>Technical guides</h2><br /> @@ -171,8 +171,8 @@ <span>These are not whole books, but guides (smaller or larger) which I found very useful. in random order:</span><br /> <br /> <ul> -<li>Advanced Bash-Scripting Guide </li> <li>Raku Guide at https://raku.guide </li> +<li>Advanced Bash-Scripting Guide </li> </ul><br /> <h2 style='display: inline' id='podcasts'>Podcasts</h2><br /> <br /> @@ -181,16 +181,16 @@ <span>In random order:</span><br /> <br /> <ul> -<li>Deep Questions with Cal Newport</li> -<li>The Pragmatic Engineer Podcast</li> -<li>Dev Interrupted</li> -<li>Backend Banter</li> <li>Maintainable</li> -<li>Go Time (Changelog)</li> -<li>Ship it (Changelog) </li> +<li>Backend Banter</li> <li>Cup o' Go [Golang]</li> -<li>The ProdCast (Google SRE Podcast)</li> +<li>The Pragmatic Engineer Podcast</li> +<li>Ship it (Changelog) </li> <li>Hidden Brain</li> +<li>The ProdCast (Google SRE Podcast)</li> +<li>Dev Interrupted</li> +<li>Go Time (Changelog)</li> +<li>Deep Questions with Cal Newport</li> </ul><br /> <h3 style='display: inline' id='podcasts-i-liked'>Podcasts I liked</h3><br /> <br /> @@ -207,15 +207,15 @@ <span>This is a mix of tech and non-tech newsletters I am subscribed to. In random order:</span><br /> <br /> <ul> -<li>Andreas Brandhorst Newsletter (Sci-Fi author)</li> <li>Ruby Weekly</li> <li>byteSizeGo</li> -<li>VK Newsletter</li> <li>The Imperfectionist</li> -<li>Register Spill</li> +<li>VK Newsletter</li> <li>Applied Go Weekly Newsletter</li> -<li>Golang Weekly</li> <li>The Valuable Dev</li> +<li>Register Spill</li> +<li>Andreas Brandhorst Newsletter (Sci-Fi author)</li> +<li>Golang Weekly</li> </ul><br /> <h1 style='display: inline' id='formal-education'>Formal education</h1><br /> <br /> diff --git a/gemfeed/2024-10-24-staff-engineer-book-notes.html b/gemfeed/2024-10-24-staff-engineer-book-notes.html index 58b8b2d9..53c02836 100644 --- a/gemfeed/2024-10-24-staff-engineer-book-notes.html +++ b/gemfeed/2024-10-24-staff-engineer-book-notes.html @@ -30,10 +30,73 @@ <br /> <ul> <li><a href='#staff-engineer-book-notes'>"Staff Engineer" book notes</a></li> +<li>⇢ <a href='#the-four-archetypes-of-a-staff-engineer'>The Four Archetypes of a Staff Engineer</a></li> +<li>⇢ <a href='#influence-and-impact-over-authority'>Influence and Impact over Authority</a></li> +<li>⇢ <a href='#breadth-and-depth-of-knowledge'>Breadth and Depth of Knowledge</a></li> +<li>⇢ <a href='#mentorship-and-sponsorship'>Mentorship and Sponsorship</a></li> +<li>⇢ <a href='#managing-up-and-across'>Managing Up and Across</a></li> +<li>⇢ <a href='#strategic-thinking'>Strategic Thinking</a></li> +<li>⇢ <a href='#emotional-intelligence'>Emotional Intelligence</a></li> +<li>⇢ <a href='#navigating-ambiguity'>Navigating Ambiguity</a></li> +<li>⇢ <a href='#visible-and-invisible-work'>Visible and Invisible Work</a></li> +<li>⇢ <a href='#scaling-yourself'>Scaling Yourself</a></li> +<li>⇢ <a href='#career-progression-and-title-inflation'>Career Progression and Title Inflation</a></li> <li>⇢ <a href='#not-a-faster-senior-engineer'>Not a faster Senior Engineer</a></li> <li>⇢ <a href='#the-balance'>The Balance</a></li> <li>⇢ <a href='#more-things'>More things</a></li> </ul><br /> +<h2 style='display: inline' id='the-four-archetypes-of-a-staff-engineer'>The Four Archetypes of a Staff Engineer</h2><br /> +<br /> +<span>Larson breaks down the role of a Staff Engineer into four main archetypes, which can help frame how you approach the role:</span><br /> +<br /> +<ul> +<li>Tech Lead: Focuses on the technical direction of a team, ensuring high-quality execution, architecture, and aligning the team around shared goals.</li> +<li>Solver: Gets pulled into complex, high-impact problems that often involve many teams or systems, operating as a fixer or troubleshooter.</li> +<li>Architect: Works on the long-term technical vision for an organization, setting standards and designing systems that will scale and last over time.</li> +<li>Right Hand: Functions as a trusted technical advisor to leadership, providing input on strategy, long-term decisions, and navigating organizational politics.</li> +</ul><br /> +<h2 style='display: inline' id='influence-and-impact-over-authority'>Influence and Impact over Authority</h2><br /> +<br /> +<span>As a Staff Engineer, influence is often more important than formal authority. You’ll rarely have direct control over teams or projects but will need to drive outcomes by influencing peers, other teams, and leadership. It’s about understanding how to persuade, align, and mentor others to achieve technical outcomes.</span><br /> +<br /> +<h2 style='display: inline' id='breadth-and-depth-of-knowledge'>Breadth and Depth of Knowledge</h2><br /> +<br /> +<span>Staff Engineers often need to maintain a breadth of knowledge across various areas while maintaining depth in a few. This can mean keeping a high-level understanding of several domains (e.g., infrastructure, security, product development) but being able to dive deep when needed in certain core areas.</span><br /> +<br /> +<h2 style='display: inline' id='mentorship-and-sponsorship'>Mentorship and Sponsorship</h2><br /> +<br /> +<span>An important part of a Staff Engineer’s role is mentoring others, not just in technical matters but in career development as well. Sponsorship goes a step beyond mentorship, where you actively advocate for others, create opportunities for them, and push them toward growth.</span><br /> +<br /> +<h2 style='display: inline' id='managing-up-and-across'>Managing Up and Across</h2><br /> +<br /> +<span>Success as a Staff Engineer often depends on managing up (influencing leadership and setting expectations) and managing across (working effectively with peers and other teams). This is often tied to communication skills, the ability to advocate for technical needs, and fostering alignment across departments or organizations.</span><br /> +<br /> +<h2 style='display: inline' id='strategic-thinking'>Strategic Thinking</h2><br /> +<br /> +<span>While Senior Engineers may focus on execution, Staff Engineers are expected to think strategically, making decisions that will affect the company or product months or years down the line. This means balancing short-term execution needs with long-term architectural decisions, which may require challenging short-term pressures.</span><br /> +<br /> +<h2 style='display: inline' id='emotional-intelligence'>Emotional Intelligence</h2><br /> +<br /> +<span>The higher you go in engineering roles, the more soft skills, particularly emotional intelligence (EQ), come into play. Building relationships, resolving conflicts, and understanding the broader emotional dynamics of the team and organization become key parts of your role.</span><br /> +<br /> +<h2 style='display: inline' id='navigating-ambiguity'>Navigating Ambiguity</h2><br /> +<br /> +<span>Staff Engineers are often placed in situations with high ambiguity—whether in defining the problem space, coming up with a solution, or aligning stakeholders. The ability to operate effectively in these unclear areas is critical to success.</span><br /> +<br /> +<h2 style='display: inline' id='visible-and-invisible-work'>Visible and Invisible Work</h2><br /> +<br /> +<span>Much of the work done by Staff Engineers is invisible. Solving complex problems, creating alignment, or influencing decisions doesn’t always result in tangible code, but it can have a massive impact. Larson emphasizes that part of the role is being comfortable with this type of invisible contribution.</span><br /> +<br /> +<h2 style='display: inline' id='scaling-yourself'>Scaling Yourself</h2><br /> +<br /> +<span>At the Staff Engineer level, you must scale your impact beyond direct contribution. This can involve improving documentation, developing repeatable processes, mentoring others, or automating parts of the workflow. The idea is to enable teams and individuals to be more effective, even when you’re not directly involved.</span><br /> +<br /> +<h2 style='display: inline' id='career-progression-and-title-inflation'>Career Progression and Title Inflation</h2><br /> +<br /> +<span>Larson touches on how different companies have varying definitions of "Staff Engineer," and titles don’t always correlate directly with responsibility or skill. He emphasizes the importance of focusing more on the work you're doing and the impact you're having, rather than the title itself.</span><br /> +<br /> +<span>These additional points reflect more of the strategic, interpersonal, and leadership aspects that go beyond the technical expertise expected at this level. The role of a Staff Engineer is often about balancing high-level strategy with technical execution, while influencing teams and projects in a sustainable, long-term way.</span><br /> +<br /> <h2 style='display: inline' id='not-a-faster-senior-engineer'>Not a faster Senior Engineer</h2><br /> <br /> <ul> diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 15d5ee5f..46762008 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> - <updated>2024-10-24T20:59:32+03:00</updated> + <updated>2024-10-24T21:11:23+03:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="https://foo.zone/gemfeed/atom.xml" rel="self" /> @@ -40,10 +40,73 @@ <br /> <ul> <li><a href='#staff-engineer-book-notes'>"Staff Engineer" book notes</a></li> +<li>⇢ <a href='#the-four-archetypes-of-a-staff-engineer'>The Four Archetypes of a Staff Engineer</a></li> +<li>⇢ <a href='#influence-and-impact-over-authority'>Influence and Impact over Authority</a></li> +<li>⇢ <a href='#breadth-and-depth-of-knowledge'>Breadth and Depth of Knowledge</a></li> +<li>⇢ <a href='#mentorship-and-sponsorship'>Mentorship and Sponsorship</a></li> +<li>⇢ <a href='#managing-up-and-across'>Managing Up and Across</a></li> +<li>⇢ <a href='#strategic-thinking'>Strategic Thinking</a></li> +<li>⇢ <a href='#emotional-intelligence'>Emotional Intelligence</a></li> +<li>⇢ <a href='#navigating-ambiguity'>Navigating Ambiguity</a></li> +<li>⇢ <a href='#visible-and-invisible-work'>Visible and Invisible Work</a></li> +<li>⇢ <a href='#scaling-yourself'>Scaling Yourself</a></li> +<li>⇢ <a href='#career-progression-and-title-inflation'>Career Progression and Title Inflation</a></li> <li>⇢ <a href='#not-a-faster-senior-engineer'>Not a faster Senior Engineer</a></li> <li>⇢ <a href='#the-balance'>The Balance</a></li> <li>⇢ <a href='#more-things'>More things</a></li> </ul><br /> +<h2 style='display: inline' id='the-four-archetypes-of-a-staff-engineer'>The Four Archetypes of a Staff Engineer</h2><br /> +<br /> +<span>Larson breaks down the role of a Staff Engineer into four main archetypes, which can help frame how you approach the role:</span><br /> +<br /> +<ul> +<li>Tech Lead: Focuses on the technical direction of a team, ensuring high-quality execution, architecture, and aligning the team around shared goals.</li> +<li>Solver: Gets pulled into complex, high-impact problems that often involve many teams or systems, operating as a fixer or troubleshooter.</li> +<li>Architect: Works on the long-term technical vision for an organization, setting standards and designing systems that will scale and last over time.</li> +<li>Right Hand: Functions as a trusted technical advisor to leadership, providing input on strategy, long-term decisions, and navigating organizational politics.</li> +</ul><br /> +<h2 style='display: inline' id='influence-and-impact-over-authority'>Influence and Impact over Authority</h2><br /> +<br /> +<span>As a Staff Engineer, influence is often more important than formal authority. You’ll rarely have direct control over teams or projects but will need to drive outcomes by influencing peers, other teams, and leadership. It’s about understanding how to persuade, align, and mentor others to achieve technical outcomes.</span><br /> +<br /> +<h2 style='display: inline' id='breadth-and-depth-of-knowledge'>Breadth and Depth of Knowledge</h2><br /> +<br /> +<span>Staff Engineers often need to maintain a breadth of knowledge across various areas while maintaining depth in a few. This can mean keeping a high-level understanding of several domains (e.g., infrastructure, security, product development) but being able to dive deep when needed in certain core areas.</span><br /> +<br /> +<h2 style='display: inline' id='mentorship-and-sponsorship'>Mentorship and Sponsorship</h2><br /> +<br /> +<span>An important part of a Staff Engineer’s role is mentoring others, not just in technical matters but in career development as well. Sponsorship goes a step beyond mentorship, where you actively advocate for others, create opportunities for them, and push them toward growth.</span><br /> +<br /> +<h2 style='display: inline' id='managing-up-and-across'>Managing Up and Across</h2><br /> +<br /> +<span>Success as a Staff Engineer often depends on managing up (influencing leadership and setting expectations) and managing across (working effectively with peers and other teams). This is often tied to communication skills, the ability to advocate for technical needs, and fostering alignment across departments or organizations.</span><br /> +<br /> +<h2 style='display: inline' id='strategic-thinking'>Strategic Thinking</h2><br /> +<br /> +<span>While Senior Engineers may focus on execution, Staff Engineers are expected to think strategically, making decisions that will affect the company or product months or years down the line. This means balancing short-term execution needs with long-term architectural decisions, which may require challenging short-term pressures.</span><br /> +<br /> +<h2 style='display: inline' id='emotional-intelligence'>Emotional Intelligence</h2><br /> +<br /> +<span>The higher you go in engineering roles, the more soft skills, particularly emotional intelligence (EQ), come into play. Building relationships, resolving conflicts, and understanding the broader emotional dynamics of the team and organization become key parts of your role.</span><br /> +<br /> +<h2 style='display: inline' id='navigating-ambiguity'>Navigating Ambiguity</h2><br /> +<br /> +<span>Staff Engineers are often placed in situations with high ambiguity—whether in defining the problem space, coming up with a solution, or aligning stakeholders. The ability to operate effectively in these unclear areas is critical to success.</span><br /> +<br /> +<h2 style='display: inline' id='visible-and-invisible-work'>Visible and Invisible Work</h2><br /> +<br /> +<span>Much of the work done by Staff Engineers is invisible. Solving complex problems, creating alignment, or influencing decisions doesn’t always result in tangible code, but it can have a massive impact. Larson emphasizes that part of the role is being comfortable with this type of invisible contribution.</span><br /> +<br /> +<h2 style='display: inline' id='scaling-yourself'>Scaling Yourself</h2><br /> +<br /> +<span>At the Staff Engineer level, you must scale your impact beyond direct contribution. This can involve improving documentation, developing repeatable processes, mentoring others, or automating parts of the workflow. The idea is to enable teams and individuals to be more effective, even when you’re not directly involved.</span><br /> +<br /> +<h2 style='display: inline' id='career-progression-and-title-inflation'>Career Progression and Title Inflation</h2><br /> +<br /> +<span>Larson touches on how different companies have varying definitions of "Staff Engineer," and titles don’t always correlate directly with responsibility or skill. He emphasizes the importance of focusing more on the work you're doing and the impact you're having, rather than the title itself.</span><br /> +<br /> +<span>These additional points reflect more of the strategic, interpersonal, and leadership aspects that go beyond the technical expertise expected at this level. The role of a Staff Engineer is often about balancing high-level strategy with technical execution, while influencing teams and projects in a sustainable, long-term way.</span><br /> +<br /> <h2 style='display: inline' id='not-a-faster-senior-engineer'>Not a faster Senior Engineer</h2><br /> <br /> <ul> @@ -10,7 +10,7 @@ <body> <h1 style='display: inline' id='foozone'>foo.zone</h1><br /> <br /> -<span class='quote'>This site was generated at 2024-10-24T21:04:20+03:00 by <span class='inlinecode'>Gemtexter</span></span><br /> +<span class='quote'>This site was generated at 2024-10-24T21:11:23+03:00 by <span class='inlinecode'>Gemtexter</span></span><br /> <br /> <span>Welcome to the foo.zone. Everything you read on this site is my personal opinion and experience. You can call me a Linux/*BSD enthusiast and hobbyist. I mainly write about tech, IT, programming and sometimes also about self-improvement here. Note that this blog usually does not overlap with what I do at my day job as a Site Reliability Engineer.</span><br /> <br /> diff --git a/notes/staff-engineer.html b/notes/staff-engineer.html index 459aa6e8..a08bb25d 100644 --- a/notes/staff-engineer.html +++ b/notes/staff-engineer.html @@ -30,10 +30,73 @@ <br /> <ul> <li><a href='#staff-engineer-book-notes'>"Staff Engineer" book notes</a></li> +<li>⇢ <a href='#the-four-archetypes-of-a-staff-engineer'>The Four Archetypes of a Staff Engineer</a></li> +<li>⇢ <a href='#influence-and-impact-over-authority'>Influence and Impact over Authority</a></li> +<li>⇢ <a href='#breadth-and-depth-of-knowledge'>Breadth and Depth of Knowledge</a></li> +<li>⇢ <a href='#mentorship-and-sponsorship'>Mentorship and Sponsorship</a></li> +<li>⇢ <a href='#managing-up-and-across'>Managing Up and Across</a></li> +<li>⇢ <a href='#strategic-thinking'>Strategic Thinking</a></li> +<li>⇢ <a href='#emotional-intelligence'>Emotional Intelligence</a></li> +<li>⇢ <a href='#navigating-ambiguity'>Navigating Ambiguity</a></li> +<li>⇢ <a href='#visible-and-invisible-work'>Visible and Invisible Work</a></li> +<li>⇢ <a href='#scaling-yourself'>Scaling Yourself</a></li> +<li>⇢ <a href='#career-progression-and-title-inflation'>Career Progression and Title Inflation</a></li> <li>⇢ <a href='#not-a-faster-senior-engineer'>Not a faster Senior Engineer</a></li> <li>⇢ <a href='#the-balance'>The Balance</a></li> <li>⇢ <a href='#more-things'>More things</a></li> </ul><br /> +<h2 style='display: inline' id='the-four-archetypes-of-a-staff-engineer'>The Four Archetypes of a Staff Engineer</h2><br /> +<br /> +<span>Larson breaks down the role of a Staff Engineer into four main archetypes, which can help frame how you approach the role:</span><br /> +<br /> +<ul> +<li>Tech Lead: Focuses on the technical direction of a team, ensuring high-quality execution, architecture, and aligning the team around shared goals.</li> +<li>Solver: Gets pulled into complex, high-impact problems that often involve many teams or systems, operating as a fixer or troubleshooter.</li> +<li>Architect: Works on the long-term technical vision for an organization, setting standards and designing systems that will scale and last over time.</li> +<li>Right Hand: Functions as a trusted technical advisor to leadership, providing input on strategy, long-term decisions, and navigating organizational politics.</li> +</ul><br /> +<h2 style='display: inline' id='influence-and-impact-over-authority'>Influence and Impact over Authority</h2><br /> +<br /> +<span>As a Staff Engineer, influence is often more important than formal authority. You’ll rarely have direct control over teams or projects but will need to drive outcomes by influencing peers, other teams, and leadership. It’s about understanding how to persuade, align, and mentor others to achieve technical outcomes.</span><br /> +<br /> +<h2 style='display: inline' id='breadth-and-depth-of-knowledge'>Breadth and Depth of Knowledge</h2><br /> +<br /> +<span>Staff Engineers often need to maintain a breadth of knowledge across various areas while maintaining depth in a few. This can mean keeping a high-level understanding of several domains (e.g., infrastructure, security, product development) but being able to dive deep when needed in certain core areas.</span><br /> +<br /> +<h2 style='display: inline' id='mentorship-and-sponsorship'>Mentorship and Sponsorship</h2><br /> +<br /> +<span>An important part of a Staff Engineer’s role is mentoring others, not just in technical matters but in career development as well. Sponsorship goes a step beyond mentorship, where you actively advocate for others, create opportunities for them, and push them toward growth.</span><br /> +<br /> +<h2 style='display: inline' id='managing-up-and-across'>Managing Up and Across</h2><br /> +<br /> +<span>Success as a Staff Engineer often depends on managing up (influencing leadership and setting expectations) and managing across (working effectively with peers and other teams). This is often tied to communication skills, the ability to advocate for technical needs, and fostering alignment across departments or organizations.</span><br /> +<br /> +<h2 style='display: inline' id='strategic-thinking'>Strategic Thinking</h2><br /> +<br /> +<span>While Senior Engineers may focus on execution, Staff Engineers are expected to think strategically, making decisions that will affect the company or product months or years down the line. This means balancing short-term execution needs with long-term architectural decisions, which may require challenging short-term pressures.</span><br /> +<br /> +<h2 style='display: inline' id='emotional-intelligence'>Emotional Intelligence</h2><br /> +<br /> +<span>The higher you go in engineering roles, the more soft skills, particularly emotional intelligence (EQ), come into play. Building relationships, resolving conflicts, and understanding the broader emotional dynamics of the team and organization become key parts of your role.</span><br /> +<br /> +<h2 style='display: inline' id='navigating-ambiguity'>Navigating Ambiguity</h2><br /> +<br /> +<span>Staff Engineers are often placed in situations with high ambiguity—whether in defining the problem space, coming up with a solution, or aligning stakeholders. The ability to operate effectively in these unclear areas is critical to success.</span><br /> +<br /> +<h2 style='display: inline' id='visible-and-invisible-work'>Visible and Invisible Work</h2><br /> +<br /> +<span>Much of the work done by Staff Engineers is invisible. Solving complex problems, creating alignment, or influencing decisions doesn’t always result in tangible code, but it can have a massive impact. Larson emphasizes that part of the role is being comfortable with this type of invisible contribution.</span><br /> +<br /> +<h2 style='display: inline' id='scaling-yourself'>Scaling Yourself</h2><br /> +<br /> +<span>At the Staff Engineer level, you must scale your impact beyond direct contribution. This can involve improving documentation, developing repeatable processes, mentoring others, or automating parts of the workflow. The idea is to enable teams and individuals to be more effective, even when you’re not directly involved.</span><br /> +<br /> +<h2 style='display: inline' id='career-progression-and-title-inflation'>Career Progression and Title Inflation</h2><br /> +<br /> +<span>Larson touches on how different companies have varying definitions of "Staff Engineer," and titles don’t always correlate directly with responsibility or skill. He emphasizes the importance of focusing more on the work you're doing and the impact you're having, rather than the title itself.</span><br /> +<br /> +<span>These additional points reflect more of the strategic, interpersonal, and leadership aspects that go beyond the technical expertise expected at this level. The role of a Staff Engineer is often about balancing high-level strategy with technical execution, while influencing teams and projects in a sustainable, long-term way.</span><br /> +<br /> <h2 style='display: inline' id='not-a-faster-senior-engineer'>Not a faster Senior Engineer</h2><br /> <br /> <ul> diff --git a/uptime-stats.html b/uptime-stats.html index f44d2c84..c7b68e86 100644 --- a/uptime-stats.html +++ b/uptime-stats.html @@ -10,7 +10,7 @@ <body> <h1 style='display: inline' id='my-machine-uptime-stats'>My machine uptime stats</h1><br /> <br /> -<span class='quote'>This site was last updated at 2024-10-24T21:04:20+03:00</span><br /> +<span class='quote'>This site was last updated at 2024-10-24T21:11:23+03:00</span><br /> <br /> <span>The following stats were collected via <span class='inlinecode'>uptimed</span> on all of my personal computers over many years and the output was generated by <span class='inlinecode'>guprecords</span>, the global uptime records stats analyser of mine.</span><br /> <br /> |