My goal is to make adding new features as easy as 1,2,3: 1) Create API handler to be used in a catch all route like /api/[...all]. this will internally route the requests to the plugin's route handlers GET|POST|PUT|DELETE /api/blog/posts 2) Create client router that will be

Every developer will eventually run into a big only a better developer can solve 😅

I'm tired too bro 😩

🫩

🧐 I just had to see how my lib is being bundled.

Its an abusive relationship really

Most people think the hard part is getting started. The hard part is continuing to do the work when the excitement wears off and the grind feels hopeless.

The riskiest thing you can do is have a job. You give your 9-to-5, your weekends, your soul to a company that replaces you with a line of code or a budget cut. These companies preach “we’re a family” until the bottom line gets tight or when they find a optimization that can cut

every time I talk about my engine with devs that used Unity their whole life I always get the same reaction: 1 - they don't believe one person can build an engine that surpasses it and 2 - even if they could, it must result in tech that is "too hard" to use this used to

About time 👌

Custom directives are getting out of control. 'use server' 'use client' 'use cache' 'use cache:remote' 'use workflow' 'use streaming' 'use edge' 'use strict' is a JS directive. The stuff above isn't. That's a problem. More: tanstack.com/blog/directive…

Even though I'm not a fan of string directives Vercel's Workflow thing is excellent DX. 👌 share.google/Odek5irHmJ5Tbj…