<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sentry on Daniel Ancuta</title><link>https://ancuta.org/tags/sentry/</link><description>Recent content in Sentry on Daniel Ancuta</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Daniel Ancuta</copyright><lastBuildDate>Sat, 01 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://ancuta.org/tags/sentry/index.xml" rel="self" type="application/rss+xml"/><item><title>Error tracking and incident response on production with Sentry + Squadcast + Linear + Slack</title><link>https://ancuta.org/posts/error-tracking-and-incident-response-on-production/</link><pubDate>Sat, 01 Jul 2023 00:00:00 +0000</pubDate><guid>https://ancuta.org/posts/error-tracking-and-incident-response-on-production/</guid><description>&lt;p&gt;There are multiple strategies to mitigate the number of bugs and problems with the app in production. Some teams focus on unit tests, functional tests, integration tests, manual tests, multiple environments to run those, and build the artifact of the app. Processes for reviewing code, static code analysis, CI/CD pipelines, and so on and so forth.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://ancuta.org/posts/error-tracking-and-incident-response-on-production/featured.jpg"/></item></channel></rss>