Nafees Nazik (@NFS__21) header
Nafees Nazik (@NFS__21) profile picture

Building @feeblohq | Open for opportunities DM

🇱🇰
Joined April 2020
Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)Photo by Nafees Nazik (@NFS__21)
Feeblo has only one user as of now, but not gonna stop for the love of the game. Back to work on adding more features and polishing the UX
1
27
Nafees Nazik retweeted
Introducing PayKit A billing and entitlement library built with Effect and @alchemy_run. You declare your features, plans and prices in one your code and paykit will handle the rest for you • Usage-based billing • Plans, features and entitlements • Stripe and Polar providers • Event-sourced billing ledger • BYO Database • Optional admin panel built with @foldkit repo link below 👇
2
1
4
159
Introducing PayKit A billing and entitlement library built with Effect and @alchemy_run. You declare your features, plans and prices in one your code and paykit will handle the rest for you • Usage-based billing • Plans, features and entitlements • Stripe and Polar providers • Event-sourced billing ledger • BYO Database • Optional admin panel built with @foldkit repo link below 👇
2
1
4
159
I've always wanted to build something from scratch and take it all the way to the end, with a good UX. After a lot of procrastination, it's finally ready and I'm excited to share it Meet feeblo.com 👋 An open-source, self-hosted alternative to Canny that helps you collect feedback, let users vote on ideas, and share your roadmap. built with @tanstack db and @EffectTS_ If you like it, drop a ⭐ on GitHub, it helps a ton 🙏
5
1
1
5
236
P.S. if anyone's looking for a mid-level engineer, I'd be happy to chat. I'm open to new opportunities! 🙏
44
Nafees Nazik retweeted
Replying to @NFS__21
nah i switched over to blacksmith ages ago, but i just spent the entire day working with AI and optimizing it. i also spent a lot of time refactoring parts of the codebase. here's a massive list of what we did if you'd like to throw your agent at it :) --- Running less A pull request runs only the tests and jobs its change reaches. Test files whose inputs already passed are skipped. A change to CI's own files runs only the jobs it touches. The service builds and tests only when its Rust inputs change. A pull request reuses the service checks main already passed. Merges record a pass instead of running CI again. Merges check types only, with no pack or tests. A PR packs only when it changes what gets packed. The heavy checks run once a day, in the sweep before the release. The deep property tests run only in the daily sweep. Recording workflows and lint-only changes no longer run every test. Each review no longer starts a full CI run. Running faster Test shards are sized by measured time, not file count. Shards that finish early take files from the busy ones. The slowest test files were split. Long waits in tests were cut short. Workers in server tests start in half the time. Dependencies and the Rust toolchain load from a cached disk. Vitest's cache is kept between shards. Jobs that wait on each other were shortened. Setup now runs in parallel with the work it waits for. Format, lint and types got their own job and a bigger runner. A duplicate debug Rust test step was removed. The machine proof waits for real events, not fixed sleeps. Machine sizes Small runs moved to cheaper machines, and heavy ones to bigger machines where that bills less. Flakes CI files an issue for each flaky test and closes it once measured fixed. A batch of flaky tests was fixed. Watching cost Each job has a time budget, and a daily health report flags overruns. A spend watcher stops CI at the monthly cap. The docs agents load have a size budget. Local runs out Pip's checks moved to CI and the local runs were deleted. The checks run as test people moved to CI. Recording lanes use the released CLI. Releases and deploys Production deploys only from a checked release. The release gate now really blocks. Still going: splitting the model-check tests into smaller files
1
1
73
Finally it’s here 🚀🚀
Effect v4 is here. One ecosystem. Zero dependencies. The next chapter of Effect and the foundation for building reliable software and AI agents in TypeScript.
84
Nafees Nazik retweeted
your "stack" still matters, maybe it won't matter as much in the future (soon even) but it matters today these stupid fuckin robots don't make good initial decisions ratstack.sh/
12
16
2
240
10,869
Crazy to think a $13 billion company is basically using a Hugging Face emoji as its logo 🤗
61
🚨🇲🇦 Manchester City are confident to get deal done for Ayyoub Bouaddi in the next days. Negotiations are accelerating as reported on Monday and #MCFC increasingly optimistic. 🩵 Bouaddi to join now or in 2027 could also depends on exits, including Rodri situation.
1,285
3,515
975
62,569
6,627,672
I'm a simple man. I check my CodexBar to see my usage, and OpenAI has already reset it again 🙏
114
“use auth”
Better Auth is joining Vercel! From the very beginning, this team has been my biggest inspiration and has always reflected many of the reasons I started working on Better Auth. I’m incredibly grateful to our community, our team, our investors - in particular @koomen and @arnavsahu341 from @peakxvpartners for believing in my vision and taking a chance on me. And thank you everyone @vercel that made this happen - I'm excited to to be building together!! I’ve shared some thoughts on the blog post linked Excited for what’s ahead ❤️ better-auth.com/blog/better-…
1
173
F**king greatest player ever to play this game
72
Self DDoSed my Cloudflare Workers just because I missed an asterisk in my worker routes 😭
83
/review + Kimi 2.6 has become muscle memory at this point. OpenCode Go is an absolute bang for the buck.
2
79
Helpful tip if you’re using effect on your codebase, agents very good at it
We on the @EffectTS_ team we often recommend cloning the Effect repo into your project so your agent can explore the source directly. I finally wrote up why it works and how to set it up: effect.website/blog/the-one-…
68
First not last
The Google Threat Intelligence Group has detected the first known instance of a threat actor using an AI-developed zero-day exploit in the wild. While the attackers planned a wide-scale strike, our proactive counter-discovery may have prevented that from happening. This finding is part of our new report on AI-powered threats.
53
If your team relies on Github Actions, take a few minutes to read this. Given the recent supply chain attacks, this article does a great job breaking down the risks, what actually happened, and the practical steps teams should take to secure their CI/CD pipelines.
1
105