Standing Up an Nx Monorepo: Task Graph, Affected Builds, and Remote Cache
Stand up an Nx monorepo with a correct task graph, nx affected builds and a self-hosted remote cache so a one-package change no longer rebuilds the whole repo.
Stand up an Nx monorepo with a correct task graph, nx affected builds and a self-hosted remote cache so a one-package change no longer rebuilds the whole repo.
Build a distroless-style ASP.NET service on Ubuntu Chiseled: non-root by default, no shell, a fraction of the CVEs, with globalization and debugging handled.
Hand-rolled $1/$2 argument handling breaks the moment flags get reordered. Here is a copy-pasteable getopts block with long options, validation and a working –help.
T+1 removes the overnight window manual allocation and confirmation flows depend on. Automate same-day affirmation and measure every post-trade hop against the shortened clock.
NIS2 and the CRA are frequently discussed as if they’re the same regulatory push wearing two names. They regulate two entirely different things, aimed at two entirely different actors — and an organisation that’s mapped one against its obligations has often mapped nothing useful against the other. I’ve written separately about NIS2’s essential-entity obligations and …
If you are an essential entity, the supervisor does not wait for an incident to come looking. That single fact — proactive, ex-ante supervision — is what separates your obligations under NIS2 from everyone else’s, and it changes what “compliant” has to mean. NIS2 sorts in-scope organisations into two tiers, essential and important, and most …
AI ambition runs into a hard physical constraint that software rarely does: the compute it needs is scarce, expensive, and cannot be conjured on demand. GPU capacity — the specialised hardware that trains and runs large AI models — has been in genuine shortage, which turns compute from a utility you draw on freely into …
Nobody talks about trust when they’re choosing a database. They talk about performance, cost, vendor support, and what the development team knows. These are legitimate considerations. They are not the complete picture. How data is stored is a trust decision. Who can access it is a trust decision. How long it is retained and what …