<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Workflow on ppl-blog</title><link>https://rifqi-blog.vercel.app/tags/workflow/</link><description>Recent content in Workflow on ppl-blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rifqi-blog.vercel.app/tags/workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>Git, Linear, Discord: The Automation Layer That Replaced Manual Status Updates</title><link>https://rifqi-blog.vercel.app/posts/discord-linear-dev-workflow/</link><pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate><guid>https://rifqi-blog.vercel.app/posts/discord-linear-dev-workflow/</guid><description>&lt;p&gt;The friction in team development isn&amp;rsquo;t usually the code. It&amp;rsquo;s the overhead around the code: knowing what&amp;rsquo;s in review, who&amp;rsquo;s working on what, whether a ticket moved, whether that MR you were waiting on is finally merged. Most teams solve this by adding a status-update ritual — a daily standup field, a manual Discord message, a ticket that someone remembers to update after they&amp;rsquo;re done. This works until someone forgets, or the meeting cadence doesn&amp;rsquo;t match the merge cadence, or you&amp;rsquo;re on a different timezone.&lt;/p&gt;</description></item></channel></rss>