Software component names should be whimsical and cryptic

Re:Software component names should be whimsical and cryptic by bayindirh on Tuesday September 13, 2022 @06:31AM (#32822523)

I opt to compromise and use middle ground name, which both related and fun.

A tool for sending mails via Mailgun? “Railgun” then, for example.

[ Parent | on HN ]

Re:Software component names should be whimsical and cryptic by bckr on Tuesday September 13, 2022 @06:57AM (#32822692)

This is my stance. 2 words: Memorable Use.

Banana Cache

Hadouken Security Service

Lightfoot Containers

I mean, this is pretty much the AWS formula.

[ Parent | on HN ]

Re:Software component names should be whimsical and cryptic by bayindirh on Tuesday September 13, 2022 @07:45AM (#32823044)

For bigger services, it makes sense. For smaller utilities single word names are better IMHO.

I'll keep this formula in mind too, and use it when I develop something bigger.

[ Parent | on HN ]

Re:Software component names should be whimsical and cryptic by tetha on Tuesday September 13, 2022 @12:45PM (#32826750)

This is the right middle ground imo as well. It adds a bit of simple difference between the 15 different exporters, without being too far off. We have things like the "Tenant Saw" - extracts a tenant from a multi tenant system, or a foosystem-butler called Vlad - automating and scripting a bunch of busywork around the foosystem.

[ Parent | on HN ]