14 ms·
For what it’s worth: the expected behaviour to swap code snippets internally is to share a link to an internal version of pastebin/gist that allows comments, ve
by bertil 9y ago
For what it’s worth: the expected behaviour to swap code snippets internally is to share a link to an internal version of pastebin/gist that allows comments, version control and referencing. Whether that has to be compulsive or whether casual code is fine is probably a worst contention that vim vs. emacs so I’ll just leave that here.
On Workplace by Facebook: I can see how that seems counter-intuitive, but I’ve worked for four distinct companies who had it or moved to using it, with or without Slack and (given some hints on how to use it properly) this is the most compelling solution to a lot of internal communication issues. It’s about as impactful as email or cellphone: you can’t really understand how things work without. I am not considering working for a company that doesn’t use it (or an improvement).
- johannes1234321 9y agoThis depends on the snippet size and purpose. For collaboration on code it's likely the wrong tool. However when exchanging single statements there is no good reason to switch between tools.