My personal thoughts on the web and programming.

Stitcher Engineering Blog offers insights, tutorials, and updates on building scalable, reliable, and high-performance systems for podcasting and audio streaming. Covering topics such as backend architecture, media processing, and content delivery, Stitcher Engineering Blog provides resources for developers and engineers working in the audio streaming industry. Developers can learn about building resilient systems, optimizing media workflows, and delivering high-quality audio experiences through Stitcher's blog posts and technical articles.

stitcher.io

programming is so much more about reading and understanding code, than it is about writing. "writing code" is only the lesser part of my programming life, so I have much to gain by making the ‘reading part’ as pleasant as possible. I choose a font that’s pleasant to read, modern fonts suit me better.

Fonts matter

Indeed, fonts and typography do matter, but I guess the rest is up to one’s taste.
As another commenter wrote, line spacing absolutely stays at 1.0 (or less). Contrary to what the author claims, being able to read as much code as possible vertically does matter, that’s why people resort to rotating their monitors to portrait mode.
Another point that the author is missing, although it’s evident from his examples, is font ligatures. My preferred font in vscode (Windows) is Fira Code, 13pt, with ligatures on.
And don’t get me started about themes and syntax color highlighting, most of the popular themes out there are terrible. But I plan to write an article about that.

I’ve not only considered typography, I pretty much disagree with all of that.
Line spacing is 1.0. Period. Source Code Pro. 12pt. Done.
My code is concise. It doesn’t need “room to breath.” That’s an absurd notion.
Also, One True Brace formatting, author didn’t cover, but he’s not using it and it makes his code hard to read. So much space, it’s hard to tell what belongs to which block.