161–170 of 479 posts
Earlier quoted context omitted.
Do you really pursue "inbox zero" on slack? That sounds like a full-time job in itself.
I do. At Walmart. It drives me slightly insane. Wish I could turn that part of myself off more often.
Have never been like this with email though (but email is much higher volume/more individual things to click on... and less interesting :D)
Earlier quoted context omitted.
Um, why? The other day I had a killer headache. Just couldn’t shake it. I did everything I needed to that was time sensitive, then went AFK. I don’t see any reason to be suspicious of others if they do similarly—we all have days when we’re just not at our best for some reason.
To defend @bagacrap, they said they tend to be a bit suspicious. And I am, too, when I hear this weekly from the same person (and when I ask back next day, if she recovered, she asks me "from what"?) I'm all in for more times off for parents, more PTOs, sabbaticala, etc. But come on, having "a cold" twice a month... IT IS suspicious.
I'm with the other commenters who agree in spirit, but would hate the details in the post. Assigned channels where you are expected to post your random thoughts feels utterly dystopian to me. In my experience, "rambling" channels build up organically... as you have a thought, you share it with someone relevant, not just drop it into a channel and see who reads it. Over time, small group chats evolve naturally, and as…
Yep this. Just make a "random" channel, where most people keep notifications off, and use it for everything random, from lunch invitations to "i'm selling olive oil", etc.
I'm with the other commenters who agree in spirit, but would hate the details in the post. Assigned channels where you are expected to post your random thoughts feels utterly dystopian to me. In my experience, "rambling" channels build up organically... as you have a thought, you share it with someone relevant, not just drop it into a channel and see who reads it. Over time, small group chats evolve naturally, and as…
When I'm considering a refactor, I write up my thoughts in English (which often helps clarify things rather than focusing in code at first). And then I point the rest of my team, to the post and say something like, "I'm going to tackle this next Wednesday, let me know if you see anything wrong with the approach". People who care and have options can chime in, if they're too busy they can ignore it. But everyone is given the chance to comment.
But where I find the real value is when I'm working on a new algorithm or analysis approach. Our internal blog software natively supports LaTeX math blocks (like GFM), so I can write out my algorithm ideas using formal math notation. I've pre-found a bug or bad idea many times just by translating my English into LaTeX. I actually find the expression of those ideas in a blog post the key tool to solidify ideas before I code them.
I'm under no illusions that most of the team even reads what I write, but the work of formalizing it for semi-public consumption really clarifies my thoughts and keeps me from spinning too much while I'm actually writing the code.
These aren't super formal academic quality publications, more like semi-formal ramblings, but I think the difference between hitting "publish" vs just typing in a channel slows me down enough to really think through things - and those who do end up reading them are reading slightly more thought out idea than a stream-of-consciousness rambling which means they'll get more out of it too.
I'm with the other commenters who agree in spirit, but would hate the details in the post. Assigned channels where you are expected to post your random thoughts feels utterly dystopian to me. In my experience, "rambling" channels build up organically... as you have a thought, you share it with someone relevant, not just drop it into a channel and see who reads it. Over time, small group chats evolve naturally, and as…
“I see you’ve only had 15 rambles this week” “Isn’t 15 the minimum?” “Well, yeah, if you just want to do the bare minimum. But look at Todd over there - he has 37 rambles” “Well if you wanted people to have 37 rambles why wouldn’t you make that the minimum”
I'm with the other commenters who agree in spirit, but would hate the details in the post. Assigned channels where you are expected to post your random thoughts feels utterly dystopian to me. In my experience, "rambling" channels build up organically... as you have a thought, you share it with someone relevant, not just drop it into a channel and see who reads it. Over time, small group chats evolve naturally, and as…
> I'm with the other commenters who agree in spirit, but would hate the details in the post This seems to happen a lot: Someone writes some highly exaggerated career advice that has good intent at the core but turns into overly weird suggestions by the end. They might be trying to be memorable or to make an impact by exaggerating the advice. Then some people, often juniors, take it literally and start practicing it.…
Earlier quoted context omitted.
I do tend to be a bit suspicious of the one-day "under the weather" events. However I do think we need to make extra room for parents (I am not one, yet). I'm going to need a doctor who's younger than me when I'm 80+ Folks could always just disappear instead of announcing these things, but is that better? And as a senior on my team, I over announce certain stuff to let the other team members know that WLB is ok.
Interesting. When I do not feel up to the task of working, whether it is a physical, mental, emotional, spiritual, or arbitrary cause, I use one of my provided PTO days and email the team a short "I will not be showing up to work today" message, without explaining the cause. I similarly don't bat an eye when a coworker takes off for whatever reason. We're allotted PTO. Why jump through hoops to convince ourselves tha…
I don’t think I’ve taken a “sick day” once since going remote over 5 years ago. But for the last 10 years I’ve been leading initiatives first at startups and then at consulting companies and I mostly have autonomy and the trust to get things done.
Earlier quoted context omitted.
Indeed, I, as a fully remote, probably overworked person, sometimes wonder if I'm a loser just because I never * pick up Becky from school * feel under the weather today so I'll be offline and "take it easy" (never hear about me anymore today) * sorry "traffic jam" (10:00am) * sorry "train canceled" * will leave a bit early (2pm) for [insert random reason] appointment While all these can be completely valid reasons,…
I do tend to be a bit suspicious of the one-day "under the weather" events. However I do think we need to make extra room for parents (I am not one, yet). I'm going to need a doctor who's younger than me when I'm 80+ Folks could always just disappear instead of announcing these things, but is that better? And as a senior on my team, I over announce certain stuff to let the other team members know that WLB is ok.
Unless you are the one paying for that person and they are not performing as by contract, even if someone needs an extra day off to chill, you should be happy they do take it as it creates an environment where you also could take it off if you so wished.
This is a great place to use threads.
If someone wants to ramble, you say “Starting a thread to think through ” in the project channel and then you put your follow-up chats in the thread. This way it only occupies a single line and notification (for those who have it enabled) but keeps it in the right place.
Creating excessive numbers of channels is a common small company mistake that they’ll come to regret later. Every growing company I’ve worked for has gone through a “let’s create channels for everything” phase followed later by a “we’re all so burnt out from being in 80 different channels” phase. Creating a separate channel for every person of a project will scatter the discussions and add excessive cognitive load for juggling channels.