<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering Culture on Martin C. Richards</title>
    <link>//www.martinrichards.me/tags/engineering-culture/</link>
    <description>Recent content in Engineering Culture on Martin C. Richards</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 30 Apr 2026 07:25:31 +0200</lastBuildDate>
    <atom:link href="//www.martinrichards.me/tags/engineering-culture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Are we microservice yet? More services than people.</title>
      <link>//www.martinrichards.me/post/are_we_microservice_yet/</link>
      <pubDate>Thu, 30 Apr 2026 07:25:31 +0200</pubDate>
      <guid>//www.martinrichards.me/post/are_we_microservice_yet/</guid>
      <description>&lt;h1 id=&#34;are-we-microservice-yet-more-services-than-people&#34;&gt;Are we microservice yet? More services than people.&lt;/h1&gt;&#xA;&lt;p&gt;The number of services in your system is not the flex you think it is.&lt;/p&gt;&#xA;&lt;p&gt;A recent Wise post flexing about how they have over 1000 services and 950 engineers triggered a pet peeve about how teams treat service count as some sort of badge of how well they are doing microservices. Like that is the goal in and of itself and not a tool to decompose problems around the people you have.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
