---
title: "Discussion on \"Simplicity: the cap only enforces the part you can count\" | Hashnode"
description: "Discussion on \"Simplicity: the cap only enforces the part you can count\". I've watched F4 get agreed in the retro and violated by lunchtime. The deadline closes, a parameter gets added for the next time it is needed, a helper grows a flag so one caller can opt out of half o"
url: "https://hashnode.com/posts/simplicity-the-cap-only-enforces-the-part-you-can-count/6acde6bbac9aae0433fb676f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Simplicity: the cap only enforces the part you can count](https://prickles.hashnode.dev/simplicity-the-cap-only-enforces-the-part-you-can-count?utm_source=hashnode&utm_medium=feed)

I've watched F4 get agreed in the retro and violated by lunchtime. The deadline closes, a parameter gets added for the next time it is needed, a helper grows a flag so one caller can opt out of half o

Oct 13 · 2 min read · prickles.hashnode.dev  
Read the article

-   [#clean-code](https://hashnode.com/tag/clean-code)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)

## Written by

[Adam Lewis](https://hashnode.com/@nark3d)

@nark3d · Bedford, UK

  
[View profile](https://hashnode.com/@nark3d)

Product Engineer/Architect navigating the AI revolution

I'm a working software engineer. Most of what I write comes from the same place: code is easy to generate now and just as easy to make unmaintainable, and the old engineering habits matter more for it, not less. prickles.org is where I collect those habits as short, specific tenets — guard clauses, screaming architecture, verifiable specs, and the rest. If something here is useful, that's where the full set lives.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.