This is a bit of a different post for dev.to. Not a coding tutorial
exactly, more of a behind the scenes look at a small tool I shipped
recently.
I built checkmynumerology.com, a free name numerology calculator
that supports both Pythagorean and Chaldean systems. The whole
thing runs client side, no backend, no database, no user accounts.
Why Client Side Only
Numerology is personal. People are entering their full legal name
into this thing. The least I could do was make sure nothing leaves
their browser. All calculations happen in JavaScript on the client,
nothing is sent to any server, nothing is logged.
This also made the architecture dead simple. Static site, fast
load, no auth layer to maintain.
The Calculation Logic
Pythagorean is straightforward. Map each letter to a number
1 through 9 in alphabetical order, sum them, reduce to a single
digit unless you hit 11, 22, or 33 which are Master Numbers and
stay as is.
Chaldean is slightly more interesting because the mapping is
not alphabetical. Each letter has a value based on its sound
frequency, and 9 is never assigned to any letter. The reduction
logic is the same but you are working from a different lookup table.
I built both lookup tables and ran the same name through both
to make sure results matched established references before shipping.
Three Outputs Per Calculation
Expression Number: sum of all letters
Soul Urge Number: sum of vowels only
Personality Number: sum of consonants only
Each has its own interpretation copy which I wrote manually,
no AI slop, because the interpretations needed to be clear and
practical rather than vague and mystical.
What I Would Do Differently
Honestly the biggest lesson was on the content side. I underestimated
how much explaining the tool needs. People do not just want a number,
they want to understand what it means and why. The FAQ and explanation
sections took longer than the calculator itself.
The Site
If you want to poke around: checkmynumerology
It is free, no sign-up, open to anyone. Feedback welcome.
Top comments (1)
Great write-up on keeping the architecture simple and entirely client-side to respect user privacy with such personal data. It’s a great reminder that building the tool is often only half the battle—the real work lies in crafting the educational content and FAQs to guide the users!