71–78 of 78 posts
Earlier quoted context omitted.
Ideally, only results should matter. But 'Zzz' somehow reinforces the default assumption that a remote worker will try to be paid for slacking off. Now, I am going back to bed.
I mean, the product itself is named Slack...
> Our only office is Slack. You mistyped Mattermost :) Seriously, no reason to share all your company inner workings with a random 3rd party when it takes literally 5 minutes to set up a completely private (and also free!) clone of the same.
I might argue that Slack has no interest in anyone's inner workings. I've been at companies building relatively uninteresting products that treated Github like it was the same as emailing source code and server logins to the competition. I could be wrong, but I have never heard of a single instance of a company on Github having code stolen because it was on Github. I have heard of many companies who have had their in…
Risk analysis: using online DVCS/bugtracker/chat service you are one compromised password away from letting an attacker read the whole contents and potentially alter them. Many of those passwords will be stored in browser. Browsers are known for being softer targets compared to servers, generally speaking.
Contrast this with an on-premise services: You still have login credentials but also require people to badge-in to access the building and login on the desktops or start a VPN (often requiring creds and 2fa).
Earlier quoted context omitted.
I force myself to attend as many meetups as possible. I find it beneficial to just attend and even if you have no interest in the talk, it's nice being around other people who potentially are
I tried that, but it's hard, I'm not a very social person and the meetups I attended here were not very interesting...
Earlier quoted context omitted.
I tried that, but it's hard, I'm not a very social person and the meetups I attended here were not very interesting...
I like to go on hikes with outdoors-oriented Meetup groups. I like hiking anyway, and I frequently find someone to have an interesting conversation with. If I don't, no problem, it's still fun to do the hike anyway even if I don't talk to anyone.
Earlier quoted context omitted.
Yes I'd be interested to hear more about that setup too!
Basically all of us are async. A few of us in the bay area,a few on the east coast, 1 in australia, 1 in eastern europe, and a few in japan/korea. We have 1 weekly standup at 3:00 PM PST which is ~8am Japan Time (where I live). All of our messaging is async. Most people manage themselves. Tasks tend to be longer sprints. Half of our team has kids. Work is more independently scheduled. We all collaborate asynchronousl…
it is definitely great to meet in person, to shake hands, grab a coffee together, etc. but what is the value, professionally speaking? Years of socialization training stemming from childhood to gauge whether it's really worth interrupting people. I do enjoy the opportunity to do remote work, but even in the office, I'm finding an unstated expectation that I should always have a second pair of eyes on my slack notific…
I work at a 100% remote office. We don't use Slack, or really anything other than Google hangouts. It is pretty easy to just say "Got a sec?", as you would in person. Then type, call, share screens, whatever, when you both have a moment. It may seem different on the surface, but it really is the exact same communication as you would have in person... you just need to ask. And much of the time, real-time responses are…
it is definitely great to meet in person, to shake hands, grab a coffee together, etc. but what is the value, professionally speaking? Years of socialization training stemming from childhood to gauge whether it's really worth interrupting people. I do enjoy the opportunity to do remote work, but even in the office, I'm finding an unstated expectation that I should always have a second pair of eyes on my slack notific…
Yeah, this is why I still prefer IRC over Slack and most other team chat systems. I hear a lot of people suggest them because of missing messages with IRC, but I actually think the missing messages is a feature. A ping on IRC to someone that isn't there is a bit like walking by someone's office and noticing that they aren't there. I don't want my phone to notify me immediately every time a team chat message goes thro…
No, it's absolutely not like that. The use case for "not dropping messages" is that you send a message and know they received it. You don't have to remember it manually, you don't have to introduce another chat system just to asynchronously remember to resend messages later. The other guy can respond at their convenience. Dropping messages would make the application a critical failure for any serious business uses. There are lots of features to mute notifications per room or for time durations.
Earlier quoted context omitted.
Yeah, this is why I still prefer IRC over Slack and most other team chat systems. I hear a lot of people suggest them because of missing messages with IRC, but I actually think the missing messages is a feature. A ping on IRC to someone that isn't there is a bit like walking by someone's office and noticing that they aren't there. I don't want my phone to notify me immediately every time a team chat message goes thro…
> a bit like walking by someone's office and noticing that they aren't there. No, it's absolutely not like that. The use case for "not dropping messages" is that you send a message and know they received it. You don't have to remember it manually, you don't have to introduce another chat system just to asynchronously remember to resend messages later. The other guy can respond at their convenience. Dropping messages…
Having multiple chat systems is ok, if they actually serve multiple purposes.