Sabitlenmiş Tweet
CodeBucks⚡
1.2K posts

CodeBucks⚡
@code_bucks
35K+ YouTube subs | Software Engineer who ships AI apps | Scaling AI first development Agency | DM for AI SaaS development
Katılım Eylül 2020
173 Takip Edilen886 Takipçiler

agree, you need to model both.
My point is just that cheaper tokens don't automatically mean more demand. In a lot of workflows, demand only really opens up when the model is good enough that humans don't have to keep fixing the output.
Until then, cheaper tokens mostly just make bad or messy outputs cheaper.
English

@code_bucks I’d argue you should be doing both to model both supply side and demand side if you’re uncertain what the path function of constraints and tipping points will be.
English

If you are on the buyside and your PM or CIO insists AI is a bubble you should do everything in your power to find a new seat.
How deeply you understand bottlenecks and tokenomics will be the primary driver of alpha over the next five years and you should put yourself in a position where you have the leash to be involved and learning instead of watching from the sidelines.
We are at the starting line. The people pointing to memory stocks instead of model IQ tipping points simply lack the IQ or imagination to understand that.
English

No it's not, the DX is way better in supabase, and appwrite charges a lot just for image transformations, plus their interface is very slow. Seriously, check their pricing. For now, it's smarter to just use a postgres DB from neonDB for your MVP, then switch to planetScale when your app grows.
English

@heynavtoor Replace Supabase by Appwrite, it’s miles better and open source too, has more features too
English

Here are 10 GitHub repos that quietly print money while you sleep.
1. Cal. com
Open-source Calendly. Fork it, white-label it, sell to dentists and lawyers for $200/month. The founders hit $5M ARR in 3 years doing exactly this.
Repo → github.com/calcom/cal.com
2. Plausible Analytics
Privacy-first Google Analytics. Self-host it, resell to agencies for $50/month per client. Two founders bootstrapped this to 7 figures.
Repo → github.com/plausible/anal…
3. Ghost
Open-source Substack with 100% margin. 1,000 readers at $5/month equals $60,000 a year. Forever.
Repo → github.com/TryGhost/Ghost
4. n8n
Open-source Zapier. Sell automation services for $500-$2,000 per setup. n8n raised $14M because the agency model behind it works.
Repo → github.com/n8n-io/n8n
5. Supabase
Free Firebase replacement. Build a SaaS in a weekend, charge $29-$99/month. They raised $116M for a reason.
Repo → github.com/supabase/supab…
6. Medusa
Open-source Shopify. Take 5% on every sale forever. Zero rev share to Shopify.
Repo → github.com/medusajs/medusa
7. AppFlowy
Open-source Notion. Sell self-hosted to enterprises worried about data privacy. They raised $30M because this market is massive.
Repo → github.com/AppFlowy-IO/Ap…
8. Coolify
Open-source Vercel and Heroku. Charge developers $20/month to manage their deployments. Replace their $200 Vercel bill.
Repo → github.com/coollabsio/coo…
9. Listmonk
Open-source Mailchimp. Send unlimited emails for the cost of an AWS bill. Resell to agencies at 10x markup.
Repo → github.com/knadh/listmonk
10. Penpot
Open-source Figma. Sell self-hosted design tools to agencies who refuse to upload client files to the cloud.
Repo → github.com/penpot/penpot
The difference between developers who build features and developers who build businesses is one decision.
Pick one of these. Fork it this weekend. Ship it next week.
The founders behind these repos already proved the model.
Save this. Share it with the developer in your life who deserves to break free.
100% free. 100% open source.




English

@ChatGPTapp For this I’d rather connect a separate bank account meant only for daily expenses. Then AI can analyze spending without touching the main account.
It's like using a separate VPS 😆, isolated, cleaner data, and much safer to experiment with and useful.
English

@code_bucks @hiarun02 vibe coding is the new chatbot coding - easy to demo, hard to maintain. the AI studio updates sound nice but without IDE integration at the engineering level your project dies in staging. most vibe coded projects never see production
English

@nikitabier I noticed multiple accounts quoting announcements/news tweets with 16-20 sec clips of random movie actors reactions purely to farm impressions & reach.
Zero original value, just algorithm gaming. This kind of low-effort content farming increased a lot.
Proof attached👇
English

@Roumanel_off @ForrestPKnight Opus 200k context version is performing much better for me with max effort then 1m context version.
English

I will never set up skills manually again.
Someone open-sourced a single command that scans your project, detects your entire tech stack, and installs the right AI agent skills for everything it finds automatically.
It's called autoskills. You run `npx autoskills` in your project root. That's it.
→ Reads your package.json and config files to fingerprint your stack
→ Matches detected technologies against a curated skill registry at skills.sh
→ Installs skills for 50+ technologies: React, Next.js, Vue, Svelte, Astro, Tailwind, Supabase, Neon, Playwright, Expo, Stripe, Prisma, Cloudflare, AWS, Vercel, GSAP, Bun, Deno, Hono, NestJS, Spring Boot, and more
→ `--dry-run` flag shows what it would install before touching anything
One command. Your entire AI skill stack. Installed.
Link in the comments.

English

@skirano Looking forward to it, what do you think about meta's new model for frontend? I think you are the best person to answer this.
English

@trq212 Like how you guys are improving the UX with these tiny features but it should be called something like /planPreview cause /ultraplan sounds like enhanced version of /plan.
English

@perplexity_ai There goes your subscription management saas.
Forget github green squares, I'm interested in these blue ones 😂

English

@thsottiaux @adonis_singh Hope the model arrives soon and good at frontend 🙌🏻 so I don't have to keep 2 subscriptions.
English

it’ll probably be months before we use a model of this level of capability
Chris@chatgpt21
Machines of loving grace coming a little sooner than expected 😅
English

Railway just moved their entire frontend off Next.js → Vite + Tanstack router + Nitro. 200+ routes, 2 PRs, zero downtime.
Why they left Next.js:
> builds crept past 10 minutes. 6 of those were next alone, half stuck on "finalizing page optimization"
> still on pages router → shared layouts were hacky workarounds
> app router would've fixed layouts but it's server-first. their app is client-heavy (dashboard, real-time canvas, websockets everywhere)
> they were never using next's server primitives anyway, just fighting the framework
Why tanstack + vite:
> type-safe routing out of the box. route + search params inferred, autocomplete across the whole tree
> pathless layout routes replaced every layout hack
> instant HMR, near-zero dev server startup
> SSR only where it matters (marketing, changelog, careers). pure client everywhere else
> less framework magic, more explicit control
The migration itself:
> PR 1: ripped out everything next-specific (next/image, next/head, next/router) → swapped for browser APIs or framework-agnostic libs
> PR 2: the actual framework swap. nitro replaced next.config.js, consolidating 500+ redirects, headers, and caching in one place • merged sunday morning, war room in discord, fixes shipped same day
Trade-offs they accepted:
> lost next/image → using
+ fastly edge optimization
> lost next-seo, next-sitemap → built small in-house versions
> tanstack start is newer, rougher edges exist
Result: 10+ min builds → under 2. each module is a content-hashed chunk, so shipping a billing change invalidates only that chunk. returning users download KB, not MB.
Important caveat:
This isn't a "next.js bad" story. next got railway from zero to millions of users. they outgrew it because their product is overwhelmingly client-side and they ship multiple times a day. if you're building a content site, marketing pages, or anything SEO/SSR-heavy, next is still excellent. if you're building a stateful, websocket-driven dashboard and your build times are eating your iteration loop, this stack is worth a serious look.
Pick the framework that matches your product, not the one that's trending.
Railway@Railway
We moved Railway's entire frontend off Next.js. Two PRs, zero downtime. Builds went from 10+ minutes to under two. 200+ routes on @vite_js + @tan_stack Router, instant HMR, and dev server startup in seconds. @vrzgc's full breakdown: blog.railway.com/p/moving-railw…
English

Anthropic is truly unstoppable.
Mythos is crushing Claude Opus 4.6 across every serious agentic coding benchmark.
It has found vulnerabilities in the Linux kernel, a 27-year-old vulnerability in OpenBSD, and a 16-year-old vulnerability in FFmpeg.
No wonder folks at big labs keep telling me AGI is already here.

English

@code_bucks Yes, I prefer silent clicks.
Don't know if there is an alternative with silent clicks.
English













