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)
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
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
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
🚨🇲🇦 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
Nafees Nazik retweeted
Let me also take this opportunity with Preact being a hot-topic now that I write about Preact topics on my blog! If you want to know more about the new diffing algorithm, you can look at the source code and read a few of my articles!
2
4
19
1,965
Nafees Nazik retweeted
this blog post is full of practical tips on Postgres: What I Wish Someone Told Me About Postgres
3
66
2
787
59,477
Nafees Nazik retweeted
If you're on 🦋 but having a hard time finding your people over there, I made a quick little thing to help. You can export your GitHub and/or Twitter follows to a file, and then in a localhost app, automate searching & following of your social rolodex github.com/lukeed/bluesky-im…
3
10
1
101
13,178
Nafees Nazik retweeted
Ryan just keeps delivering, a repo of cool preact patterns! Go checkout some patterns for blogs (and pre-rendering)
As promised, here's a simpler demo of the ideas used for the Preact docs site: github.com/rschristian/preac… I tried to document most of it in the readme, let me know if anything's unclear or if you have questions. I'd like to get a solid repo of reference projects up for Preact.
1
2
10
2,071
Nafees Nazik retweeted
If you're not doing over a million dollars in ARR for your SaaS app, you almost certainly don't need more than a single server. Chasing a 99.99% uptime in those early days by prematurely optimizing your resilience is a vast of effort that could have fueled features and bug fixes.
95
268
85
3,469
349,224
Nafees Nazik retweeted
my toxic trait is that I think I can code it in a week
100
536
89
3,201
165,375
Nafees Nazik retweeted
We are making fundraising easier with standard @ycombinator Post-money and pre-money SAFE at @captableinc, you can also upload your custom agreement.
2
8
431
Nafees Nazik retweeted
✋🏼 we are actively building an open-source Captable successor, and would love to get some feedback from the community @captableinc
Replying to @JosephJacks_
Someone should make an open source version of Carta that allows anyone to really easily manage their cap table
3
11
972
How do I create a single component that fetches it's own data across React server and React client? Conditional exports?
2
2
4
870
Nafees Nazik retweeted
Easy mistake, let’s all learn from it. Treat your server action arguments the same as a payload in a post api request: untrusted. Data such as a userId should only come from some type of getSession call inside your action. If you’re doing some type of admin dashbaord and need to apply operations to individual users, that’s when it’s fine to pass in a userId, but you’ll still need to get the session and verify the user invoking your action has permissions to modify that passed in userId.
I just realized I was planting a colossal security breach into my React Server Components. This is the first time I have used them extensively, and I didn't fully realize that I can't trust arguments.
9
11
1
103
29,135
At @documenso we recently integrated Kysely on top of @prisma so we can migrate our nasty raw queries to a type-safe alternative. Can't wait to use this to tackle some of our more complex queries within the app where Prisma's querying language isn't 100% suitable!
9
5
50
6,884