Live data from Hacker News

Viewing profile — zain__t

zain__t

HN member
Joined
Fri, Mar 13, 2026, 7:47 PM UTC
HN karma
13
Public activity
17 items

About zain__t

Founder of Nubroetch. I put together expert teams to build complex projects. In my spare time, I build and ship SaaS products. Currently tackling the 'AI vs AI' war in recruitment.

Feel free to contact : zain@trynubrotech.com

Recent public activity

  1. story
  2. story
  3. story
  4. story
  5. story
  6. story
    I'm building a way to verify resume claims with AI

    A job post gets 500 applicants in an hour. Recruiters spend 6 seconds per resume. Nobody checks if any of it is true. We read your resume, test every skill you claimed, and give yo…

  7. comment
    Comment #47369914

    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 t…

  8. comment
    Comment #47369879

    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…

  9. comment
    Comment #47369802

    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…

  10. comment
    Comment #47369774

    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 w…

  11. comment
    Comment #47369747

    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 docume…

  12. comment
    Comment #47369563

    Completely agree the manual capture is exactly where it breaks down every time. Curious, what's your current setup? GitHub + Slack or something different?

  13. comment
    Comment #47369524

    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?

  14. comment
  15. comment
    Comment #47369062

    I am already working to automate the process

  16. comment
  17. story
    How do you capture WHY engineering decisions were made, not just what?

    We onboarded a senior engineer recently strong, 8 years experience. He spent 3 weeks playing code archaeologist just to understand WHY our codebase looks the way it does. Not what …