4 ms·
I’ve been pretty happy with Slab. Straightforward shared wiki with a good editor, governance, and integrations. https://slab.com/ https://slab.com/ I tried usi
by sa46 3y ago
I’ve been pretty happy with Slab. Straightforward shared wiki with a good editor, governance, and integrations. https://slab.com/ https://slab.com/
I tried using README files in the repo but there’s far too much friction to get most folks to bother. Google Docs tend to disappear content due to a lack of structure.
- morkalork 3y agoSpeaking of Google docs, I just now had the joy of talking to a co-worker while trying to figure out the source of truth for something and we spent 10 minutes thinking we were looking at the same doc when in fact we were not! The owner had made and shared multiple slightly different copies.
- paiute 3y agoAt my current job, i need to make a jira ticket, a branch, do a live review… all to change a minor thing in a README
- neilkk 3y agoThat sounds bad, but sometimes it makes sense to optimise the process for midsize changes. The vast majority of useful work is done in midsize changes. Lots of people like to generate a flurry of tiny commits but it's not necessarily the most productive way to work, even without much overhead per change. You can always bundle tiny changes together until it's worth it for you and other people like the reviewer to do the parts that don't scale downwards.
- nomel 3y ago> I tried using README files in the repo but there’s far too much friction I have confluence links in my Readme, which seems to be a pretty good balance, since it's physically impossible for people to use a search bar in a wiki.