Go monk

A Lewis approach to IT

C.S. Lewis was not a fan of newspapers. He spent time reading books, writing, thinking and discussing rather than keeping up with everything. This approach might also work in tech, once you reach a certain level of seniority. The basics, like TCP/IP and Unix, change slowly. The ideas behind them, like simplicity and solving the real problem, change even more slowly. And the hype that lasts reaches you anyway. However, some adaptations are needed.

The adaptations

Your own stack is not news. Vulnerability announcements (CVEs), vendor advisories, end-of-life notices, release notes and deprecations for the things you run are work input, not hype. Read them; ignoring them is negligence.

Avoid the reverse trap. Lewis warned against “chronological snobbery”: assuming an idea is wrong because it’s old. That cuts both ways. “Old means good” is as lazy as “new means good”. Some hype sticks, at least for some uses: cloud, containers, maybe AI. The question is whether something solves a real problem better. You don’t need the daily noise, but it’s worth checking in every few months.

A practical setup

  1. Drop: tech news feeds, hype on X and LinkedIn, “top 10 tools of the year” posts.
  2. Keep: security advisories and release notes for what you run, plus one or two slow sources, like a weekly digest or a quarterly roundup.
  3. Spend most of your time on: classic books, quality code (like Go’s stdlib), hands-on work in a lab, and fixing real incidents properly, down to the root cause.
  4. Once a year: ask what new thing has proven itself, then learn that one thing in some depth.

In short

Ignore the hype, but don’t ignore your systems. That’s close to what Lewis did: he read little news, but he was well informed about what mattered to him.