<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mark Ajzenstadt</title>
    <description>The latest articles on DEV Community by Mark Ajzenstadt (@limestonedigital).</description>
    <link>https://dev.to/limestonedigital</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4031066%2Febcc4b0b-0154-4b7e-a0ab-573ad281e4a6.png</url>
      <title>DEV Community: Mark Ajzenstadt</title>
      <link>https://dev.to/limestonedigital</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/limestonedigital"/>
    <language>en</language>
    <item>
      <title>Top 26 Engineering Newsletters Actually Worth Your Inbox</title>
      <dc:creator>Mark Ajzenstadt</dc:creator>
      <pubDate>Fri, 17 Jul 2026 15:56:34 +0000</pubDate>
      <link>https://dev.to/limestonedigital/top-30-engineering-newsletters-actually-worth-your-inbox-adl</link>
      <guid>https://dev.to/limestonedigital/top-30-engineering-newsletters-actually-worth-your-inbox-adl</guid>
      <description>&lt;p&gt;Everyone recommends ByteByteGo and The Pragmatic Engineer. &lt;/p&gt;

&lt;p&gt;Don't get me wrong, they're great... but the best engineering writing of the last two years is coming from newer publications nobody's put on a list yet. Here's what survived my filter.&lt;/p&gt;

&lt;p&gt;I have a rule: if I haven't opened a newsletter in three weeks, I unsubscribe. No guilt, no "maybe later" folder. It's the only way to keep email useful when every engineering team, indie hacker, and AI startup on the planet is running a Substack.&lt;/p&gt;

&lt;p&gt;That rule has consequences. Over the past couple of years it has killed off almost every famous-name newsletter in my inbox — not because they got worse, but because they got comfortable. &lt;/p&gt;

&lt;p&gt;Meanwhile, a new generation of engineering publications launched around 2023–2024 started earning their slot every single week. They're smaller, sharper, and written by people still close to the work.&lt;/p&gt;

&lt;p&gt;The other thing my rule revealed: AI engineering quietly became its own discipline. Not "AI news" — there are a thousand newsletters rehashing model launches. I mean the craft of building production systems on top of LLMs: agents, evals, brownfield integration, governance, cost. That coverage barely existed two years ago. Now it's the most valuable section of my inbox, which is why it leads this list.&lt;/p&gt;

&lt;p&gt;So here's what survived. Twenty-six newsletters, organized by topic, heavy on publications you haven't seen on every listicle. Steal the whole list.&lt;/p&gt;

&lt;h2&gt;
  
  
  🤖 AI Engineering &amp;amp; Production AI
&lt;/h2&gt;

&lt;p&gt;Two years ago this category didn't exist. Today it's the most important one here, because building with LLMs in production is genuinely different work — different failure modes, different economics, different skills — and general engineering newsletters mostly aren't covering it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://latent.space" rel="noopener noreferrer"&gt;Latent Space&lt;/a&gt; — swyx &amp;amp; Alessio Fanelli.&lt;/strong&gt; swyx literally coined "AI engineering" as a discipline, and this is its watering hole: podcast, essays, and the AINews digest covering frontier models, agents, and the career path itself. The anchor of the category.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://thefoundation.limestonedigital.com" rel="noopener noreferrer"&gt;AI Foundation&lt;/a&gt; — Limestone Digital.&lt;/strong&gt; The one I'd add first. One tight email every Tuesday, written from inside AI-native engineering teams actually shipping AI to production. Recent issues like "the brownfield problem" (AI in greenfield is easy; AI in brownfield requires real work), "AI governance is not sexy (but it's a must-have)," and "tokens ≠ value" hit the operational bottlenecks nobody else writes about. No hype, no launch rehashes — just what works when the demo ends and the migration begins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://magazine.sebastianraschka.com" rel="noopener noreferrer"&gt;Ahead of AI&lt;/a&gt; — Sebastian Raschka.&lt;/strong&gt; The most technically honest LLM writing on Substack — model architectures, paper roundups, and tutorials from the author of &lt;em&gt;Build a Large Language Model From Scratch&lt;/em&gt;. Zero hype.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://interconnects.ai" rel="noopener noreferrer"&gt;Interconnects&lt;/a&gt; — Nathan Lambert.&lt;/strong&gt; AI research explained from inside frontier labs: RLHF, post-training, open-weight models. Essential if you build on top of open models.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://turingpost.com" rel="noopener noreferrer"&gt;Turing Post&lt;/a&gt; — Ksenia Se.&lt;/strong&gt; Goes several layers deeper than typical AI roundups, with explainers on LLMs, agents, and AI infrastructure that stay bookmark-worthy for months.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://aitidbits.ai" rel="noopener noreferrer"&gt;AI Tidbits&lt;/a&gt; — Sahar Mor.&lt;/strong&gt; A practitioner's filter on the firehose. The deep dives on agentic workflows and AI-assisted coding are consistently ahead of the curve.&lt;/p&gt;

&lt;h2&gt;
  
  
  🧠 Software Engineering &amp;amp; System Design
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://newsletter.systemdesigncodex.com" rel="noopener noreferrer"&gt;System Design Codex&lt;/a&gt; — Saurabh Dashora.&lt;/strong&gt; Practical system design through real-world case studies rather than abstract theory. A recent launch that's already a staple for interview prep and architecture thinking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://hungryminds.dev" rel="noopener noreferrer"&gt;Hungry Minds&lt;/a&gt; — Alexandre Zajac.&lt;/strong&gt; One system design or AI concept per week, curated from 100+ sources by an ex-Amazon SDE III. The Monday brief format is ruthlessly efficient: one deep idea, a few trends, done.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://thetshaped.dev" rel="noopener noreferrer"&gt;The T-Shaped Dev&lt;/a&gt; — Petar Ivanov.&lt;/strong&gt; JavaScript/React/Node architecture plus career growth in the AI era. One of the freshest voices (launched ~2024) on staying valuable as a full-stack engineer while AI reshapes the job.&lt;/p&gt;

&lt;h2&gt;
  
  
  🧑‍💼 Engineering Leadership &amp;amp; Management
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://grocto.substack.com" rel="noopener noreferrer"&gt;groCTO&lt;/a&gt; — the Typo team.&lt;/strong&gt; Most leadership newsletters predate AI-assisted development. groCTO tackles the new questions: measuring productivity when agents write code, restructuring teams, AI-era engineering metrics.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://theengineeringmanager.com" rel="noopener noreferrer"&gt;The Engineering Manager&lt;/a&gt; — James Stanier.&lt;/strong&gt; Monthly deep dives on management, org design, and the human side of software, from the author of &lt;em&gt;Become an Effective Software Engineering Manager&lt;/em&gt;. His writing on prioritization alone is worth the subscription.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://softwareleadweekly.com" rel="noopener noreferrer"&gt;Software Lead Weekly&lt;/a&gt; — Oren Ellenbogen.&lt;/strong&gt; 700+ issues of consistent, high-quality curation on people, culture, and leadership. The most reliable link-list on this entire page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://levelup.patkua.com" rel="noopener noreferrer"&gt;Level Up&lt;/a&gt; — Patrick Kua.&lt;/strong&gt; Curated reading for EMs, VPs, and CTOs, running for over a decade. Kua's commentary around each link is where the value is.&lt;/p&gt;

&lt;h2&gt;
  
  
  📈 Career Growth
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://alifeengineered.substack.com" rel="noopener noreferrer"&gt;A Life Engineered&lt;/a&gt; — Steve Huynh.&lt;/strong&gt; Treats your career like an engineering problem to be optimized, from an ex-Amazon Principal Engineer. The promotion-packet and compensation content is uncommonly specific.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://strategizeyourcareer.com" rel="noopener noreferrer"&gt;Strategize Your Career&lt;/a&gt; — Fran Soto.&lt;/strong&gt; Launched in 2023 and grown fast by being genuinely actionable — every Sunday issue gives you something to &lt;em&gt;do&lt;/em&gt;, not just something to think about.&lt;/p&gt;

&lt;h2&gt;
  
  
  🧰 Frontend &amp;amp; Web Development
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://bytes.dev" rel="noopener noreferrer"&gt;Bytes&lt;/a&gt; — Fireship.&lt;/strong&gt; The JavaScript ecosystem's news, twice a week, served with actual humor. Now run by Jeff Delaney, so the entertainment density is even higher. (Most lists still credit ui.dev — that changed.)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://thisweekinreact.com" rel="noopener noreferrer"&gt;This Week in React&lt;/a&gt; — Sébastien Lorber.&lt;/strong&gt; Exhaustive React and React Native coverage from a Docusaurus maintainer, with sharp analysis of what actually matters versus what's just loud.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://webweekly.email" rel="noopener noreferrer"&gt;Web Weekly&lt;/a&gt; — Stefan Judis.&lt;/strong&gt; Surfaces the small web platform features — HTML, CSS, JS, performance, accessibility — that you'd otherwise miss entirely. Consistently delightful.&lt;/p&gt;

&lt;h2&gt;
  
  
  ☁️ DevOps, SRE &amp;amp; Platform Engineering
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://platformweekly.com" rel="noopener noreferrer"&gt;Platform Weekly&lt;/a&gt; — Luca Galante.&lt;/strong&gt; The flagship newsletter of the platformengineering.org community, with 100k+ readers. If "platform engineering" is anywhere on your roadmap, this is the source.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://sreweekly.com" rel="noopener noreferrer"&gt;SRE Weekly&lt;/a&gt; — Lex Neva.&lt;/strong&gt; Curated reliability and incident-response reading that takes the holistic SRE view — human factors and process, not just failover architectures. Running strong since 2016.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://www.devopsbulletin.com" rel="noopener noreferrer"&gt;DevOps Bulletin&lt;/a&gt; — Mohamed Labouardy.&lt;/strong&gt; Weekly AWS, Kubernetes, cloud security, and FinOps news with original stories and open-source picks alongside the headlines.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://www.lastweekinaws.com" rel="noopener noreferrer"&gt;Last Week in AWS&lt;/a&gt; — Corey Quinn.&lt;/strong&gt; AWS news with the noise strained out and gently, lovingly mocked. The most efficient — and funniest — filter on AWS's firehose of releases.&lt;/p&gt;

&lt;h2&gt;
  
  
  📰 General Tech &amp;amp; Daily News
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://tldrsec.com" rel="noopener noreferrer"&gt;tl;dr sec&lt;/a&gt; — Clint Gibler.&lt;/strong&gt; Weekly AppSec, cloud security, and DevSecOps tools and research, trusted by 90k+ subscribers. The security newsletter for engineers who aren't full-time security people — which is most of us.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://tldr.tech" rel="noopener noreferrer"&gt;TLDR&lt;/a&gt;.&lt;/strong&gt; Byte-sized daily tech and programming news in a 5-minute read, with 13 specialized editions. Subscribe to the daily plus whichever verticals match your stack.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://changelog.com/news" rel="noopener noreferrer"&gt;Changelog News&lt;/a&gt; — Adam Stacoviak &amp;amp; Jerod Santo.&lt;/strong&gt; Open source and developer news from two people who've covered the space since 2009. Nobody contextualizes what a project or license change means better.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://programmingdigest.net" rel="noopener noreferrer"&gt;Programming Digest&lt;/a&gt; — Jakub Chodounsky.&lt;/strong&gt; The anti-overload newsletter: five handpicked articles per week, no filler. The constraint forces the best curation on this list.&lt;/p&gt;




&lt;h2&gt;
  
  
  What my unsubscribe rule taught me
&lt;/h2&gt;

&lt;p&gt;Look at what survived and a pattern emerges. The newsletters that last aren't the ones with the biggest audiences or the most famous authors — they're the ones with a &lt;em&gt;sharp filter and a point of view&lt;/em&gt;. Five links instead of thirty. One concept instead of a news dump. A Tuesday email that assumes you ship production code, not that you collect bookmarks.&lt;/p&gt;

&lt;p&gt;The second pattern is the one I'd bet on for the next two years: the center of gravity in engineering content is moving from "here's what shipped" to "here's what works." Everyone can read a model-release changelog. Almost nobody is writing honestly about what happens after — the brownfield migrations, the governance conversations, the gap between token spend and actual value. That's exactly the territory the AI engineering section of this list occupies, and it's why &lt;a href="https://thefoundation.limestonedigital.com" rel="noopener noreferrer"&gt;AI Foundation&lt;/a&gt; by Limestone Digital has become the first thing I open on Tuesdays: it's written from the side of the work where the demo has ended and the real problems begin.&lt;/p&gt;

&lt;p&gt;If you take nothing else from this post, take the rule itself. Subscribe liberally, unsubscribe ruthlessly, and let your inbox become a place that makes you better at your job instead of busier at it. Start with two or three from the AI section, give them three weeks each, and keep only what earns its slot.&lt;/p&gt;

&lt;p&gt;And if there's a newer newsletter in your inbox that survived your own filter — I genuinely want to know about it. Drop it in the responses.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Mark A.
&lt;a href="https://limestonedigital.com" rel="noopener noreferrer"&gt;https://limestonedigital.com&lt;/a&gt; &lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>leadership</category>
      <category>softwareengineering</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
