zain__t

6 ms·

1.
I'm building a way to verify resume claims with AI
1 points by zain__t 6mo ago|0 comments
2.
by zain__t 6mo ago
That day is now and the reason is that the documentation doesn't have to be written anymore. The conversation that led to the decision already exists — in your PR comments, Slack threads, and tickets. The reasoning is already there. It
3.
by zain__t 6mo ago
Those comment templates are actually really well structured you've invented a mini decision record format without calling it that. The problem you're hitting is discoverability the why is there, but only if you happen to read that
4.
by zain__t 6mo ago
The Q&A doc you're maintaining is fascinating you've essentially hand-built the thing I'm trying to automate. The 'Why Kafka?' entry is exactly the kind of decision that disappears when you leave. The search pro
5.
by zain__t 6mo ago
This is the clearest articulation of the problem I've seen. You've basically described exactly what I'm building. The passive ingestion angle treating reasoning as a byproduct of work already being done rather than a separate
6.
by zain__t 6mo ago
This is incredibly valuable context thank you. The career security point especially is something I hadn't fully articulated but explains why ADRs always die. Nobody wants to document themselves out of a job. The approach I'm explo
7.
by zain__t 6mo ago
Completely agree the manual capture is exactly where it breaks down every time. Curious, what's your current setup? GitHub + Slack or something different?
8.
by zain__t 6mo ago
The git hook idea for enforcing doc updates is really interesting has that actually worked long term for your team or does it eventually get bypassed?
9.
by zain__t 6mo ago
I am already working to automate the process
10.
How do you capture WHY engineering decisions were made, not just what?
41 points by zain__t 6mo ago|64 comments