<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>It-Architecture on McAviti's Blog</title><link>https://www.mcaviti.net/en/categories/it-architecture/</link><description>Recent content in It-Architecture on McAviti's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Klemens Dickbauer</copyright><lastBuildDate>Wed, 26 Nov 2025 00:14:00 +0000</lastBuildDate><atom:link href="https://www.mcaviti.net/en/categories/it-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Read: Surviving Strategy &amp; Architecture, by Michael D. Stark</title><link>https://www.mcaviti.net/en/read-surviving-strategy-and-architecture-by-michael-stark/</link><pubDate>Wed, 26 Nov 2025 00:14:00 +0000</pubDate><guid>https://www.mcaviti.net/en/read-surviving-strategy-and-architecture-by-michael-stark/</guid><description>
IT and IT architecture is a volatile and often stress-inducing field. &amp;ldquo;Keep calm and baldly go where no enterprise architect has gone before&amp;rdquo; is a proper mission statement. But maybe ancient Asian philosophy is even more helpful.</description></item></channel></rss>