Blog
Short reads on building software.
Tips, tool reviews and news for people who build for the web. One idea per post, explained plainly.
62 postsPage 4 of 6RSS feed
Client-side caching for API responses
Refetching the same data on every visit wastes time and bandwidth. HTTP cache headers, an in-memory cache and browser storage each solve a different part of the problem.
Web Workers: move heavy work off the main thread
Heavy JavaScript freezes the page because it shares a thread with the interface. A Web Worker runs that work in the background. A working example and the limits to know.
WebAssembly beyond the browser: what WASI enables
WebAssembly began as a way to run fast code in browsers. With WASI it runs on servers, at the edge and inside plugins: sandboxed, portable and quick to start.
Angular Signals: fine-grained reactivity explained
Signals give Angular a precise way to track state: when a value changes, only the views that read it update. How signal, computed and effect work, with examples.
Tree shaking: why your bundle still ships unused code
Tree shaking removes code you never import, but only when the bundler can prove it is unused. ES modules, the sideEffects flag and your import style decide what goes.
Monorepo dependencies with pnpm and npm workspaces
Workspaces let a frontend, an API and shared packages live in one repository with one install. How pnpm and npm workspaces work, and when each one fits.
Promise.allSettled: keep the results that succeeded
Promise.all throws away every result when one request fails. Promise.allSettled waits for all of them and reports each outcome, so one failure cannot empty a page.
JavaScript debugging beyond console.log
console.log works until the bug is three calls deep. Breakpoints, conditional breakpoints, logpoints and the call stack show what the code does while it runs.
Dev Containers: one environment for the whole team
New developers lose days to setup, and 'works on my machine' never dies. A devcontainer.json file gives everyone the same tools, versions and services.
The WebAssembly Component Model, explained
Core WebAssembly modules can only exchange numbers. The Component Model adds typed interfaces, so code written in Rust, Go, Python or JavaScript can be combined safely.
Error handling in microservices: retries and circuit breakers
In a distributed system, something is always failing a little. Timeouts, retries with backoff, circuit breakers and consistent errors keep one fault from spreading.
JWT best practices: expiry, storage and validation
JSON Web Tokens are simple to issue and easy to get wrong. Short lifetimes, refresh token rotation, safe storage and strict validation close the common holes.
Tell us what’s in the way.
A few lines is enough. You get a candid yes, a candid no, or a sharper question.
- Working software in week four
- A reply in one business day
- Handover is the deliverable
Prefer email? [email protected]