
engineering @hydra_db · go/rust engineer · fucking around and finding out
anywhere in the world
Joined May 2025
- Tweets10.4K
- Following581
- Followers1.7K
- Likes33.5K
finally a maintainer for github.com/hydra-db/hydradb 😍
good morning. we went for a random ride today and ended up trekking our way to a lake in the middle of the hills
then i drove a scooty for the first time (thanks to @stevenstank775 and @Divyummyy)
goodnight chat
(these guys will post good pictures hopefully)
aditya. retweeted
This is peakk
TrenTorch.com
aditya. retweeted
There's no reason not to FAFO in tech.
You now have an all-knowing intelligence assistant now; what's stopping you from becoming the best version of yourself?
Just pick something hard & learn it.
Trust me you won't regret it.
aditya. retweeted
built SaaT (saat, turkish for time)
implemented 11 distributed clock algorithms from scratch in Go. zero frameworks.
from physical wallclocks to lamport clocks and vector clocks, covering google's truetime, interval tree clocks, and HLC. compared tradeoffs and how they resolve conflicts
also built a network simulator with jitter to audit causality and test concurrent edge cases across them
[ link : github.com/dexisback/Saat ]
can someone help my guy out please
my Founders Directory deployments got paused
turns out, i might actually be in hell💀
tldr-
324 MILLION Firestore read requests
₹18,330 in charges
all this on October 15 alone 😭
not because I had thousands of users.
but because 61 visitors generated over 3k pageviews.
first thought? maybe i deployed too many changes using my Codex-driven changes
but the insights were even more unexpected
here's what the analytics showed:
- 3,819 pageviews from just 61 visitors in just 2 days
- 759 pageviews in a single hour
- almost all suspicious traffic had no referrer
- 5 US Chrome Mobile visitors generated ~1,973 pageviews in one day
- 324 MILLION Firestore read requests
- ₹18,330 in Firestore charges
imagine paying ₹19K.
for a side project.
Vercel flagged excessive Fluid Active CPU usage and paused my deployment.
so i started investigating.
i checked my Codex chat history. it had accessed production only a handful of times. most of the QA was done on local servers.
nowhere close to thousands of requests.
the traffic looked more like an automated browser, scraper, testing agent, or a reload loop running JavaScript with an Android user agent.
could be a bot, scraper, automated browser, or some kind of reload loop. still investigating the exact source.
but 324 million database reads?
not normal human traffic.
"at the end of the day, life is all about embracing its uncertainty, and once you learn to love it, the game is all yours"
i do be saying sum tuff shit at times 🥀
Replying to @depak_7
as much as id love to, all it is is to farm clicks and views on here, but again, everyone's path and journey is different
in the time we live in, and this ai era that we're in right now (god bless), there's really no "one size fits all" kinda thing which people get into cs for in the first place. it just isnt the same anymore. you can't just do everything a "roadmap" tells you to and expect to land a 50LPA job after 6 months
at the end of the day, life is all about embracing its uncertainty, and once you learn to love it, the game is all yours :)












