Fullstack Web Developer | B.Eng | Founder @codeulo | React & Next.js | Pro websites | Sharing dev lessons | Chelsea | Web dev @Preply | wa.link/jv163p
Joined April 2020
- Tweets 1,926
- Following 1,457
- Followers 1,093
- Likes 2,004
84 Photos and videos
Pinned Tweet
Looking to #connect with builders on X ๐
If you're into:
โข Building SaaS
โข AI tools
โข Vibe coding
โข Building in public
โข Figuring it out as you go
Drop a quick intro or tell us what you're working on.
Always down to connect with builders. Let's grow together ๐.
2
2
77
6 years of building on the web has taught me that the frameworks change constantly, but TCP, HTTP status codes, database indexing, and browser rendering engines remain exactly the same. Master the fundamentals, and framework migrations become trivial ๐ซถ.
18
3
1
8
579
My fellow devs. If you are building a realtime feature, do not default to raw WebSockets immediately. Check out Server-Sent Events (SSE) first.
SSE runs natively over HTTP/2, handles reconnection automatically out of the box, and is significantly easier to scale behind standard reverse proxies than stateful WebSocket connections.
2
21
When reviewing code, don't just look for bugs. Look for cognitive load. If a file takes more than two minutes of intense concentration to mentally trace, it needs to be broken down. Readable code saves companies more money than micro-optimized algorithms ever will.
1
26
Edge computing isn't a silver bullet. Running Next.js on Edge functions sounds amazing for latency, but if your database is sitting in a single AWS region across the world, every single database query your Edge function makes faces massive cold-start and round-trip penalties.
Keep your compute close to your data ๐ซถ.
19
The best debugging tool is still a solid night of sleep. I havve spent three hours staring at a broken Fastify hook at 1:00 AM, only to wake up at 8:00 AM and fix it in exactly four lines of code. If you are stuck, step away from the IDE. Your brain keeps compiling in the background anyway ๐
.
1
20
Stop using any to bypass the compiler, and stop using as unknown as T to force types.
If you're dealing with unpredictable data from external APIs, use unknown combined with type guards or a library like Zod to validate schemas at the application boundary. Make your type safety real, not a cosmetic illusion ๐๐คฃ.
1
30
What's the difference between a mid-level dev and a senior dev in the JS ecosystem?
Mid-level: Knows how to use Next.js, Fastify, and Tailwind perfectly.
Senior: Knows when using Next.js is total overkill and a single static HTML/JS file would perform better, cost less, and load faster.
1
31
Supabase is just PostgreSQL under the hood. Stop treating it like a basic NoSQL document store.
If you aren't writing foreign key constraints, indexing your frequently queried columns, or using stored procedures for complex transactions, you are missing out on 90% of its power. Let the database do the heavy lifting, not your Next.js API route.
1
22
The hardest part of hitting 6 years of engineering experience isn't learning new languages, it's learning when to say "no" to a rewrite.
Junior devs want to rewrite because the existing code is messy. Senior devs know that a rewrite just trades a set of known bugs for a set of completely unknown bugs. Patch, refactor, and ship ๐.
18
If you are using Node.js for heavy cryptographic operations or image processing, stop doing it on the main event loop. Node is single-threaded for JavaScript execution.
Offload those tasks to the worker_threads module or delegate them directly to a dedicated service. Protect that event loop at all costs.
1
22
Shipping software in 2026 isn't about knowing every single framework feature. It's about having a rock-solid, opinionated boilerplate where you don't have to rethink your database connection, auth flows, or Tailwind layout every time you open a new repository.
Speed comes from elimination, not raw typing speed. What's the one tool in your stack you refuse to replace?
16
Next.js App Router optimization tip: Stop putting use client at the very top of your page files unless absolutely necessary.
Instead, push your stateful logic (like toggles, modals, or counters) down into isolated, leaf-node components. Keep your layout tree purely server-side to maximize streaming SSR efficiency and keep your client bundle tiny.
2
19
Stop building high-throughput backends on Express just because it's what you learned in 2018.
If you're building a realttime system or a heavy API layer in 2026, Express is actively costing you money in server overhead.
Here is a brutal technical breakdown of why I migrated our core services to Fastify, and the exact event-loop optimizations that cut our CPU utilization by 40%. ๐งต
2
2
38
Don't rewrite working software just for the hype. If your Express app gets 10 requests a minute, leave it alone.
But if you are scaling Next.js apps with heavy microservice backends, or piping data into Supabase webhooks, that microsecond difference compounds into thousands of dollars on your compute bill.
Build for where your data is going ๐, not where it is right now.
1
18
Are you still heavily relying on Express for enterprise apps, or have you made the switch to Fastify, NestJS, or Bun's native server?
Let's debate below in cm section. ๐
14