Developer, Ghost Writer | Dm for work/collab
Joined October 2025
- Tweets744
- Following1.1K
- Followers2K
- Likes14.4K
Imagine building this with Next.js:
A website that never needs a redesign.
It observes where users struggle, generates new interface variations, tests them safely, and improves itself.
No manual A/B testing.
No static UX.
A product that evolves while people use it.
PostgreSQL can store large column values outside the main table row.
It's called TOAST.
Large values may be compressed or moved to separate storage.
A simple SELECT * can be more expensive than selecting only the columns you need.
Oh My God!
Jensen Huang is caught with his pants down economist.com/business/2026/…
A long-running PostgreSQL transaction can prevent VACUUM from cleaning up dead rows.
Even if that transaction isn't actively querying anything.
One forgotten transaction can contribute to table bloat.
Idle doesn't always mean harmless.
Dumb MacBook User:
256GB → M1
512GB → M2
1TB → M3
2TB → M4
4TB → M5
Smart MacBook User:
256GB MacBook + 2TB External SSD.
Apple hates this one trick. 💀
Prediction: By 2050, React won’t just render pixels.
It’ll render environments.
→ Interfaces projected into rooms
→ Components anchored to real objects
→ UI controlled by gestures
→ State shared across physical spaces
One component tree. An entire world.
Imagine building a React app that NEVER goes offline.
Backend dies? It keeps working.
Database disappears? Local state survives.
Network splits? Users keep collaborating.
Servers return? Everything reconciles.
The frontend becomes its own infrastructure.
Wild React idea:
What if useState() could hold multiple futures?
→ Simulate 100 user decisions
→ Render their outcomes in parallel
→ Compare consequences instantly
→ Commit only the chosen timeline
Git branches, but for live UI state.
Hot take: React components shouldn’t be permanent.
Imagine a UI that rebuilds itself around every user.
No fixed navbar.
No predefined dashboard.
No traditional page layouts.
Every user gets a completely different interface.
Same app. Infinite experiences.
Someone should build a React app that renders your NEXT action before you take it.
→ Predicts user intent
→ Prepares entire UI branches
→ Executes likely workflows in a sandbox
By the time you click, the work is already done.
Zero perceived latency.
The next trillion-dollar idea might be a browser that rewrites itself.
Not just the UI.
Its rendering engine.
Its security architecture.
Its entire execution model.
Continuously improving without breaking anything.
A browser that evolves.
Hot take: The last generation of developers will build for screens.
The next will build for reality.
Interfaces that exist in physical space.
Follow your eyes.
Understand your surroundings.
Disappear when unnecessary.
React for the physical world.
Unpopular opinion:
By 2050, we won’t download apps.
You’ll describe what you need.
Your device will build the software.
It’ll exist for 10 minutes.
Then disappear.
No App Store. No installations.
Software created on demand.
Someone should build a browser with a SHADOW MODE.
Before you click “Confirm,” it simulates the action in an isolated environment.
Shows what changes.
Detects irreversible effects.
Lets you preview the outcome.
A sandbox for real-life clicks.
What if your React app remembered HOW you use it?
→ Rearranges frequently used tools
→ Remembers unfinished workflows
→ Restores your exact workspace
→ Adapts shortcuts to your habits
No chatbot. No AI-generated UI.
Just brilliant product engineering.
Imagine a React app that works BETTER when your internet disappears.
→ Full offline editing
→ Local-first storage
→ Background sync
→ Automatic conflict resolution
→ Zero lost changes
Not just offline support.
Offline-first by design.
Apple could put a Windows laptop inside a MacBook shell.
Half of tech Twitter would suddenly discover how smooth Windows feels.