Original Summary

Over the past few weeks I’ve hit some genuinely interesting engineering problems on my projects. Sometimes I want to share those learnings/work. Other times I just want to keep that piece of work, the architecture, the decisions I made, the alternatives I considered, and why I went the way I did. LinkedIn doesn’t feel like the place for that, because it ends up reading like self-promotion. And I don’t want to start a blog. I’m an engineer, not a technical writer, and I don’t want every problem I solve to become a writing exercise. It feels more urgent now that coding agents write a lot of the code. The PR only shows what changed, but the reasoning behind it is gone once the session ends. So I’ve been building EngLog. Each record captures the problem, the investigation, the decisions, the tradeoffs and the evidence behind it. Some records I write myself. Others I draft from my GitHub PRs and linked issues, then review and edit before publishing. It only reads the PR and issue text, never the code. I’ve put the link and an example record in the comments. If you’ve worked on something interesting recently, I’d love for you to try adding a record. I’m also curious how other engineers handle this. Do you keep track of the interesting problems you’ve solved, or does that context mostly get lost once the PR is merged?   submitted by   /u/Then_Respect_1964 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/15 00:50:30