cborenstein

16 ms·

121.
Ask HN: How do you use Git for docs?
2 points by cborenstein 8y ago|1 comments
122.
by cborenstein 8y ago
Might be fun to integrate with an API like twitter or twilio so you can practice using an HTTP client (I use axios) with react.
123.
by cborenstein 8y ago
Design Your Life https://designingyour.life/the-book/ applies engineering design principles to your career and personal goals
124.
by cborenstein 8y ago
very interesting - that seems like a good and still pretty simple rule too. I feel like if the docs are organized well then volume shouldn't matter but at the same time having fewer docs means less room for error in organizing.
125.
by cborenstein 8y ago
that's a good idea. would you recommend a file/directory structure or just tags/keywords next to each command in a flat file? I'm wondering if the directory structure will feel too clunky and result in less getting writt
126.
by cborenstein 8y ago
very interesting. It seems like a good idea to not worry about the structure when first writing things down but to reserve time at the end of the week to organize. where do you usually write your "temp" notes? do you use any struc
127.
by cborenstein 8y ago
thanks for sharing - that makes sense. Where do you usually write your runbooks? In a google docs/confluence type wiki or with your code? How do you organize them so that you can find/share them quickly?
128.
by cborenstein 8y ago
thanks for all of your suggestions. What do you find is the best way to organize the command-line incantations (what a great way to describe them) and click sequences? do you write them in something like google docs or confluence or in your
129.
by cborenstein 8y ago
I like that simple rule but I think it will lead us to have a lot of small notes super quickly, which might be difficult to weed through later. Do you find yourself with this problem? How do you make the small commands findable/underst
130.
Ask HN: When should my team start documenting?
10 points by cborenstein 8y ago|16 comments