<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gregor Hohpe on Blog</title><link>https://blog.djvelimir.com/tags/gregor-hohpe/</link><description>Recent content in Gregor Hohpe on Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 12 Oct 2026 18:08:57 +0200</lastBuildDate><atom:link href="https://blog.djvelimir.com/tags/gregor-hohpe/index.xml" rel="self" type="application/rss+xml"/><item><title>Thinking Like an Architect</title><link>https://blog.djvelimir.com/post/conferences/thinking-like-an-architect---gregor-hohpe---ndc-london-2025/</link><pubDate>Mon, 12 Oct 2026 18:08:57 +0200</pubDate><guid>https://blog.djvelimir.com/post/conferences/thinking-like-an-architect---gregor-hohpe---ndc-london-2025/</guid><description>&lt;p&gt;Are architects supposed to be the smartest people on the team, making all the important decisions for developers to fill in the blanks? Certainly not.&lt;/p&gt;
&lt;p&gt;Rather, architects make everyone else smarter, for example by sharing decision models or revealing blind spots. Architects also communicate across many organizational layers by using models and metaphors. This talk reflects on two decades working as an architect, ranging from the executive penthouse to the serverless engine room.&lt;/p&gt;</description></item></channel></rss>