<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Python - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/python/</link><description>Python - Tag - AWS Sensei</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 30 May 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://aws-sensei.cloud/tags/python/" rel="self" type="application/rss+xml"/><item><title>Deploy smarter, sleep better — unit tests and change detection for Lambda APIs</title><link>https://aws-sensei.cloud/posts/2026-05-30-testing-selective-deployment/</link><pubDate>Sat, 30 May 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-05-30-testing-selective-deployment/</guid><description>🔊 Voiced by Amazon Polly
As long as a project runs only for me, a failed deployment is annoying but harmless. That changes the moment the first LinkedIn post goes out and real readers land on the site. A broken chat widget, a dead contact form, or a failed sentiment analysis is no longer just a personal problem — it&amp;rsquo;s a bad first impression.
That was the trigger to tackle two things I&amp;rsquo;d been putting off: unit tests for all Lambda functions and a pipeline that only deploys what actually changed.</description></item></channel></rss>