<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://hpc.social/personal-blog/feed.xml" rel="self" type="application/atom+xml" /><link href="https://hpc.social/personal-blog/" rel="alternate" type="text/html" hreflang="en-US" /><updated>2025-10-08T21:12:00-06:00</updated><id>https://hpc.social/personal-blog/feed.xml</id><title type="html">hpc.social - Aggregated Personal Blog</title><subtitle>Shared personal experiences and stories</subtitle><author><name>hpc.social</name><email>
[email protected]</email></author><entry><title type="html">The trap of prioritizing impact</title><link href="https://hpc.social/personal-blog/2025/the-trap-of-prioritizing-impact/" rel="alternate" type="text/html" title="The trap of prioritizing impact" /><published>2025-09-20T14:46:41-06:00</published><updated>2025-09-20T14:46:41-06:00</updated><id>https://hpc.social/personal-blog/2025/the-trap-of-prioritizing-impact</id><content type="html" xml:base="https://hpc.social/personal-blog/2025/the-trap-of-prioritizing-impact/"><![CDATA[<p>(I wrote this originally as a comment in <a href="https://randsinrepose.com/welcome-to-rands-leadership-slack/">RLS </a>in response to a staff-level engineer who was frustrated at how little they got to code anymore, and it resonated with enough folks that maybe it’s worth sharing here!)</p>
0 commit comments