with-point

5 ms·

1.
by with-point 7y ago
I've also had enough with various wikis. And at some point we didn't find a decent tool for documenting our projects. We decided to build our own tool https://nots.io (yay NIH syndrome). The main idea is to make possib
2.
by with-point 7y ago
Shameless self-promotion: That was exact problem I was facing during my entire career. That's why we decided to build a tool which links documentation and code -- https://nots.io This gives at least two benefits: now it&#x2
3.
by with-point 7y ago
Gonna make a new section in price FAQ with this question. Thanks for your input!
4.
by with-point 7y ago
Hey, @mc3 Thanks for your feedback! This is the reason why we posted our work on HN. I really appreciate it! You won't believe, storing Nots data as a separate git repo or as a metadata was our initial thought when we were starting the
5.
by with-point 7y ago
Any information around the code: short text or link on what code does. The bigger technical specification in markdown. PDFs/images/GDocs that describe why code looks the way it looks. You're using some non-standard language f
6.
by with-point 7y ago
We have 2 levels of prices: -- per project, no matter how many teammates involved into documenting stuff -- per user, if you're quite big org and have lot's of colleagues and lots of repos/projects. If your entire team saves
7.
by with-point 7y ago
Hi HN, I’m Alex of Nots.io ( https://nots.io/ ) Nots is a SaaS for engineering teams aimed to help keep project docs up-to-date by linking them to the source code. The problem: During my career, I saw so many times, how the c
8.
Show HN: Nots.io – a developer-centric look at how to document your code(nots.io)
18 points by with-point 7y ago|9 comments
9.
Show HN: Nots.io – a developer-centric look at how to document your code
6 points by with-point 7y ago|0 comments