Look At This Marvel:
<img src="https://media.daily.dev/image/upload/s--uTV7_kxt--/f_auto/v1758808649/ugc/content_9044e6e9-bda5-4d2e-ae4b-86bbd3e6264c?_a=BAMAK+ZW0" alt="1000079881">
With this you will never have to <code>import type { ButtonProps } from './Button'</code> ever again! Just <code>import { Button } from './Button'</code> and voila! Component <code>&lt;Button /&gt;</code> and Props <code>Button.Props</code> are right there.
Isn’t it smart?
…
Well yes it is and that is exactly the problem!
You see, in software development SMART usually means COMPLICATED and if i have learned anything over the years it is that COMPLICATED means BAD.
And this code is smart and complicated for so many reasons!!
1. You Hardly Ever Import Props Directly
Seriously, how often do you actually need to import the props from outside the component file? Maybe twice a year? Forcing every file to bend to this “smart” import logic is like carrying an umbrella every day because it once rained in 2017.
2. Every Developer And Their Mum Will Ask “Why?”
Yeah, it’s clever. For about 5 minutes. Then you realize nobody will remember two months from now why the Button has a mysterious namespace. “Props” isn’t just a type anymore, it’s an easter egg with a riddle.
3. Weird Edge Cases
Have you tried assigning namespaces to an object?
<img src="https://media.daily.dev/image/upload/s--r0o-Z7Jt--/f_auto/v1758813821/ugc/content_e44a7db1-4e47-44c6-a961-1f12d4f3f2c2?_a=BAMAK+ZW0" alt="1000079895">
Well lets keep this short, it doesn’t work. So when you ever run into this, you will have to solve this in an even more complicated way… Congrats!
4. Even LLMs don’t get it
As this code is unusual LLMs will not get it and will definitely not start writing it themselves unless you add a rule for it. Just like devs, LLMs work better with what’s idiomatic. (Idiomatic means: Writing code the way locals would—not like a tourist with a guidebook.)
<hr>
As Grug once said “complexity very, very bad”
The truth is, the best devs don’t add complexity, they remove it. Being able to write smart code, but then not doing it. That is true wisdom. With smart code you will get: More bugs, more questions, more dependence, more confusion, more time spent reading code and more time spent explaining your idiocy to LLMs…
Let my pain be your warning! Do yourself a favor and write your Props the boring way. In fact, write all your code the boring way. Your future self will thank you!

Smiley Face

Fabian Letsch

A developer argues against overly clever code patterns, using a TypeScript namespace trick for component props as an example. The post explains why 'smart' code that combines component exports with prop types creates unnecessary complexity, confuses team members, breaks in edge cases, and makes code harder to maintain. The author advocates for writing boring, idiomatic code that prioritizes clarity and maintainability over cleverness.

Being "Smart" Is Painfull

Based. Come back two months later and the code looks so obscure. Then you remember that it is YOU who wrote it. When you wrote it, it was a masterpiece. Now it is a liability

coming back to your old, trash code months later:
<img src="https://media.daily.dev/image/upload/s--XyJeNQis--/f_auto/v1759591302/ugc/content_87c1d987-a726-4c09-bafb-fcf0f6f30ed3?_a=BAMAK+ZW0" alt="image">

The irony of misspelling painful in the title of this post is not lost on me.