1d ago · 13 min read · Originally published on ajeetchaulagain.com on May 11, 2026. I've been building ShipWindow for a few months now — deliberately slowly, with a production mindset from day one. No users yet, but real ar
Join discussion
Mar 9 · 8 min read · I almost picked wrong. We were rebuilding our frontend platform at work — five apps, three shared component libraries, a design token package, and a CLI tool that nobody fully understood anymore. Classic monorepo chaos. I spent about two weeks seriou...
Join discussionMar 3 · 11 min read · Monorepo Tools Guide: Turborepo, Nx, Bazel, and Moon A monorepo without proper tooling is worse than separate repos. You get all the drawbacks -- slow builds, tangled dependencies, CI that runs everything on every change -- without the benefits. The ...
Join discussionMar 3 · 6 min read · Monorepos are excellent for sharing code across multiple packages and apps, but they have an inherent problem: as they grow, builds get slow. Run tests on a change to a utility package, and you might trigger rebuilds of 15 apps that depend on it — mo...
Join discussionMar 3 · 8 min read · Monorepo Tools Compared: Turborepo, Nx, and Bun Workspaces Monorepos are no longer controversial. Most teams with more than two related packages eventually consolidate into a single repository. The question isn't whether to use a monorepo -- it's whi...
Join discussionMar 3 · 9 min read · Monorepo Tools Compared: Nx vs Turborepo vs Bazel vs Lerna A monorepo is only as good as the tooling that manages it. Without proper build orchestration, a monorepo with 50 packages becomes slower than 50 separate repos. The right tool makes builds f...
Join discussionFeb 16 · 7 min read · This article was originally published on Saru Blog. What You'll Learn Next.js + Go monorepo architecture patterns Practical use of pnpm workspace + Turborepo Sharing UI components across 4 portals Package splitting strategies that don't break down...
Join discussionFeb 12 · 11 min read · Turborepo: Monorepo Build Optimization Modern engineering teams managing monorepos face a critical bottleneck: build times that scale linearly with repository size. A monorepo containing 50+ packages can easily consume 30-45 minutes per CI run, multi...
Join discussionFeb 12 · 6 min read · Turborepo Monorepo: Manage Multiple Packages Fast The Build That Took 20 Minutes (Now Takes 30 Seconds) Our CI pipeline was killing productivity. Then we switched build tools. Here's what happened. Table of Contents Modern Build Tools 2026 Architect...
Join discussion
