The best newsletters for AI and software engineers (2026)

Going deep on a fast-moving field is one of the few things newsletters are genuinely great for. A good one is a smart person's weekly attention, already filtered — which beats refreshing Hacker News or doomscrolling a timeline that's optimized to make you angry, not informed. The catch is that the must-read list keeps growing. Every strong newsletter you add is another tab, another unread count, another thing you subscribed to with the best intentions and now skip.

So here's a coverage map worth your inbox — newsletters AI and software engineers actually read, grouped so you can see which distinct job each one does. In short: start with Latent Space, add a daily such as TLDR AI or AlphaSignal, use The Batch and Import AI for different kinds of research framing, keep The Pragmatic Engineer (and Refactoring if you lead a team) for craft and career, and add Hacker Newsletter if you still want HN signal without the scroll. Follow every source that gives you a useful, non-redundant angle; NewsNook is the layer that lets you cover the full set without reading every issue end to end. Each pick below is real, currently publishing, and described honestly.

Last checked: July 2026. Every newsletter below was confirmed active as of this date. Last Week in AI resumed after a mid-year pause — keep an eye on cadence. Newsletters get renamed, paused, or paywalled; if one's gone quiet by the time you read this, treat that as a sign to re-audit your list.

AI and ML research — the frontier, explained

If your job is to understand where the field is going, not just what shipped this week, start here.

• The Batch (DeepLearning.AI, with Andrew Ng) — a weekly roundup of AI news and research with Ng's own letters up front. Strong on framing why a development matters, written for practitioners rather than headline-chasers.
• Import AI (Jack Clark) — weekly, research-forward, and unusually good at connecting frontier papers to policy, safety, and the bigger trajectory of the field. Dense, but the kind of dense that pays off.
• Ahead of AI (Sebastian Raschka) — long-form essays, roughly every couple of weeks, that explain the how behind model releases. Closer to a short course than a news digest; one issue often teaches more than five dailies.
• Last Week in AI (Andrey Kurenkov / Skynet Today) — a weekly text-and-audio summary of the week's biggest AI news with editorial commentary. Useful as a broad catch-up — just know the cadence has slipped before, so treat it as a bonus weekly rather than a load-bearing habit.

AI engineering — building on top of the models

Less "what does this paper mean," more "how do I ship this." Dailies overlap, but they also emphasize different signals; keep the ones that consistently add a useful angle and let your reader collapse the repetition.

• Latent Space (swyx & Alessio Fanelli) — the strongest pick for engineers building on AI: evals, inference, agent architectures, and the practical decisions other outlets skip. Newsletter plus podcast.
• The AI Engineer (Paolo Perrone) — production-minded explainers and tool comparisons for engineers leveling into AI systems — RAG vs fine-tuning, observability, inference trade-offs — closer to a short course than a news digest.
• TLDR AI — a free daily, five-minute read of AI news, research, and tools, slanted toward engineers and the work rather than the hype cycle. Good as your fast daily scan.
• AlphaSignal — another free daily for engineers, weighted toward papers, repos, and model releases ranked for signal. It overlaps with TLDR AI, but the paper-and-repo emphasis can justify following both; keep it if that distinct angle regularly earns attention.
• Ben's Bites — a free daily of AI product launches, tools, and news. More product-curious than research-dense; the right daily if you care what shipped for builders more than what landed on arXiv.
• The Neuron — a daily, broader-audience AI newsletter covering tools and industry moves in a quick, skimmable format. Useful if you want a wider lens than the engineering-only feeds.

Software-engineering craft — careers, systems, the inside view

Not AI-specific, but on most serious engineers' lists.

• The Pragmatic Engineer (Gergely Orosz) — deep dives on Big Tech and startup engineering from the inside, plus career and industry intelligence. Widely read by senior engineers and engineering leaders; a paid tier unlocks the full archive.
• ByteByteGo (Alex Xu) — system design explained in plain language and clear diagrams, from the authors of the popular system-design book series. Especially handy when you're leveling up your architecture instincts or prepping interviews.
• Refactoring (Luca Rossi) — weekly essays on how engineering teams actually ship — process, AI-in-the-workflow, management archetypes — written for ICs and managers who want practices, not just news.
• Software Lead Weekly (Oren Ellenbogen) — a free, hand-curated weekly of people, culture, and leadership links for anyone building teams. Light to read; high signal if you're growing into tech lead or eng management.

General tech context — the wider picture

To keep the field in perspective, not just the code.

• Benedict Evans — a weekly Sunday read on what happened in tech that mattered and what it meant. Strategy-and-context over tactics; good ballast against week-to-week noise.
• Hacker Newsletter — a hand-curated weekly digest of the best of Hacker News since 2010. The civilized way to get the signal from HN without losing an afternoon to the comments.

That's a deliberately structured list, not a ceiling. Start with the lanes that match what you're trying to get better at, then add sources when they contribute a distinct perspective: research, implementation, engineering craft, leadership, or wider context. The goal is broad enough coverage to catch what matters without pretending every arrival deserves a full read.

How do you keep up with all of them?

Here's where good intentions usually collapse. The problem is not following half—or all—of these sources; it is treating every issue as a full-read obligation. The inbox becomes the bottleneck, the issues pile up, and the deep ones—the Ahead of AI essay, the Pragmatic Engineer deep dive—are exactly the ones that get marked-read-and-forgotten. A broad source portfolio is valuable when every arrival is covered and only the right pieces consume deep-reading time.

This is the gap NewsNook is built to close. We're not a publisher and we don't write any of the above — we're the reader. Connect your Gmail and the newsletters you already subscribe to land in one place — no forwarding, no setup — each distilled to key points, why it matters, and a skip-or-read call, grounded in the specific writers you chose rather than a generic AI guess at the field. You skim the gist of everything and open the two issues that actually deserve your full attention, with the writer's complete piece one tap away.

For a learner, the rest of the workflow is the part that compounds:

• Ask the AI assistant to go deeper on anything you just read — "explain the eval setup in that Latent Space issue" — with answers grounded in your newsletters and the open web, with citations you can check.
• Audio of your feed, so the commute becomes a fluency-building pass instead of dead time.
• Highlights and search, so the sharp line from "some issue a few weeks back" is captured when you read it and recallable when you need it.

It's the difference between a folder of unread newsletters and an actual learning habit. (More on the engineer-and-learner workflow on the for engineers & lifelong learners page — and if your real problem is the firehose itself, see keeping up with AI without doomscrolling Hacker News.)

The whole thing in three lines:

1. Cover the lanes that matter with as many useful, non-redundant sources as the field demands.
2. Read them on a schedule instead of doomscrolling HN between meetings.
3. Distill every arrival so the deep issues still get opened — briefs up front, full pieces a tap away.

NewsNook is free to start for up to three newsletters — connect Gmail and your first brief is ready in a couple of minutes.