From a senior to future senior Hackers

Latest Posts

View all posts →

Latest Videos

View all videos →
Triaging Node.js's 16-patch security release against your dependency graph

Triaging Node.js's 16-patch security release against your dependency graph

Node.js shipped 16 security fixes on 2026-11-16, with five reportedly found using Claude. This short covers the triage order: verify the advisory set from the primary source, sort by exploit path instead of CVSS, sweep every runtime in your dependency graph, and prove the upgrade. Full write-up: https://hackyjs.com/posts/triaging-nodejss-16-patch-security-release-against-your-dependency-graph

nodejssecuritydependency-management
Auditing Qwen4-Max: 2.4T Parameters and a 60% Per-Task Claim

Auditing Qwen4-Max: 2.4T Parameters and a 60% Per-Task Claim

Alibaba's Qwen4-Max arrived in coverage dated 16 November 2026 with two numbers attached: 2.4 trillion parameters and roughly 60% lower cost per task. This audit separates what the release coverage actually states from what it leaves out — active parameters per token, unit pricing, the retry policy and the comparison baseline are all missing — and then builds a retry-adjusted cost-per-successful-task worksheet you can run against your own tasks this week. What's inside: - Why a per-task drop is a retry claim, not a rate cut: five channels can produce that 60%, and only one of them is a change to the price card. - MoE mechanics: 2.4 trillion total parameters is a memory story (about 4.8 TB of BF16 weights, 2.4 TB at FP8, 1.2 TB at 4-bit), not a per-token cost story. - Tokens per successful task, expected attempts under capped and uncapped retry loops, and the fixed per-task overhead most audits forget. - A metering wrapper that groups by task instead of by API call, so failed attempts stay in the numerator where they belong. No independent reproduction of the benchmark results was available at the time of writing, and no Qwen4-Max run backs these numbers: everything here is arithmetic over stated assumptions. Read the full write-up: https://hackyjs.com/posts/24t-parameters-60-cheaper-per-task-auditing-qwen4-max-after-retries

llm-economicsmoeqwen
Testing Email, Teams, and Copilot Fallbacks Against an M365 Control-Plane Outage

Testing Email, Teams, and Copilot Fallbacks Against an M365 Control-Plane Outage

On 15 November 2026 a reported global Microsoft 365 outage affected Outlook, Teams and Copilot. Microsoft linked it to a network upgrade issue and said it would publish a full review. The engineering problem isn't the outage itself — it's that most fallbacks turned out to share an identity provider, a DNS resolver and a tenant policy boundary with the primary path. This short walks through the testable model: - Control plane versus data plane, and why the fault pattern is warm sessions surviving while every cold start fails. Existing sessions buy you roughly one access-token lifetime, not a day. - Email, Teams and Copilot as separate dependency chains. Inbound mail often keeps landing while users cannot read it, and Copilot needs identity, a licence, Graph, the semantic index, permission trimming and tenant policy before it emits a token. - A lab-scoped harness in a disposable tenant with synthetic users: curl's --resolve flag pins one hostname to a blackhole address for a single request, modelling a DNS answer that resolves but never connects, without touching the machine's resolver. - A baseline probe captured before the drill, so you can tell a degraded probe from one that was always slow. Everything here assumes a tenant you own, users you created, and faults injected on your side of the wire. Do not fault-inject against Microsoft endpoints from a production network. Reporting summarised here is headline-level. Root cause, exact duration in UTC, regional scope beyond the reported US and Japan impact, and the causal status of the reported hotel warning-system failure all remain unconfirmed until Microsoft publishes its review. Full write-up: https://hackyjs.com/posts/testing-email-teams-and-copilot-fallbacks-against-an-m365-control-plane-outage

microsoft-365outageresilience