Ugh, this is embarrassing (but here's what I learned) 👋 #191492
Closed
anshmajumdar121
started this conversation in
A Welcome to GitHub
Replies: 1 comment
-
|
👋 Thanks for being part of our community! We noticed you've already created an introduction in the A Welcome to GitHub category. We only allow one introduction per person in this category (including closed ones). If you have questions or would like to start a new conversation, please navigate to another category. This discussion has been closed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, I'm Ansh. I build things that live in terminals. And I almost lost one of them because I forgot the most basic rule in dev.
So here's the thing: I've been diving deep into C++, Python, and JavaScript, messing around with MongoDB, Firebase, SQL—trying to understand how real systems actually scale, not just how to make them compile. I wanted to build something that felt alive, not just another todo app.
So I made TermiPet 🐾
A tiny virtual pet that lives in your terminal. It hatches uniquely for you, reacts to your keystrokes, gets happy when you code, worried when you idle. Fully themeable. Event-driven. No GUI fluff—just pure system-thinking in a shell.
✨ I was proud of it.
✨ I wrote the docs.
✨ I even deployed a live demo.
But here's where I messed up.
I was so focused on making the product feel real, I treated the code like it was disposable.
I kept iterating locally. "I'll push to GitHub once it's polished," I told myself.
"I'll add tests, then README, then then I'll share it."
Sound familiar?
Then my laptop decided to update at 3 AM.
Not a dramatic NVME funeral like some horror stories—just a silent, corrupted git folder and a npm install that suddenly couldn't find half its dependencies.
I panicked. Checked backups. Realized: I never pushed the latest branch.
The deterministic hatching logic? The event reactor? The theming engine?
All sitting in a local folder that now felt very, very fragile.
I spent the next 6 hours reconstructing commits from memory and terminal history.
It worked—but barely. And the stress wasn't worth it.
So I pushed everything.
✅ https://github.com/anshmajumdar121/termipet
✅ https://anshmajumdar121.github.io/termipet/
And now I'm sharing it with you—not because it's perfect, but because it's real.
I'm brand new to GitHub. I want to move from "building projects" to "building systems people actually use." I want to collaborate, contribute to open source, and learn how to solve real problems with code.
So here's my ask:
🐣 Does the pet concept feel fun or gimmicky?
⚡ Are the event-driven reactions useful or over-engineered?
🎨 Is the theming system intuitive?
🐛 Did you find a bug? (Please tell me.)
Even a "meh, not for me" helps. I'm still learning.
Beta Was this translation helpful? Give feedback.
All reactions