4 ms·

> 1. it starts with the worst possible feature (if I chnage the docs then a slack notification is sent to everyone). They show the update going to a #docs chan

by zild3d 4y ago

> 1. it starts with the worst possible feature (if I chnage the docs then a slack notification is sent to everyone). They show the update going to a #docs channel, that doesn't mean it notifies everyone. It notifies whoever wants to be notified of updates posted to the #docs channel. Currently using something similar for notion, channel membership is opt in, and most have notifications silenced

lifeisstillgood 4y ago
Fair enough (the words "notifies everyone" probably should be chanaged.) But that's not really the point - it's that I don't get what they are doing that beats me coding something in an afternoon. (Inam trying really hard not to do the famous Dropbox comment) But afaik the main feature here is you can add a piece of metadata in a comment that says "if this module is chnaged in a release branch, then some other documentation file must also be chnaged in the same branch. Now, yeah that's kind of good as a policy. But if I am using docutils and my index.rst has a reference to "foo.bar.addmoney" then I can see how to set up a pre-commit hook and some worker that will do the same thing. Now this is a pretty good feature to add to say Jenkins or GitHub Actions. I could see that being a desirable feature for some set of teams. I just don't like the "add extra meta data" thing, and I don't see what the win is outside of the CI tools (not too sure how they are hooking into the CI ecosystems) But hell good luck to you guys, you are in the arena. well done - good luck and I hope it works out. Just please stop and work on that elevator pitch so that I do get it. I mean Inam interested enough in this area that i watched a video, read thirty comments and replied a couple of times. I should be the perfect target customer.
- 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. Appreciate it.
  - lifeisstillgood 4y ago
    No worries - don't take the feedback as a negative - I wish you all the best, this problem is a real issue (as is a lot around this point - see "your code as a crime scene" as a good book on this sort of automated analysis of likely areas code is falling down) and good luck for just being in the game - well done and wish you the best
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.

by zild3d 4y ago

lifeisstillgood 4y ago

Fair enough (the words "notifies everyone" probably should be chanaged.) But that's not really the point - it's that I don't get what they are doing that beats me coding something in an afternoon. (Inam trying really hard not to do the famous Dropbox comment) But afaik the main feature here is you can add a piece of metadata in a comment that says "if this module is chnaged in a release branch, then some other documentation file must also be chnaged in the same branch. Now, yeah that's kind of good as a policy. But if I am using docutils and my index.rst has a reference to "foo.bar.addmoney" then I can see how to set up a pre-commit hook and some worker that will do the same thing. Now this is a pretty good feature to add to say Jenkins or GitHub Actions. I could see that being a desirable feature for some set of teams. I just don't like the "add extra meta data" thing, and I don't see what the win is outside of the CI tools (not too sure how they are hooking into the CI ecosystems) But hell good luck to you guys, you are in the arena. well done - good luck and I hope it works out. Just please stop and work on that elevator pitch so that I do get it. I mean Inam interested enough in this area that i watched a video, read thirty comments and replied a couple of times. I should be the perfect target customer.

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. Appreciate it.
- lifeisstillgood 4y ago
  No worries - don't take the feedback as a negative - I wish you all the best, this problem is a real issue (as is a lot around this point - see "your code as a crime scene" as a good book on this sort of automated analysis of likely areas code is falling down) and good luck for just being in the game - well done and wish you the best

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.