<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Career on arlind.dev</title><link>https://arlind.dev/tags/career/</link><description>Recent content in Career on arlind.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 07 Apr 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://arlind.dev/tags/career/index.xml" rel="self" type="application/rss+xml"/><item><title>When a Demo Reshuffles Your Roadmap</title><link>https://arlind.dev/blog/when-a-demo-reshuffles-your-roadmap/</link><pubDate>Tue, 07 Apr 2026 07:00:00 +0000</pubDate><guid>https://arlind.dev/blog/when-a-demo-reshuffles-your-roadmap/</guid><description>You&amp;rsquo;re two weeks from finishing a milestone. The team is in a rhythm. The next milestone is scoped, the tickets are written, and the order of work is settled: Feature A first, then Feature B. It&amp;rsquo;s clean. Everyone knows what&amp;rsquo;s coming.
Then someone demos the product to a customer, and everything shifts.
The feedback that rearranges everything It usually doesn&amp;rsquo;t come as a dramatic reveal. It&amp;rsquo;s a comment during a sales call, a question from a prospect that nobody has a good answer to, or a demo where the audience fixates on a screen you considered secondary.</description></item></channel></rss>