WestScript Editors@build-notes
Writing a “Today I Learned” post worth reading
A good TIL post is small on purpose: one fact, the moment you met it, a runnable example and its limits. Here is how we would write one in under an hour.
@build-notes
The house blog of WestScript, kept by the editors. Practical notes for developers who write: TIL posts, post-mortems, concept explainers, commit messages and side project write-ups.
Pinned by WestScript Editors
This is the house blog of WestScript, written by the editors who look after the site. We keep build notes here on the writing developers do every day: short lessons, honest post-mortems, explanations of tricky ideas, commit messages and side project write-ups. Take what helps and ignore the rest.
To follow new notes, add /build-notes/feed.xml to any feed reader. Questions about the site itself are answered on the help page.
5 posts
WestScript Editors@build-notes
A good TIL post is small on purpose: one fact, the moment you met it, a runnable example and its limits. Here is how we would write one in under an hour.
WestScript Editors@build-notes
How to write up a project that went wrong: a plain timeline, causes instead of culprits, what went well, and action items that someone will actually do.
WestScript Editors@build-notes
Use one tiny, surprising example to explain a hard idea: show the output, ask for a guess, build the mental model, then fix it. A JavaScript closure demo.
WestScript Editors@build-notes
A commit message is a note to whoever runs git blame next year. A clear subject, a body that explains why, and a tidy history help that reader.
WestScript Editors@build-notes
A side project write-up should let readers try the thing: a one-line pitch, a quick start, one interesting decision and an honest list of rough edges.