hahnbee

7 ms·

61.
by hahnbee 4y ago
We totally understand how important security is to companies. It the main reason why we are source available and self-hostable.
62.
by hahnbee 4y ago
We're such huge hypocrites. You're right. We're addressing this asap.
63.
by hahnbee 4y ago
Thank you, we really appreciate your feedback. We're both technical founders and we're very aware that we need to work on making the language clearer. Your feedback makes it crystal clear that we really need to work on this. App
64.
by hahnbee 4y ago
Thanks for the feedback! We were planning on adding an ownership layer to it so that you can ping certain people who are the specific people who need to be notified.
65.
by hahnbee 4y ago
Yeah. We started this whole endeavor because we, as developers, also hated writing documentation. We thought that if we made it easier - whether it's by automating it through AI or by bringing the documentation closer to the code - it
66.
by hahnbee 4y ago
Your point about incentivizing is very interesting. We mainly interviewed teams that were in our batch AKA early stage startups/small teams that didn't have much of a divide between management and developers - definitely a mistake
67.
by hahnbee 4y ago
> how do we keep documentation close to the context to which it relates, AND allow it to be manipulated, tested, and more, all through automated business logic? Solve that. Well spoken.
68.
by hahnbee 4y ago
Yeah, that honestly makes a lot of sense.
69.
by hahnbee 4y ago
Gotcha, apologies for all the questions - did you implement this for your company? That's interesting that the reception you got was primarily against documentation inside a repo. Maybe Gitbook could've been a good compromise? I r
70.
by hahnbee 4y ago
That's very interesting. How did you implement this? : "I've taken to supporting cross-references across the repo, connecting references of the form ^^{foo} to anchors of the form @@{foo}, wherever they appear (code, comment,
71.
by hahnbee 4y ago
Currently we use a repo's git information to create the link between code and documentation. We also support many-to-many connections so you could granularly choose lines of code to connect to documentation. But you make a good point!
72.
Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams
149 points by hahnbee 4y ago|55 comments
73.
Too Lazy to Write Documentation? Let the AI Write It for You(betterprogramming.pub)
6 points by hahnbee 5y ago|0 comments
74.
Show HN: Figstack – Automatically understand, document, and translate code(figstack.com)
5 points by hahnbee 5y ago|0 comments