Testing Open Graph locally is a bit deceptive: your browser can see localhost, but Facebook, LinkedIn, Slack, Discord, X/Twitter, etc. cannot.
The best workflow is:
1. Check the HTML locally
2. Expose localhost with ngrok
3. Test the public URL in real social preview/debugger tools
Chrome plugins are useful for fast feedback, but the final validation should happen through a public HTTPS URL.
I wanted a tiny CLI tool for a very specific workflow: take an image and expand its canvas to 1200x630, centered, without resizing the image itself. Useful for Open Graph images.
But the interesting part was not the image logic. The interesting part was this constraint:
I do not want global Node, npm, pnpm, TypeScript, or tsx.
That changes the setup.
Authentication sounds scary until you look at it from the top down: who are you, how do you prove it, and how does the app remember you. This guide builds that mental model one layer at a time.
Your .zshrc started as ten tidy lines and has quietly become a 400-line dumping ground of half-remembered aliases, dead exports, and copy-pasted snippets you're afraid to delete. Here's how to clean it up and keep it that way.
Most developers use curl as a quick way to "hit an endpoint". But curl is much more than that — a tiny HTTP client, a debugging tool, a poor man's Postman, a network probe, a CI health checker, a download manager, and often the fastest way to understand what's really happening between your machine and a server. Here are 25 curl recipes I actually reach for.
You write next build, run vercel deploy, and a URL comes back. But between that command and the response your users get, there's a whole distributed system — build pipelines, an edge network, serverless and edge functions, caches at multiple layers. This post opens the box and walks through what Vercel actually does with a Next.js app.
A top-down tour of Next.js: start from the mental model of the framework as a whole, then drill into the concepts that actually shape how you build with it.
A field guide to the modern frontend ecosystem — the frameworks, tools, standards, and patterns worth knowing about, so you can tell the durable signal from the passing noise.
Caring isn't just a nicety, it's a productivity multiplier.
This is the first of a series of posts about the most common mistakes in Frontend development. This is the most common mistake I see in React projects.
This post explains what the Single Responsibility Principle (SRP) is and why it's important for React components. It shows how putting too much code and too many tasks in one component can lead to messy, hard-to-maintain apps.