As a professional you can't just go off in a corner and produce something (no matter how fun it is). I learned this the hard way as a software engineer. In fact the hardest part of software engineering is collaborating with humans and integrating their ideas and requirements into what you're building.
Helping other people, not producing output or profit, is the fundamental human enterprise. Other people exist and need help: It's the only reason you have a job. Amazing how many people miss this and think their job is to "be good at X" instead of "help other people with X".
True, if you are talking about general population. But among those who can code in my experience the biggest obstacle at work is being able to communicate and collaborate efficiently.
Generally yes, it's old and stable, and it's not centralized so not everyone goes down at once. When you host your own you often get to choose the downtime as well, updates get run at midnight when no one is working, not at 10AM on a work day.
A service the scale of slack also runs into a whole host of scaling issues that a little intranet IRC client will never have.
Oh good. I was going nuts trying to figure out why I suddenly couldn't communicate with my coworkers and Slack kept saying I didn't have internet when I clearly had internet.
Ah, the downside of relying on a third party for critical communication infrastructure when you're a full remote company...
I just quit a call where we were using screen hero. It worked great. Then I noticed my status said I was still on a call so I thought I'd restart slack. It didn't really want to quit, so I killed it. Sorry everyone.
Sigh... 10 minutes of cursing trying to troubleshoot the LTE connection on my phone. Sadly Slack has become a fairly critical part of our communication.
41 comments
[ 7.5 ms ] story [ 141 ms ] threadhttps://news.ycombinator.com/item?id=15597431
https://news.ycombinator.com/item?id=15597387
https://news.ycombinator.com/item?id=15597382
What does that mean?
Building things is hard, mistakes happen, and that's totally okay.
So yes, IRC channels have better availability than Slack.
A service the scale of slack also runs into a whole host of scaling issues that a little intranet IRC client will never have.
Ah, the downside of relying on a third party for critical communication infrastructure when you're a full remote company...
At this time that post has 116 points in 35 minutes.
https://tkcs.in/461W2z0c1M3z
It's concerning/odd for their status page to be affected by whatever infrastructure issue they're having.
Curious: does that even matter, assuming response body is gzipped?