Ofline
As a daily life of Developer we often spend mainly our time with Vs Code, Terminal, and other stuffs i.e. mostly with terminal and as i notice , one small thing kept happening repeatedly:
Someone would ask:
And then the usual flow would begin:
It doesn’t sound like a big issue.
But over time, it felt wrong.
It was the interruption.
As a developers, we live inside the terminal:
Now imagine breaking that flow just to check something as simple as a date.
It’s not the time it takes.
It’s the fact that you had to leave your environment.
That was my first thought too.
But quickly, it doesn’t solve the actual problem.
The default date command:
So the “quick check” is no longer quick.
You still end up leaving the terminal.
I didn’t start with the idea of building a tool.
I started with a frustration:
“Why do I need to leave my terminal for something this small?”
That’s how NEPKAL was born—a simple CLI tool for Nepali date.
That’s it.
No browser.
No tab switching.
No context loss.
NO internet required
Just instant output inside the workflow.
NEPKAL is not about calendars.
It’s about small friction in developer workflows.
We usually focus on big things:
But ignore the tiny interruptions that happen dozens of times a day.
One browser switch doesn’t matter.
But ten of them do.
Honestly—not for everyone.
If you don’t work with Nepali dates, you’ll never need it.
But if you do, it removes a very small but constant annoyance from your daily flow.
And sometimes, that’s enough reason to build something.
Most developer tools don’t exist because something is impossible.
They exist because something is slightly annoying, repeated often enough, and simple enough to fix.
NEPKAL came from exactly that kind of annoyance.
Someone would ask:
“What’s the Nepali date today?”And then the usual flow would begin:
someone pauses what they’re doing think
often opens a browser and searches for Hamro Patro
checks the date
comes back to the terminal or wherever they are like vs code, IDE or something
It doesn’t sound like a big issue.
But over time, it felt wrong.
It was the interruption.
As a developers, we live inside the terminal:
- logs running
- services restarting
- APIs being debugged
- Constant context in the command line
Now imagine breaking that flow just to check something as simple as a date.
It’s not the time it takes.
It’s the fact that you had to leave your environment.
That was my first thought too.
But quickly, it doesn’t solve the actual problem.
The default date command:
- only gives Gregorian calendar
- doesn’t support Nepali (Bikram Sambat) dates
- doesn’t fit into a Nepali developer workflow
So the “quick check” is no longer quick.
You still end up leaving the terminal.
I didn’t start with the idea of building a tool.
I started with a frustration:
“Why do I need to leave my terminal for something this small?”
That’s how NEPKAL was born—a simple CLI tool for Nepali date.
That’s it.
No browser.
No tab switching.
No context loss.
NO internet required
Just instant output inside the workflow.
NEPKAL is not about calendars.
It’s about small friction in developer workflows.
We usually focus on big things:
- system design
- performance
- scalability
But ignore the tiny interruptions that happen dozens of times a day.
One browser switch doesn’t matter.
But ten of them do.
Honestly—not for everyone.
If you don’t work with Nepali dates, you’ll never need it.
But if you do, it removes a very small but constant annoyance from your daily flow.
And sometimes, that’s enough reason to build something.
Most developer tools don’t exist because something is impossible.
They exist because something is slightly annoying, repeated often enough, and simple enough to fix.
NEPKAL came from exactly that kind of annoyance.