Skip to content
tezvyn:
Menu

Tooling

48 bites tagged Tooling: interview questions with model answers, and 60-second explainers.

Test yourself: Top 30 Tooling interview questions →Multiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.
Vue, Angular & Svelte1 min read

Angular is decoupling its compiler from TypeScript APIs

Angular says it is building an Angular-specific compiler so the framework can benefit from TypeScript 7’s native tooling without depending on its compiler APIs.

React Native2 min read

Cost of console.log and production-safe debugging

Each console.log serializes data and, when devtools are attached, crosses the bridge synchronously, blocking the JS thread; strip logs in release and use Flipper, dev tools, or remote crash and analytics tools.

React Native1 min read

Expo managed workflow vs bare React Native

Expo gives fast setup, OTA updates, managed builds, and prebuilt APIs; bare gives full native control and arbitrary native modules.

Product Strategy1 min read

Measure a competitor's public performance

Synthetic audits via Lighthouse and WebPageTest, timed public-API probes, and reading response headers.

Node.js & Express1 min read

dependencies vs devDependencies in package.json

Dependencies ship and run in production; devDependencies are only for development; omitted with npm install --production.

Design Systems1 min read

Automated detection of deprecated component usage

Machine-readable deprecation metadata, AST scanning across repos, scheduled jobs, per-team dashboards and PR-level warnings with codemod links.

Design Systems1 min read

Tracking design system health across the org

Static AST scanning for component imports and props, lint or detect-one-offs, parse package manifests for version drift, aggregate into a dashboard.

Design Systems1 min read

Tracking design system component usage and versions

Static scan of code or lockfiles, a central reporting store, and a dashboard; data drives deprecation and roadmap.

Design Systems1 min read

Tracking design system adoption technically

Scan codebases for component imports via AST, compute adoption versus off-system usage, and aggregate into a dashboard over time.

Design Systems1 min read

Monorepo vs polyrepo for a design system

Atomic cross-package changes and shared tooling versus build orchestration, caching, and versioning complexity.

Design Systems1 min read

Storybook's role in design system infrastructure

Isolated development, living documentation, visual and interaction testing, shared review surface.

Design Systems1 min read

Publishing a component to a private NPM registry

Configure package.json fields and scoped name, build dist, set registry auth, npm publish with access restricted.

Design Systems1 min read

Auto-generating component API docs from source

Extract types via react-docgen-typescript, surface in Storybook ArgsTable, enrich with JSDoc.

Design Systems1 min read

Automated Release Pipeline

An automated release pipeline turns merged design-system changes into published, versioned packages without manual steps, using semantic versioning and changelogs so consumers can upgrade safely and the team ships small changes frequently and reliably.

Data Science & Analytics2 min read

Python Virtual Environments

A virtual environment is an isolated Python installation with its own packages, so each project gets the exact dependency versions it needs without conflicting with other projects or the system Python.

CSS & Design Systems2 min read

Monorepo tradeoffs for a design system

Monorepos give atomic cross-package changes, shared tooling, and easy local linking; drawbacks include build complexity, CI scaling, and tighter coupling.

CSS & Design Systems1 min read

CSS Modules versus BEM for encapsulation

CSS Modules scope via build-time hashed class names automatically; BEM scopes via disciplined human naming with no tooling.

CSS & Design Systems1 min read

Transforming tokens for multiple platforms

A transformer like Style Dictionary parses JSON, applies platform transforms, and renders formatted outputs (CSS vars, Swift, Kotlin) via configured platforms.

CSS & Design Systems1 min read

Why design systems use Sass or PostCSS

Sass adds variables, nesting, mixins, and functions for reuse; PostCSS transforms CSS via plugins like autoprefixer.

CSS & Design Systems1 min read

Build a custom PostCSS plugin (px to rem)

Export a plugin returning visitor hooks, walk Declaration nodes, parse and rewrite px values to rem against a base size.

CSS & Design Systems2 min read

What does autoprefixer do and why?

Autoprefixer is a PostCSS plugin that adds vendor prefixes to CSS based on a browserslist target using compatibility data, so you write standard CSS and it handles support.

CSS & Design Systems1 min read

What is PostCSS and how it differs from Sass

PostCSS is a plugin-driven tool that parses CSS into an AST and transforms it; it is not a fixed language like Sass but a platform for plugins like autoprefixer.

CSS & Design Systems1 min read

What is a CSS pre-processor?

A pre-processor adds variables, nesting, mixins, functions, and partials, compiling its own syntax into plain CSS for the browser.

Design Systems1 min read

Measuring design system adoption and health

Component coverage and version spread from code scans, usage analytics, issue and satisfaction signals.

Get Tooling bites daily.

Five a day, five minutes, offline. With quizzes so it sticks.

The iPhone app is on the way

We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.

Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.

Get it on Google PlayiPhone app coming soon