Hi folks! So, I’ve been thinking about log messages lately. And, honestly most of them in my opinion feel like system noise instead of something a human can act on. Like, half the time it’s a stack trace, an error code, or “something went wrong,” which doesn’t help anyone. At work, I was discussing what “human‑friendly” logging should look like with my team, and someone wrote up a short guideline about writing clearer, more actionable messages (disclosure: I work at this company). I found it useful, so sharing in case others like this kind of thing.
Curious how others approach this. There are some other good reads as well in this repo, do check out!
We’ve been experimenting with a more reproducible and narrative SQL workflow inside VS Code, and ended up building a SQL Notebook feature into our extension. It mixes SQL queries, Markdown, and results, and it stores everything in a single .exabook file.
The motivation was mostly practical: teams were writing SQL in one tool, explaining it in another, and sharing screenshots elsewhere. Nothing was reproducible, versionable, or reviewable. So we merged those ideas into one workflow that fits naturally inside VS Code.
Would love feedback, especially on:
- the notebook format
- whether the UX feels natural or awkward
- limitations we might not be seeing where this fits (or doesn’t fit) in a typical SQL workflow
Curious how others approach this. There are some other good reads as well in this repo, do check out!