---
title: "Responsibly mid-size: What Matters, Suffers"
description: "Moving into a mid-size company requires adopting processes and attitudes piecemeal rather than suddenly operating like a large enterprise, while preserving the ability to deliver customer value. The post challenges “clean code” as a universal standard, arguing from Sandi Metz’s discussion of churn and semantic complexity that important, frequently changed files are often large and complicated, making “bad code” an emergent feature of successful systems. It also uses Joel Spolsky’s case against rewrites to explain that ugly code may contain accumulated fixes for real bugs and operating conditions. The resulting advice is to distinguish code that manages responsibilities from code that does not, develop engineering judgment, and avoid letting aesthetic reactions damage collaboration, team cohesion, or delivery."
---

# Responsibly mid-size: What Matters, Suffers

[Ramp](https://yomu.fyi/company/ramp) · Pablo Meier · Mar 4, 2023

**Type:** Explainer

## Summary

Moving into a mid-size company requires adopting processes and attitudes piecemeal rather than suddenly operating like a large enterprise, while preserving the ability to deliver customer value. The post challenges “clean code” as a universal standard, arguing from Sandi Metz’s discussion of churn and semantic complexity that important, frequently changed files are often large and complicated, making “bad code” an emergent feature of successful systems. It also uses Joel Spolsky’s case against rewrites to explain that ugly code may contain accumulated fixes for real bugs and operating conditions. The resulting advice is to distinguish code that manages responsibilities from code that does not, develop engineering judgment, and avoid letting aesthetic reactions damage collaboration, team cohesion, or delivery.

## Context

Ramp has grown from its early days into a solidly mid-size company after raising substantial funding and hiring many people. The post frames responsible mid-size operation as a challenge: the company must change how it works without adopting large-company practices all at once, while maintaining team cohesion and customer-focused delivery.

## Approach / What changed

The post uses the Serenity Prayer as a framework for deciding which processes and attitudes to adopt. It examines “clean code” through Sandi Metz’s discussion of file churn and semantic complexity, cites Joel Spolsky’s argument against rewriting working systems, and draws on examples of accumulated bug fixes and compatibility behavior to argue for judging code by its responsibilities and results.

## Takeaways

- Plotting file churn against semantic complexity tends to reveal a small set of important files that are both frequently changed and complicated; this pattern appears across successful codebases.
- Ugly, old code may contain tested fixes for specific bugs, low-memory conditions, removable media, or old platform versions, so its apparent messiness can preserve behavior that is not immediately obvious.
- In a mid-size company, internal friction and loss of team alignment can threaten progress more directly than competitors; code-quality judgments should not obstruct collaboration or delivering customer value.

**Tags:** [Refactoring](https://yomu.fyi/topic/refactoring), [Testing](https://yomu.fyi/topic/testing)

- Source: [Ramp](https://builders.ramp.com/post/what-matters-suffers)
- Source URL: https://builders.ramp.com/post/what-matters-suffers
- Ingested by Yomu: 2026-09-01T01:33:44.316Z

[Read original post](https://builders.ramp.com/post/what-matters-suffers)