A little — every day.
A breakdown in numbers of an Apple Configurator configuration profile: what it consists of, why almost half of the block list is not entertainment but workarounds, and what changed in az-log.
Sixteen major versions: one at a time, what breaks at each stage, import cycles, overlays in the top layer, zone.js, and why a monorepo makes upgrading cheaper.
How to build and check only what a change touches: nx affected, the right base for comparison, why cancelled pipelines lose changes, OOM on the runner, and the cache that hid tests.
A follow-up to the post on your own ESLint rules: when a fix can be trusted to eslint --fix, when it should only be suggested, and how to write rules for Angular HTML templates.
What to move first, how to draw library boundaries, and why a new region is now 5 minutes and ~25 configuration files rather than a copy of someone else's project.
Preparing for Java junior and intern interviews with the OCA 1Z0-808 book: progress in numbers, what each chapter covers, where TypeScript habits get in the way, and LeetCode problems for each …
What changes in v4, why library classes vanish from the build in a monorepo, what @source and @reference are for, what to do with Sass, and how to keep old habits from coming back.
One project for 17 apps, release and source maps in CI, sampling, why all HTTP errors stuck together in one group, fingerprints, and what Sentry should not know about the user.
If the same mistake reaches review twice, a machine should catch it. A three-step ladder, your own rule taken apart step by step, tests, and how to measure the benefit.
How I started logging every day in a spreadsheet across four areas, what the very first row showed, and why my iPhone and iPad were left with almost no entertainment afterwards.