<?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>EngineeringPractice on Calyntro Blog</title><link>https://calyntro.com/blog/tags/engineeringpractice/</link><description>Recent content in EngineeringPractice on Calyntro Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://calyntro.com/blog/tags/engineeringpractice/index.xml" rel="self" type="application/rss+xml"/><item><title>Tests Don't Care Who Typed the Code</title><link>https://calyntro.com/blog/posts/2026-07-03-tests-dont-care-who-typed-the-code/</link><pubDate>Wed, 01 Jul 2026 09:00:00 +0200</pubDate><guid>https://calyntro.com/blog/posts/2026-07-03-tests-dont-care-who-typed-the-code/</guid><description>AI-generated code has the same failure modes as human code. But there&amp;#39;s a subtler trap: when one model writes the spec, the test, and the implementation, it can validate its own mistakes. Here&amp;#39;s how to break that loop.</description></item></channel></rss>