964: Markdown as a CMS is a bad idea

Episode Summary

Executive Summary: Syntax’s potluck episode covers practical developer advice and life decisions: keyboard shortcuts and productivity tuning, using Error Lens in VS Code, an experimental Svelte 5 service worker cache approach, how AI affects framework choice and young developers’ careers, when to choose CMSs versus Markdown, whether to move countries for work, commit hygiene with AI coding tools, and backup strategies for personal, family, and sensitive data. The hosts repeatedly favor simplicity, automation, and human judgment over hype.

Main Topics: Keyboard shortcuts, hyper keys, and productivity workflows: The hosts argue that shortcuts meaningfully improve flow when customized well, especially in editors, OS window management, video editing, and mouse/keyboard hybrids. They recommend learning built-in shortcuts first, then building a personalized layer using tools like Better Touch Tool and mouse gestures. VS Code Error Lens and inline diagnostics: They clarify that 'AirLens' was actually Error Lens, a VS Code extension that displays errors inline beside code. They discuss tuning font size, colors, and exclusions so the tool is useful without being obnoxious. Svelte 5 service worker caching and stale-while-revalidate: Scott explains a service worker that caches remote function data in IndexedDB, serves initial data quickly from local storage, and uses stale-while-revalidate behavior. He notes missing invalidation logic on mutation and shares that the gist is experimental. AI, frameworks, and the future of web development: They debate whether framework choice still matters in the AI era and conclude it does—because performance, maintainability, and the ability to adopt web standards matter. They favor frameworks and UIs that use browser primitives, declarative APIs, and less duplicated code. Choosing a stack for greenfield SaaS or a band site: They recommend mature, widely supported tools, but emphasize matching the stack to the app’s needs and the team’s strengths. For content-heavy sites, they strongly discourage Markdown-as-CMS and prefer a real CMS with a good editing experience. Career advice: moving countries, AI, and staying relevant: The hosts advise caution on moving abroad for less money, especially with a family, unless there is strong assurance and upside. They also reassure young developers that AI will change the job, not eliminate the need for smart problem-solvers who keep learning. Backup strategies for large files, family data, and sensitive info: They outline a layered backup approach: local automatic backups plus off-site backups, with tools like Time Machine, Backblaze, Synology NAS, Backblaze B2, and encryption for sensitive files. They stress automation because manual backups fail in practice.

Key Arguments: Keyboard shortcuts are most valuable when they reduce friction across the whole workflow—not just in an editor—and become especially powerful when combined with a hyper key and mouse gestures. Error Lens is useful because it surfaces problems inline, but it needs customization to avoid visual overload; the goal is signal, not noise. The service worker cache is helpful for fast first loads and offline-ish behavior, but without mutation invalidation it can serve stale data. AI does not erase the importance of framework choice; better performance, accessibility, and maintainability come from choosing modern, declarative tools that align with web standards. Markdown as a CMS is painful for content-heavy sites; a real CMS is easier for non-developers and more sustainable for publishing. For a greenfield SaaS, the best stack is the one your team can ship and maintain confidently, not the trendiest one. Moving countries for a job should be approached carefully, especially with family and a pay cut; ask for more money and evaluate long-term stability before uprooting. Young developers should not panic about AI; the durable advantage is being the person who can learn continuously and solve harder problems. Backups should be automated, local plus remote, because if you rely on memory or manual steps, you will eventually lose data. Sensitive data deserves encryption and separate protection, whether via encrypted folders, disk images, or safe storage for recovery codes.

Data Points: Markdown files in Scott’s personal/blog CMS: ~1,200 - Scott describes his personal blog as being backed by a very large Markdown repository. Markdown files on Syntax site: ~1,000 - Used to illustrate why Markdown-as-CMS becomes painful at scale. Figma employee rank offered: employee number 8 - Scott says he was offered an early Figma role and turned it down. Personal salary example: $48,000/year - Scott references his prior agency salary when discussing why a move for Figma would have been a downgrade. Age of developer asking about AI career risk: 19 - A young listener asks whether AI makes web development a bad career choice. New AI commit frequency mentioned: 10 to 50 times every five minutes - A listener describes Claude Code generating a huge number of logical breakpoints/commits. Video recording size: 60–70 GB - They estimate the size of about three hours of recorded video when discussing NAS workflows. Backblaze coupon: 2 months free - Sentry sponsor mention included a promo with this duration.

Pivotal Quotes: "Markdown as content as CMS sucks. Don't do it." — Scott: Advice to the band-site/website questioner about replacing Markdown-based publishing with a real CMS. "Choice of framework does matter, but I don't think that that's going to stop the fact that everything is just on the React ecosystem right now." — Wes: Discussion of AI-assisted coding and framework selection in a changing ecosystem. "You should assume at any point in time that your computer and/or the place where you have your backups will go away." — Scott: Backup strategy guidance emphasizing redundancy and disaster recovery planning.

Implications: Listeners should optimize for maintainability, automation, and real-world usability over novelty. AI will amplify good systems and bad ones, so choose stacks, workflows, and backup plans that stay understandable, recoverable, and easy to use.