News for hackers. Stuff that matters.
Re:Three Constraints Before I Build Anything by csallen on Sunday April 26, 2026 @09:50PM (#47916860)
> One defining constraint must shape the product... Minecraft is built entirely from blocks. IKEA is flat-pack, self-assembly furniture.

I've been calling these things product primitives. I can't remember where I heard that term, but it refers to things like...

Blocks in Notion. Messages and conversations in Telegram. Frames and layers in Figma. Tweets in Twitter. Cells and sheets in Excel. Tools and layers in Photoshop. Commands in a CLI.

I think what makes for good product design is having a very small number of primitives. A bad product doesn't know what its primitives are. Or it has a very large number of primitives. It feels like everything in the product is some unique thing that works in its own unique way. So users have to learn a ton of different top-level primitives/concepts. It's confusing and intimidating and hard to teach. Ideally you just want one or two or three main primitives.

The complexity/power in an app comes from choosing powerful primitives that have depth, that are composable, etc. You can do a lot with Notion blocks. You can do a lot with Excel cells. You can do a lot with a CLI command. You can do a lot with a Minecraft block. There's depth there.

Re:Three Constraints Before I Build Anything by argee on Sunday April 26, 2026 @10:12PM (#47916998)
I think this philosophy might be oversimplified. Tana has basically two primitives (bullets and supertags) and manages to be devastatingly complex to use to the point you have to watch hours of tutorials to do very simple things. Conversely Google Maps has a lot of “primitives” but the UX is fairly tight for 90% of use cases.
Re:Three Constraints Before I Build Anything by whh on Sunday April 26, 2026 @11:36PM (#47917465)
Vaguely feels like "Atomic Design" but applied to engineering.
Re:Three Constraints Before I Build Anything by rgbrgb on Sunday April 26, 2026 @11:55PM (#47917556)
what is Tana?
Re:Three Constraints Before I Build Anything by mkl on Monday April 27, 2026 @01:31AM (#47918025)
This I think: https://tana.inc/

Seems like there's quite a bit more to it: https://outliner.tana.inc/learn

Re:Three Constraints Before I Build Anything by ffsm8 on Monday April 27, 2026 @01:45AM (#47918110)
Doesn't Jira only have one primitive: the ticket. Everything else just augments it. You could say that these augmentations are separate primitives, but then the same would apply to all tools in the other cited examples like Photoshop too
Re:Three Constraints Before I Build Anything by unholiness on Monday April 27, 2026 @08:56AM (#47920986)
It applies more to design software, where a user is creating durable things and needs to understand those things themselves. Google Maps is more of an agent: It's responsible for understanding its own complexity and answering your queries.
Re:Three Constraints Before I Build Anything by argee on Monday April 27, 2026 @01:57PM (#47924972)
My point is that, sometimes, going for the lowest common denominator or "noun" and declaring it to be your primitive (focusing on minimalism), is a worse approach than picking a larger set of primitives that suits your design. Take Hangul (한글) for example, where the primitives are designed to serve a goal, and there's no effort to "ruthlessly" minimize the number of primitives, and this is something you can learn to read in 10 minutes, or at least in a day. Whereas if you go over to something like Chinese, your numbers 1, 2, and 3 look nice thanks to your stroke primitive, but your needs quickly overwhelm your design and you end up with something quite unwieldy compared to if you had picked a more complex set of primitives — you will never learn to read all Chinese in your whole life even as a native speaker. It's a counter-intuitive design lesson.
Re:Three Constraints Before I Build Anything by evnc on Monday April 27, 2026 @11:19AM (#47922809)
Tana is basically a programming environment disguised as a text editor (in this way, it follows in the grand tradition of emacs you could say)
Re:Three Constraints Before I Build Anything by azhenley on Monday April 27, 2026 @01:12AM (#47917910)
We used to call this “concept count”. You usually want to minimize the number of core concepts that make up your product. I’ve also heard it as the “nouns and verbs” of a product.
Re:Three Constraints Before I Build Anything by lioeters on Monday April 27, 2026 @05:44PM (#47927765)
> the “nouns and verbs” of a product

Insightful, to think of a product and its interface as a "language" that the user learns. Some products give you a small and powerful vocabulary, where just a few words can accomplish a lot. Other products are like a badly designed language that lacks coherence and ease of use, where tasks that should be simple require many words, or some words don't fit together well with others.

Re:Three Constraints Before I Build Anything by boris on Monday April 27, 2026 @02:24AM (#47918330)
> Commands in a CLI … I think what makes for good product design is having a very small number of primitives.

Small but not too small. Case in point: shell scripts (POSIX shell, bash) where the scripting part was decided to be modelled as commands thus not introducing another bunch of concepts. We all know what the result is (hot, slow mess).

Re:Three Constraints Before I Build Anything by dhamidi on Monday April 27, 2026 @06:38AM (#47919863)
I know it's in vogue to bash Bash but I feel that criticism is unfair.

Shell scripting is a victim of its own success: it is _so easy_ to get started that most users get value out of knowing the first one percent and never bother to actually learn the rest.

There aren't many who have read the Bash manual, or know what zsh can do that Bash cannot, etc.

"Shell scripting is a hot, slow mess" is the same hot slow mess that you get wherever the barrier to entry is extremely low (e.g. early PHP, early JavaScript/frontend development, game development with a game engine where you can just click around in the editor, etc).

Re:Three Constraints Before I Build Anything by skydhash on Monday April 27, 2026 @07:46AM (#47920338)
There’s also the fact that shell scripting is for automation of what you may do interactively. It’s not for stuff where you want data structures to manipulate in memory. Trying to use it like python is an exercise in frustration.
Re:Three Constraints Before I Build Anything by jamesfinlayson on Monday April 27, 2026 @09:39PM (#47929559)
I remember a friend saying they had a university assignment to implement something like a spreadsheet program in bash - I suppose it was to teach them the intricacies of bash but the big takeaway was meant to be - don't use bash for anything too complicated.
Re:Three Constraints Before I Build Anything by noufalibrahim on Monday April 27, 2026 @04:48AM (#47919193)
I used a similar metric when judging programming languages. The language can get huge but if it's conceptually small, one can learn it and then leave the rest to compounding due to experience. Conceptually large languages had a barrier for me. The case when I felt this was perl.
Re:Three Constraints Before I Build Anything by gzread on Monday April 27, 2026 @09:31AM (#47921340)
When I think about products with too many primitives, I instantly think of Snapchat and Instagram - my two least favorite apps.
Re:Three Constraints Before I Build Anything by gavmor on Monday April 27, 2026 @11:39AM (#47923050)
Yeah... this sounds a bit like the Alexandrian Pattern Language concepts which directly inspired the Gang of Four's Design Patterns.

I wonder, though, if what you're describing as "product primitives" actually maps more closely to what Alexander later called "Centers," rather than the patterns themselves.

From what I understand, while the software world heavily adopted his patterns, Alexander spent his later career arguing that the ultimate building block of a system is actually a Center: localized focal points of utility and coherence, eg a well-lit courtyard, window seat, or fireplace. A strong center is naturally composable; it "resolves local tension," is made of smaller centers, and acts as a building block to generate larger ones.

When a product feels confusing or bloated, it's rarely out of bad design intent. It's just that user needs—while not necessarily glaringly—are empirically discoverable, while the true, underlying "centers" that could elegantly solve them are incredibly subtle and hard to identify. The path of least resistance is almost always to just build a unique, rigid interface for the immediate user need right in front of you. Doing the deep architectural work to discover a core primitive that naturally absorbs those needs is difficult.

So maybe that's why we build so many faster horses.