walkerrandolphsmith · walkerrandolphsmith · Jul 29, 2025 · Jul 29, 2025
diff --git a/linkedin-posts/.attachments/full-words.png b/linkedin-posts/.attachments/full-words.png
diff --git a/linkedin-posts/.attachments/kubcon.png b/linkedin-posts/.attachments/kubcon.png
diff --git a/linkedin-posts/.attachments/plausible-dashaboard.png b/linkedin-posts/.attachments/plausible-dashaboard.png
diff --git a/linkedin-posts/behavior-change.md b/linkedin-posts/behavior-change.md
@@ -0,0 +1,18 @@
+💡 Some code and system changes are clearly the right move.
+Better performance. More secure. Less risk.
+But there’s a catch: they require behavior change.
+
+You can’t force these shifts. You have to lead them.
+
+Here’s what’s worked for me:
+
+🔹 Build trust with small wins before asking for big shifts
+🔹 Paint the long-term vision, not just the short-term gain
+🔹 Show success—don’t just talk theory
+🔹 Break change into small, frictionless steps
+🔹 Meet hesitation with curiosity, not pressure
+🔹 Celebrate progress, not perfection
+
+Technical wins don’t stick without social buy-in. Build that first.
+
+https://www.linkedin.com/posts/walkerrandolphsmith_some-code-and-system-changes-are-clearly-activity-7355929595780448257-HUbu?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/dead-letter-queue.md b/linkedin-posts/dead-letter-queue.md
@@ -0,0 +1,9 @@
+Your dead letter queue is not a graveyard. 🪦 
+It's where revenue goes to die quietly. 💸 
+Most teams ignore it until it’s too late.
+
+Here’s what mature engineering orgs do instead—and why your team should too.
+
+https://walkersmith.me/blog/hidden-cost-of-ignoring-dead-letter-queue
+
+https://www.linkedin.com/posts/walkerrandolphsmith_the-hidden-cost-of-ignoring-your-dead-letter-activity-7348042343947624449-rDcz?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/diligent-developer.md b/linkedin-posts/diligent-developer.md
@@ -0,0 +1,14 @@
+Some of the engineers I respect most aren’t the ones reaching for the newest tool or framework.
+
+They don’t jump straight to tech solutions.
+They’re grounded, patient, and methodical.
+
+They look closely at the real pain points. Bottlenecks, flaky processes, operational friction and work through them one step at a time.
+
+Sometimes the fix is a small script.
+Sometimes it’s a process change.
+Sometimes it’s just asking a better question.
+
+It’s not flashy, but it moves teams forward in ways that last.
+
+https://www.linkedin.com/posts/walkerrandolphsmith_some-of-the-engineers-i-respect-most-aren-activity-7354542057530482688-5m08?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/kubecon-2025.md b/linkedin-posts/kubecon-2025.md
@@ -0,0 +1,7 @@
+Join me at hashtag#KubeCon + hashtag#CloudNativeCon North America in November!
+
+https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
+
+![kubecon announcement](kubcon.png)
+
+https://www.linkedin.com/posts/walkerrandolphsmith_kubecon-cloudnativecon-activity-7351258628240121856-OSJC?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/leet-code.md b/linkedin-posts/leet-code.md
@@ -0,0 +1,18 @@
+Still grinding LeetCode after landing the job?
+Not because I'll have to.
+Not because it’s “fun.” 😅 
+Not even because I think it’s a perfect measure of engineering skill.
+
+But because I know sharp minds get dull fast.
+
+Yeah, I’ve heard all the takes:
+ “It’s a broken hiring signal.”
+ “It’s nothing like real-world engineering.”
+ “I haven’t opened LeetCode in years and I’m doing just fine.”
+
+Cool. But when that next opportunity hits—or that systems question comes out of nowhere in a perf review—I’d rather be ready than right. 🔥 
+
+
+> Hot takes welcome. I'll lean in.
+
+https://www.linkedin.com/posts/walkerrandolphsmith_still-grinding-leetcode-after-landing-the-activity-7348040596248293379-0DBO?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/new-domain.md b/linkedin-posts/new-domain.md
@@ -0,0 +1,13 @@
+🚀 New domain. Same mission. Fresh look.
+👉 https://walkersmith.me
+
+For everyone who followed along at 🔁 walkerrandolphsmith.com — don’t worry, that domain still works and redirects automatically. No broken links. No dead ends.
+
+Thanks for sticking with me — 
+
+To check out how I made this possible read more at https://lnkd.in/emYzgFcQ
+—
+🛠️ Built with:
+ #React #Nextjs #Azure #WebDev #PersonalSite
+
+ https://www.linkedin.com/posts/walkerrandolphsmith_walker-smith-activity-7344361865822560259-ndiF?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/plausible-how-to.md b/linkedin-posts/plausible-how-to.md
@@ -0,0 +1,7 @@
+Check out how I used hashtag#Plausible to get behavioral analytics for my portfolio site. I used Azure Kubernetes with Nginx controller to expose the cluster to Azure Front Door and enabled end to end encryption with automatically rotated TLS certs using cert manager. DNS acme challenges that leveraged 100% secret-less updates to the DNS Zone. 
+
+😅 A bit much for a portfolio site, but very fun journey
+
+https://walkersmith.me/blog/plausible-in-aks-with-fully-automated-tls
+
+https://www.linkedin.com/posts/walkerrandolphsmith_self-hosting-plausible-analytics-on-aks-behind-activity-7352027297211641856-USsl?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/plausible.md b/linkedin-posts/plausible.md
@@ -0,0 +1,16 @@
+📊 Just added analytics to my personal site, and here's why I'm sharing it early.
+I recently integrated Plausible Analytics to start tracking what people engage with. It’s still early. Not much traffic yet, and no real insights to speak of — but that’s kind of the point. I want to build with feedback, not in a vacuum.
+
+If you’re a creator, engineer, or indie builder:
+ 👉 What are you learning from your own analytics?
+ 👉 How do you decide what content or projects are worth pursuing?
+
+I'd love to hear how you're thinking about growth, curiosity, and the signals that help guide you.
+
+https://walkersmith.me/blog
+
+#buildinpublic #developerlife #techblog #creators #plausibleanalytics
+
+![plausible dashboard](./.attachments/plausible-dashaboard.png)
+
+https://www.linkedin.com/posts/walkerrandolphsmith_buildinpublic-developerlife-techblog-activity-7349083333395431424-5I3Y?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/preview-links.md b/linkedin-posts/preview-links.md
@@ -0,0 +1,8 @@
+Ship with Confidence, Not Just Speed. Preview links are just the beginning — discover how full-stack ephemeral environments supercharge testing, reduce bugs, and bring engineering, product, and marketing into perfect launch alignment 🚀 
+
+#nx #k8s #IAC #product #DX
+
+https://walkersmith.me/blog/environment-vs-request-isolation
+
+
+https://www.linkedin.com/posts/walkerrandolphsmith_from-preview-links-to-full-ephemeral-environments-activity-7348736187508924418-LsSi?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/retry.md b/linkedin-posts/retry.md
@@ -0,0 +1,11 @@
+A downstream API went down for a moment. It should’ve been a blip.
+Instead, every client retried at once—over and over—and exhausted the system.
+
+Smarter retries use backoff, jitter, and know when to wait like respecting Retry-After headers.
+
+Read how to avoid turning recovery into failure:
+👉 https://lnkd.in/eqmGrfKR
+
+#devops #resilience #systemdesign
+
+https://www.linkedin.com/posts/walkerrandolphsmith_smarter-retries-how-to-build-resilient-systems-activity-7347385597075881984-MiYx?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/rewrites.md b/linkedin-posts/rewrites.md
@@ -0,0 +1,7 @@
+Rewrites won’t cover up bad practices. 
+
+Incremental delivery can go hand in hand with incremental improvement
+
+#softwaredevelopment #developer #systemsthinking
+
+https://www.linkedin.com/posts/walkerrandolphsmith_softwaredevelopment-developer-systemsthinking-activity-7349831742343593985-Wfme?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/taking-code-review-feedback.md b/linkedin-posts/taking-code-review-feedback.md
@@ -0,0 +1,15 @@
+💬 Many folks talk about how to give better code reviews. Use “nit,” be kind, focus on the code, not the coder.
+But what about getting better at taking feedback?
+
+Here’s what I’ve learned (and keep learning):
+1. It’s not personal. Ever.
+2. Don’t dismiss. If you disagree or think it’s out of scope, say why and track it.
+3. Agree in theory, not in practice? Explain the tradeoff.
+4. If a “nit” comes up a lot, codify it. Save everyone time.
+5. Say thanks. Reviewers are investing in your growth.
+
+Code review is a team sport. The better we get at receiving feedback, the better the whole team gets.
+
+Shout out to Andrew Smith for giving the best code review feedback and Hepcibha Addakula for helping me grow and level up at giving and receiving feedback!
+
+https://www.linkedin.com/posts/walkerrandolphsmith_many-folks-talk-about-how-to-give-better-activity-7353974436275884032-Okqe?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE
diff --git a/linkedin-posts/use-full-words.md b/linkedin-posts/use-full-words.md
@@ -0,0 +1,9 @@
+➡️ Use full words like authenticate or authorization instead of abbreviations like auth.
+
+💡It can prevent assumptions when seeing the code out of context 
+
+#CleanCode #DeveloperTips #JavaScript #CodeReadability #SoftwareEngineering
+
+![full words coding example](./.attachments/full-words.png)
+
+https://www.linkedin.com/posts/walkerrandolphsmith_cleancode-developertips-javascript-activity-7350485540867072002-M9ge?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAqnqGQB9vu4sAnxFYA9TgPi-2AeQbt3qsE