ardalanpouya

3 ms·

1.
by ardalanpouya 3y ago
Gotcha! will take a deeper look. thanks :)
2.
by ardalanpouya 3y ago
I like the idea of timestamping docs. How often do you run into something being "annoyingly out of date"? Asking because it happens alot for us with onboarding docs specially. I am trying to find out what we are doing wrong
3.
by ardalanpouya 3y ago
This is a very interesting idea. but I foresee two challenges here: (1) it sounds like alot of maitnance to keep a set of annotated tests that updates docs. (2) this does not sound like a solution for a company which produces handful of sys
4.
by ardalanpouya 3y ago
Sorry. In that case I used a bad word. I probably should have said internal docs that explain some specific flow or behavior of the system. A good example is one that onboards new devs.
5.
by ardalanpouya 3y ago
Is that ideal for example for onboarding new developers? Our challenge is we are are starting to hire but we also move very fast and every time we refer people to our onboarding docs, they come back confused because some essential thing is
6.
by ardalanpouya 3y ago
How is design docs different from technical docs?
7.
Ask HN: How do you keep your technical docs in sync with code?
4 points by ardalanpouya 3y ago|13 comments
8.
Show HN: Stop Wasting Time: Your Classic Documentation Is Hurting Your Business(pacely.dev)
1 points by ardalanpouya 3y ago|1 comments
9.
by ardalanpouya 3y ago
Quick feedback on the landing page. try to make it more clear as to what problem is this solving instead of being abstract. I would avoid putting an interactive widget at the top of your page. Pretty much ask yourself: "How many secon