Shen Lijun.

Write down what broke, so nobody has to debug it twice.

I'm Shen Lijun. This is the hub for the sites I maintain: hands-on error references for Linux and Windows, notes on tools and everyday knowledge. Nothing gets published until it has been reproduced in a real environment.

Why several sites instead of one

Because they serve different people, searching for different things.

An admin at 2 a.m. searching Start request repeated too quickly needs commands they can paste and a decision rule they can check against their own output. Someone trying to understand a number on a medical report needs a plain explanation, not a lecture. Putting both on one homepage helps neither.

So each direction gets its own site, and this page is the door to all of them.

Three rules I write by

  • Reproduce first. No conclusion gets published unless it ran on a VM or a real machine. If it hasn’t been tested, it stays empty.
  • Give the test, not the spell. Not “try this” but “look at this line first — if it’s A change X, if it’s B change Y.”
  • State the boundary. Which version it applies to, which distro it doesn’t, and when the whole approach breaks down.