markdown guide
 

I don't have work experience with huge slack groups but I haven't seen it scale well for non-work purposes.

If your company is interested, we've been curious about standing up a private version of the dev.to app as a company intra-net for a theoretically more scalable form-factor. πŸ˜„

 

Heh... I guess what I'm looking for is "how do larger orgs run their Slacks so they stay useful?" To date, we've mostly stuck to leaving channels public - even those that we share with other companies. Unfortunately, particularly in longer discussions or threads(and, well, Slack's "threading" feature is comically limited), it often feels like "wouldn't this be better done via email"?

It kind of feels like the "chat" model has an implied-casual nature that email doesn't. Particularly with discussions held in "public" channels, it seems like the whole "is what I'm saying well thought out and/or well-articulated" thought-process isn't really considered.

/shrug

Dunno. Seems like there could be better way to use the tool but I'm not sure how to encourage better habits?

Classic DEV Post from Feb 27

Yes, I still fall victim to Imposter Syndrome

Imposter syndrome rears its ugly head again.

Thomas H Jones II profile image
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.