Live data from Hacker News

If you're remote, ramble

stephango.com

351–360 of 479 posts

Re: If you're remote, ramble

#351
post #132

Let me share a personal story. Back in 2014 when I was working at Cloudflare on DDoS mitigation I collaborated a lot with a collage - James (Jog). I asked him loads of questions, from "how to login to a server", via "what is anycast" to "tell me how you mitigated this one, give me precise instructions you've run". I quickly realised that these conversations had value outside the two of us - pretty much everyone else…

> I collaborated a lot with a collage - James (Jog). I asked him loads of questions, from "how to login to a server", via "what is anycast" to "tell me how you mitigated this one, give me precise instructions you've run". Hi, that's me! There were definitely a lot of fun conversations. I liked that a culture of internal blogs became a thing too. It was good to see people brain dumping their experiments and findings.…

Always funny to see these sort of missed connections on HN.

> internal blogs

In my personal experience the problem is the total lack of writing culture at non-premiere companies.

Put differently: unless you’re working on a great team at a great organization roughly 90% of people cannot be expected to write/read well as a component of technical collaboration. Any thoughts on that? I may just be too cynical

Re: If you're remote, ramble

#352
post #96

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.

Yeah, children bring home all sorts of vile stuff that'll knock you out for a day. And sometimes, it'll just be something random. This morning I had - let's call it "digestive distress" to avoid describing the horrors - that would have definitely meant I wouldn't be able to work if it were a weekday, but I think I'm over it now, and I'll be showing up tomorrow just fine.

Re: If you're remote, ramble

#353

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…

> Assigned channels where you are expected to post your random thoughts feels utterly dystopian to me.

It all comes down to company culture.

Re: If you're remote, ramble

#355
> All the ramblings channels should be in a Ramblings section at the bottom of the channel list. They should be muted by default, with no expectation that anyone else will read them.

I hate that Slack and other apps have nothing in between "mute" and "tell me immediately if I have anything unread". Many channels I want to know if there are new messages and read, just not by the second. If it could batch them up and only show them as unread after lunch, perhaps.

Re: If you're remote, ramble

#356

I put my work ramblings in daily journal notes in Markdown files in a git repository. Unfortunately, I don't spend the time to then ensure that they're accessible to my co-workers - and given the amount of value that I would get if they did that, I should do it myself. Also, I'm very glad that I don't work in a place with Slack/chat culture. I really like the idea of making your ramblings available, but the thought o…

Try using a static site generator like Jekyll or Hugo with GitHub Pages to automatically publish your Markdown ramblings - minimal setup, preserves your workflow, and gives teammates a simple URL to bookmark.

Re: If you're remote, ramble

#357

This is what things like "water cooler chat" looks like for remote-first. This is the fundamental difference between what a healthy remote-first company starts to look like versus the soulless version historically in-person companies try to sell. To the author, thank you for sharing your version of the dynamics.

Our ramble channel is literally called "Water Cooler". After reading this post I will ramble in there more often, I think.

Re: If you're remote, ramble

#359

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.

Re-reading your own message should definitely be a bell for you to notice either your lack of trust in others and/or your twisted perspective that work is the goal of life. 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…

I’m neutral on this topic between you and GP, but I do think you’re discounting the fact that distrust can be legitimate. You’re assuming that we should trust blindly, it seems.

Re: If you're remote, ramble

#360

I put my work ramblings in daily journal notes in Markdown files in a git repository. Unfortunately, I don't spend the time to then ensure that they're accessible to my co-workers - and given the amount of value that I would get if they did that, I should do it myself. Also, I'm very glad that I don't work in a place with Slack/chat culture. I really like the idea of making your ramblings available, but the thought o…

Try using a static site generator like Jekyll or Hugo with GitHub Pages to automatically publish your Markdown ramblings - minimal setup, preserves your workflow, and gives teammates a simple URL to bookmark.

Oh, that's a great idea - thank you.
Post reply on HN