<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reflection on arlind.dev</title><link>https://arlind.dev/tags/reflection/</link><description>Recent content in Reflection on arlind.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 06 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://arlind.dev/tags/reflection/index.xml" rel="self" type="application/rss+xml"/><item><title>Progress Over Perfection: How to Ship When Your Code Embarrasses You</title><link>https://arlind.dev/blog/progress-over-perfection/</link><pubDate>Mon, 06 Apr 2026 12:00:00 +0000</pubDate><guid>https://arlind.dev/blog/progress-over-perfection/</guid><description>There&amp;rsquo;s a moment in every project where you look at the code you&amp;rsquo;re about to ship and feel a quiet dread. Not because it&amp;rsquo;s broken. It works. It passes tests. It does what the customer needs. But it&amp;rsquo;s not right. You can see the shortcuts, the places where you traded elegance for speed, the abstractions you didn&amp;rsquo;t have time to build.
If you&amp;rsquo;re a good engineer, this feeling is familiar. And if you&amp;rsquo;re not careful, it will make you slow.</description></item><item><title>Hello World</title><link>https://arlind.dev/blog/hello-world/</link><pubDate>Mon, 06 Apr 2026 08:00:00 +0000</pubDate><guid>https://arlind.dev/blog/hello-world/</guid><description>This is the beginning. A place to think out loud about the things I encounter in my work: the decisions, the tradeoffs, the lessons that only make sense in hindsight.
I plan to write about engineering and leadership, but also about the quieter things: how teams break down, what makes a good decision under pressure, the patterns that keep showing up across different problems.
Some posts will be deeply technical. Others will be more reflective.</description></item></channel></rss>