← Timeline

AMA: 👋 I'm Michael. Former-moderator of the sub, Facebook top performer, "the Coding Machine", junior -> principal / 2009-2017, helper of bootcamps students and grads, founder of Formation for experienced engineers preparing for interviews.

r/codingbootcamp

u/Low-One2215 wrote (the comment Michael replied to):

That would be great! Would also make for some great marketing :)

u/michaelnovati replied · ★ FEATURED
Yeah I pinged our marketing person :P Here is an example of Friday's: # Engineering Digest — February 13, 2026 [Scaling LLM Post-Training at Netflix](https://netflixtechblog.com/scaling-llm-post-training-at-netflix-0046f8790194?source=rss----2615bd06b42e---4) (*The Netflix Tech Blog*) stands out today. The team details a migration from standard SPMD loops to a hybrid actor-controller architecture on Ray to support on-policy RL. The most interesting engineering nugget is their solution for model portability: using coding agents to automaticallt port Hugging Face architectures into internal optimized kernels, strictly gated by logit equivalence tests to catch tokenizer skew. For systems engineers, [Shedding old code with ecdysis](https://blog.cloudflare.com/ecdysis-rust-graceful-restarts/) (*The Cloudflare Blog*) addresses the classic problem of dropping packets during binary upgrades. Standard `SO_REUSEPORT` often creates race conditions where the old process accepts connections it can't handle; Cloudflare demonstrates a cleaner pattern by explicitly passing listening socket file descriptors across the `execve` boundary, ensuring zero downtime for Rust services. In [Fragments: February 13](https://martinfowler.com/fragments/2026-02-13.html) (*Martin Fowler*), Fowler coins "cognitive debt"—the erosion of shared system theory—as a primary bottleneck for agentic AI. It's a concise argument that modularity and semantic naming are becoming *technical requirements* for AI reasoning, effectively refuting the idea that LLMs render code quality obsolete. [Trusting the Untestable](https://eng.lyft.com/trusting-the-untestable-validation-and-diagnostics-for-the-doubly-robust-models-00853df009df?source=rss----25cd379abb8---4) (*Lyft Engineering*) offers a rigorous method for validating causal inference models (specifically Doubly Robust estimation). They compare estimates against true randomized experiments to expose how specific propensity trimming strategies distort impact measurements—a useful pattern for debugging observational bias. Finally, [How low-bit inference enables efficient AI](https://dropbox.tech/machine-learning/how-low-bit-inference-enables-efficient-ai) (*Dropbox*) provides a reliable primer on shifting from integer quantization to hardware-native formats like MXFP, though it stays theoretical regarding dequantization overhead. Strong day for infrastructure logic—specifically the necessary shift from fragile scripts to robust, state-managed platforms in both LLM training and systems binaries.