2+ week, 4+ day ago   (303+ words) Explaining a technical problem in a second language can become harder when you try to include every detail at once. Logs, reproduction steps, customer impact, and possible fixes all compete for the first sentence. A simple structure helps: conclusion → reason…...

1+ week, 3+ day ago   (124+ words) I’m officially starting my journey into technical writing. For a while, I’ve been interested in technology, but I didn’t know exactly where I fit in. I eventually discovered technical writing, and it immediately caught my attention because it combines two…...

4+ week, 2+ day ago   (1030+ words) On 1 August I opened an issue that was three sentences long. A hundred and one minutes later the feature was merged, and the document that got it there ran to 457 lines. I didn't write those 457 lines. In fact, I didn't…...

3+ week, 5+ day ago   (277+ words) useful for planning and tracking progress Data Engineering isn't only about writing code and working...documentation is as important and part of the Engineering. Imagine building a pipeline that extracts data...can: That's Markdown and its part in the engineering…...

5+ day, 22+ hour ago   (297+ words) Writing good technical articles is difficult when the writing happens in a vacuum. Most developers write posts long after the code is finished. By the time you switch to a browser to format markdown and set tags, the immediate context…...

1+ week, 1+ day ago   (22+ words) Terrain — prepares the ground so agents don't have to guess where to stand. 🔗 GitHub:... Tagged with architecture, documentation, github, softwareengineering....

1+ week, 1+ day ago   (22+ words) It is no longer news how much our lives as developers, engineers, tinkerers, artisans, and coders... Tagged with ai, webdev, programming, productivity....

3+ week, 2+ day ago   (180+ words) Run this on any repo doing spec-driven development: Same rule, three specs, three wordings — and two meanings. 30 days from purchase is not 30 days from delivery. Nobody decided that fork. A coding agent paraphrased it into existence, and no human caught…...

1+ week, 6+ day ago   (684+ words) AI code assistants have made documentation fast to produce and easy to ignore. The issue is not speed; it's trust. Models can write a polished docstring that describes a function that no longer exists, or an example that fails on…...

1+ week, 6+ day ago   (785+ words) Two side projects, one developer, an AI assistant on both. You work on them when you can and when you feel like it, for fun. And precisely because it's for fun, you drop everything that's boring: documentation. Spoiler: you don't…...