Earlier quoted context omitted.
With async communication it’s hard to know if everyone got it. If you’re in some kind of synchronous meeting, everyone knows what everyone knows, and it’s usually more clear if people are confused or come from very different POVs, or don’t have the time, attention or other resources they need to get things done. Async communication often feels like shouting into a void, hoping that the right people saw it in time and…
> If you’re in some kind of synchronous meeting, everyone knows what everyone knows, I feel like while that's generally true, it depends. Not only because you might underestimate my ability to sleep with my eyes open. I've seen quite a few projects where in-person meetings were either badly planned, went overboard in terms of frequency / number of participants, or people were simply inattentive for other reasons. The…
Gitlab's Guide to All-Remote
221–230 of 254 posts
Re: Gitlab's Guide to All-Remote
#222How do people whiteboard remotely? This is a big problem for many development teams. Sometimes you just want to open a blank whiteboard and scribble some boxes and brainstorm or troubleshoot some things. The whiteboard is an inseparable part of nearly every meeting. And no, remote "canvas" whiteboards don't work. They end up looking like this: https://cdn.drawception.com/images/panels/2015/3-3/jLndYAfNf... . Is there…
Re: Gitlab's Guide to All-Remote
#223Our Company Handbook for Remote Work https://mobilejazz.com/company-handbook-pdf/ Other HN members have pointed out previously, that it looks like a landing page where you need to leave your e-mail address. You don't. You can download the PDF from here directly.
Why do you have it as a PDF hidden behind a call-to-action reminiscent of a sign-up though? Turn it into a website, that'll make it a lot more accessible - assuming getting people to read it is the goal, of course.
Re: Gitlab's Guide to All-Remote
#224Regarding the principles: >> 3. Writing down and recording knowledge over verbal explanations. 4. Written down processes over on-the-job training. 5. Public sharing of information over need-to-know access. 6. Opening up every document for editing by anyone over top-down control of documents. 7. Asynchronous communication over synchronous communication. These remote work principles have the direct, or side effect of b…
Re: Gitlab's Guide to All-Remote
#225I have delayed sleep phase disorder (sleep-in late; fixed by camping / sunlight) and live in a van in (roughly) CO, so the perfect job for me is working remote with a team in San Francisco. I currently work in-office with a fairly major start-up.
Re: Gitlab's Guide to All-Remote
#226Do any companies think they will keep doing remote after COVID? I have delayed sleep phase disorder (sleep-in late; fixed by camping / sunlight) and live in a van in (roughly) CO, so the perfect job for me is working remote with a team in San Francisco. I currently work in-office with a fairly major start-up.
Re: Gitlab's Guide to All-Remote
#227How do people whiteboard remotely? This is a big problem for many development teams. Sometimes you just want to open a blank whiteboard and scribble some boxes and brainstorm or troubleshoot some things. The whiteboard is an inseparable part of nearly every meeting. And no, remote "canvas" whiteboards don't work. They end up looking like this: https://cdn.drawception.com/images/panels/2015/3-3/jLndYAfNf... . Is there…
I've often pushed for having a personal white board just do dump out my own ideas for both personal and group settings. For lectures, we've just pointed a camera at the whiteboard. This is problematic because many whiteboards are shiny and you have to get most web cameras pretty far away to frame the whole thing. I've seen some experimental software that will detect markers and composite it over the image (for when people stand in front of the whiteboard--another common issue) or just increase the contrast of the writing.
I think it's a mix of new tools and new software instead of just new software using the same mouse+keyboard+Internet.
Re: Gitlab's Guide to All-Remote
#228Earlier quoted context omitted.
I actually found remote whiteboards to work quite well when used with a proper pen tablet (like a Wacom Intous). Downside of that is of course increased cost, as equipping everyone with one of those isn't that cheap. It also takes some time to get used to using those, but for permanent remote situations this is about as close as you will get to in-person whiteboards. A less sophisticated variant that works well for a…
I got a used Wacom Bamboo (very decent) for $20. Though my handwriting makes it a lot like GP's picture :)
Cintiqs, iPads, and other tablets don't require this adaptation, though. I've also been kind of amazed how well people can write using mice when forced to (from watching MOOC classes).
Re: Gitlab's Guide to All-Remote
#229Do any companies think they will keep doing remote after COVID? I have delayed sleep phase disorder (sleep-in late; fixed by camping / sunlight) and live in a van in (roughly) CO, so the perfect job for me is working remote with a team in San Francisco. I currently work in-office with a fairly major start-up.
I see so many people making the point that they have some syndrome and so they need x, y, z in a job. Valid, I'm sure, personally well-considered, true and everything, but still, indicative of a person who's problems are more important to them than the ones the company is hiring for.
Seems rational unless I'm actually trying to do the 'selling myself / interview' part.
Re: Gitlab's Guide to All-Remote
#230How do people whiteboard remotely? This is a big problem for many development teams. Sometimes you just want to open a blank whiteboard and scribble some boxes and brainstorm or troubleshoot some things. The whiteboard is an inseparable part of nearly every meeting. And no, remote "canvas" whiteboards don't work. They end up looking like this: https://cdn.drawception.com/images/panels/2015/3-3/jLndYAfNf... . Is there…