Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah) header
Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah) profile picture

Building Nextly (@nextlyhq). An open-source app framework for NextJS. Define your schema in code, or build it visually.

Pakistan
Joined August 2013
Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)Photo by Mobeen πŸ‡΅πŸ‡° (@mobeenabdullah)
We made it πŸŽ‰ Nextly (@nextlyhq) is officially in @vercel's Open Source Program, Spring 2026 cohort. A year of building, MIT licensed, now backed by the team behind Next.js itself. Thank you @amyegan and @vercel ❀️
1
2
174
What the hell is going on with Product Hunt? I spent months building my SaaS. Finally launched it today. 100+ followers. People commenting and upvoting. And Product Hunt keeps making the engagement disappear. Votes show up. Then gone. Comments too. 13 hours of this nonsense. Seriously, WTF? 🧡
7
1
1
5
317
Maybe there's a technical issue. Maybe some votes didn't qualify. Fine. Tell me. I'm not asking for special treatment or fake upvotes. I'm asking why engagement keeps appearing and disappearing. Is transparency really that difficult? Because right now, this whole experience has honestly killed my excitement about Product Hunt.
1
24
I built Rext AI with my team, and I'm proud of it regardless of what happens on Product Hunt. rext.ai But after today, I'm genuinely questioning whether I'll ever launch another product there. Other founders, tell me something. Is Product Hunt still a real launch platform in 2026? Or are we all wasting our time playing a game where we can't even see the rules?
26
Mobeen πŸ‡΅πŸ‡° retweeted
Andrej Karpathy just rewrote the rules of using LLMs: "Prompting is going away. Delete everything, keep Graph." He dropped his full 2-hour course from Stanford on "Graph-Native Research" β€’ 00:00 - Intro to Graph systems β€’ 01:08:09 - LLMs architecture This Karpathy course can replace a $100K Yale LLM senior degree. Start watching right now, then read article below
20
38
1
220
32,530
Mobeen πŸ‡΅πŸ‡° retweeted
Google just dropped a 1-hour course on full AI engineering: from 1 agent to Loops and Graphs 7:02 - Build your first agent 13:34 - What agents can do 23:08 - Context engineering 32:56 - Graph engineering 54:11 - Full autonomous system One agent saves you an hour. A thousand replaces the team. Watch it, then read the full guide on loops and graphs below
8
103
2
508
40,835
Mobeen πŸ‡΅πŸ‡° retweeted
Anthropic engineer: "At Anthropic we don't write prompts anymore. We build loops and graphs." In 30 minutes she shows how the Claude team builds systems that prompt themselves Prompts β†’ Agents β†’ Loops β†’ Graphs a prompt gets you one answer a loop gets the work done without you a graph decides which work runs at all if this cost $400 people would call it the best agents course of the year, and it is free watch it today then save the full graph engineering guide below before everyone catches up ↓
2
43
260
74,172
Mobeen πŸ‡΅πŸ‡° retweeted
πŸš€ We’re Hiring at Revnix! Looking for a Sales Development Representative (SDR) with 2–4 years of experience in prospecting, lead qualification, outbound sales, CRM management & booking discovery meetings. πŸ“© Apply: [email protected] #Hiring #SDR #SalesJobs #LeadGeneration
1
2
2
80
Happy Independence Day, Pakistan! πŸ‡΅πŸ‡° May we keep building, shipping, learning, and contributing to a stronger Pakistan. πŸ’š
31
Mobeen πŸ‡΅πŸ‡° retweeted
Just got my ticket for @nextjs Conf β€” claim yours! nextjs.org/conf/ticket/L687L…
1
13
Mobeen πŸ‡΅πŸ‡° retweeted
how to make your site readable by ai agents: 1. add an llms.txt so search tools stop guessing urls 2. check your server logs, not your analytics 3. serve a markdown version of every page 4. support content negotiation headers 5. rethink your JS-only widgets
74
54
20
1,136
180,517
90% of open source project mistakes happen here, and most builders spend zero time thinking about them: 1) when to stop adding features and just ship 2) write docs early enough that strangers can actually use it 3) build the content pipeline - I use Rext AI for this - before you need it
61
The longer you build in public, the more you need to: - Ship before it's perfect - Read other people's code - Talk to your users - Use Rext AI for content - Learn to say no to features - Write things down - Rest without guilt Anything you'd add?
46
I’m a Pakistan-based founder running Revnix, registered here as an SMC Pvt Ltd. Now I’m exploring a US LLC for two reasons: Better US/international business presence Easier client + SaaS payments through Stripe/Wise/etc. But the payment + tax structure is confusing. The main issue: I already have a Pakistani company, but some payments from platforms like Upwork/Toptal come under my personal name. Because of that, the money lands in my personal Wise/bank account instead of the Revnix company bank account. That creates problems with company accounting, PSEB/TechDestination, and the 0.25% IT export tax regime. What I’m trying to figure out: Should the clean flow be: Client/SaaS customer β†’ US LLC β†’ Revnix Pakistan business account With Revnix Pakistan invoicing the US LLC for software/IT services? Or is there a better way Pakistani founders are doing this? Also confused about the US side: Wyoming vs Delaware LLC? Wise Business vs Stripe vs Payoneer? Is Stripe realistic for a Pakistan-based founder with a US LLC? What replaced Mercury for Pakistani founders? Should the US LLC be owned by me personally or by Revnix Pakistan? I’m not looking for shortcuts. I want to set this up properly so client payments, SaaS revenue, Pakistan company accounting, PSEB/FBR, and US LLC compliance stay clean. Any Pakistan-based founders here who already solved this? Would love to learn from your experience.
52
I saw a GitHub issue once that stung a little. The user wasn't wrong. The docs were unclear, the API was confusing, and onboarding took too long. I could have gotten defensive. Instead I fixed the docs. Simplified the API. Rewrote the getting started guide. Then something shifted. Contributors showed up. Stars climbed. People started recommending it to others. Same project. Better execution. Did the project get easier? Or did the feedback just force me to actually care about the details? Long way of saying: criticism is just a list of things you can still improve. Not just for me. For any builder shipping in public.
48
I used to think shipping fast meant cutting corners. Now I build with more intention because that's what I focus on.
32