<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authorship-Time on Revelara</title><link>https://revelara.ai/tags/authorship-time/</link><description>Recent content in Authorship-Time on Revelara</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 Jul 2026 08:00:00 -0700</lastBuildDate><atom:link href="https://revelara.ai/tags/authorship-time/index.xml" rel="self" type="application/rss+xml"/><item><title>Security Shifted Left. Reliability Can Too.</title><link>https://revelara.ai/blog/security-shifted-left-reliability-can-too/</link><pubDate>Tue, 28 Jul 2026 08:00:00 -0700</pubDate><guid>https://revelara.ai/blog/security-shifted-left-reliability-can-too/</guid><description>&lt;p&gt;For about a decade, security had the same shape as a punishment. You wrote your code, you opened your pull request, you felt good about your week, and then a scanner you didn&amp;rsquo;t run and couldn&amp;rsquo;t see filed a report against you. The findings landed after the fact, in a different tool, owned by a different team, and by the time they reached you the context that produced the code was gone. You were being asked to remember why you wrote a line you&amp;rsquo;d already forgotten writing.&lt;/p&gt;</description></item></channel></rss>