You Have to Feel It

Mitchell Hashimoto News

Summary

A reflective essay emphasizing that beyond meeting specifications and delivering demos, great software must evoke the right feeling in its users—a quality that cannot be measured by checkboxes alone.

No content available
Original Article
View Cached Full Text

Cached at: 05/16/26, 03:39 AM

# You Have to Feel It Source: [https://mitchellh.com/writing/feel-it](https://mitchellh.com/writing/feel-it) You see a series of checkboxes checked\. Schedules met\. Requirements satisfied\. Demos delivered\. It's a good day\. Good job, you, good job\! A promotion is in sight\. But you didn't feel it\.*You didn't feel it\.* We, as people, feel something with every interaction\. Frustration, joy, relief, confidence\. A feeling\. A person interacts with our work\. Our work evokes a feeling\. The feeling matters\. The feeling is part of the work\. The*desired feeling*is part of the requirements\. When you feel it, you know\. The feature makes you smile when you use it\. It fits right in, like it was always meant to be there\. You want to use it again\. You want to tell people about it\. This is the difference\. This is what metrics, specifications, and demos miss\. They don't capture the feeling\. For the people who will use and live in the work, the feeling is part of their daily experience\. Which means you can't stop at checking the boxes on paper\. You have to sit with it, use it, live with it\. You have to feel it\.

Similar Articles

Some Things Just Take Time

Armin Ronacher

A reflective essay arguing that genuine success in software and business requires tenacity and patience, not just speed, and warns that the obsession with instant gratification undermines trust and long-term value.

Stop trying to engineer your way out of listening to people

Hacker News Top

An essay arguing that software engineers and product designers often avoid genuine user listening by over-engineering frameworks and systems, instead outlining seven common pitfalls that prevent effective listening to users and stakeholders.

The essence of architectural work - Part 3

Lobsters Hottest

This article continues a series on the essence of architectural work, introducing three facets of its purpose: economic, cognitive, and humane. It begins exploring the economic purpose, discussing quality attributes and their role in software architecture.

The inevitable weakness of metrics

MIT Technology Review

A reflective essay on the pitfalls of self-quantification, arguing that while metrics can reveal useful information, they often obscure or corrupt deeper self-knowledge.