Liquid syntax error: Variable '{{% raw %}' was not properly terminated with regexp: /\}\}/
How intentional loading decisions keep your app fast at scale. Frontend performance is not a late-stage cleanup task. It’s not tech debt. It’s a set of decisions we make every day while we code — what we load, when we load it, and how we render it. The answer depends on the importance of the code, its size, and when the user actually needs it. Get that wrong, and the browser pays for everything
I’m going on a short vacation this week, so this post is coming out a bit earlier than usual. I actually had a different, more “useful” topic in mind — something educational, something responsible. But then I came across this fascinating article: I don’t like Tailwind. Sorry not sorry written by @freshcaffeine , and I couldn’t get it out of my head. So I decided to write a response instead. I actu
What Is an Atomic Transaction? Before we begin, let’s define atomic transaction clearly: “It is a protective wrapper around multiple state updates that guarantees the whole operation either succeeds completely or has no effect at all.” Inside an atomic transaction, you can perform multiple set() calls, and even cross multiple await boundaries. Only when the entire operation succeeds do we commit
The "Unsharable" Dashboard Problem Imagine this common B2B SaaS scenario: An executive opens your analytics dashboard. They spend three minutes configuring the data—they filter the status to "Active," set the date range to "Last 30 Days," sort the table by "Highest Revenue," and navigate to Page 4. They copy the URL and Slack it to their team lead. The team lead clicks the link, but instead of see
Hey everyone, I shared this earlier as a CLI to analyse npm packages before installing. Since then, I’ve added something I think is even more useful: 👉 You can now scan GitHub repos before cloning or running them npx guard-install --repo https://github.com/user/repo There’s a growing pattern (especially in crypto interviews / side projects): “Clone this repo and run it locally” Some of these rep
Most React performance problems are not architectural. They are not about picking the wrong state manager or choosing the wrong rendering strategy. They are small habit things that look perfectly fine in isolation but compound quietly across a codebase until your app feels sluggish and you are not sure why. This article covers five of the most common ones, with code examples so you can see exactly
Most monorepos pay lip service to "share code via libraries." In practice, apps grow huge and libraries stay shallow. The shared/ folder becomes a junk drawer. New code goes wherever's easiest, which is usually wherever the developer is already typing - the app. After scaling our frontend monorepo to 19 applications and 86 libraries (roughly 74,000 lines of TypeScript), I've seen this pattern from