Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab's Guide to All-Remote

about.gitlab.com

Post reply on HN
Print view View original

191–200 of 254 posts

Re: Gitlab's Guide to All-Remote

#191

Post by agumonkey »

renchap wrote: post #110
rdsubhas wrote: post #100

How 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…

Excalidraw ( https://excalidraw.com ) just implemented collaboration, making it a free, secure and OSS solution for remote whiteboard :)

give it json graph output and kiss uml goodbye

Re: Gitlab's Guide to All-Remote

#192

Post by slantyyz »

cyphar wrote: post #109
lampe3 wrote: post #105

Earlier quoted context omitted.

The question is why do you need a whiteboard? What problem is the whiteboard solving? Drawing freely with a mouse is something that can be done but also you have tools like draw.io if you need to draw something.

Whiteboards are absolutely indispensable for communicating ideas quickly in a small group of people. It's effectively just a bigger (and easier to erase) version of grabbing a scrap of paper to scribble something down when explaining or describing something to someone else. I'm honestly more surprised that this isn't a universally known concept on HN. Scribbling on scraps of paper is something most people in western…

I don't know. A whiteboard alone isn't a solution.

I think it depends on the communication skills of the team.

Anyone who plays some form of "Win, Lose or Draw" or "Pictionary" will quickly realize that most people aren't as good at visual communication as they think they are.

Myself, I've been in too many whiteboarding sessions where the whiteboarder either spent too much time trying to "live bake" their idea on the whiteboard or simply produced an incoherent mess.

Re: Gitlab's Guide to All-Remote

#193

Post by andrepd »

rdsubhas wrote: post #100

How 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…

Wacom tablet? Or even just a plain cheap tablet+stylus.

Re: Gitlab's Guide to All-Remote

#194

Post by usrusr »

lbotos wrote: post #135
usrusr wrote: post #42

Earlier quoted context omitted.

Must be related to employee rights, either something highly specific that is a dealbreaker to them (what would Austria have that Germany has not?) or it's a growing list based on precedence, likely full of permanently encoded biases depending on whoever was the initial candidate.

It's mostly related to employment entity complexity vs. organizational demand for that location. To operate legally as a business in most of those countries on that list adds complexity that leadership has deemed "not yet". Doesn't mean forever, just means, not yet. I've seen countries come and go off of the list. Source: 3.5 years at GitLab.

Thanks. So it's a growing/shrinking list, because there surely are a lot of even smaller countries that would be added if something applied.

Re: Gitlab's Guide to All-Remote

#195

Post by whoisjuan »

globular-toast wrote: post #154

Gitlab's remote manifesto speaks to me in so many ways. I'd also love to work for Gitlab anyway. But, alas, I don't know Ruby on Rails and I think it's too late for me to gain the proficiency that I'd require for my expected salary from Gitlab. Are there any fully remote companies doing Python?

If you know Python you can easily learn Ruby. Not hard to do that transition. Although not similar they share the same idiomatic programming principles drawn from languages like Perl. Also, Ruby was inspired by Python:

"I was talking with my colleague about the possibility of an object-oriented scripting language. I knew Perl (Perl4, not Perl5), but I didn't like it really, because it had the smell of a toy language (it still has). The object-oriented language seemed very promising. I knew Python then. But I didn't like it, because I didn't think it was a true object-oriented language – OO features appeared to be add-on to the language. As a language maniac and OO fan for 15 years, I really wanted a genuine object-oriented, easy-to-use scripting language. I looked for but couldn't find one. So I decided to make it." - Matasamoto.

Re: Gitlab's Guide to All-Remote

#196

Post by quietthrow »

rdsubhas wrote: post #100

How 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…

Google offers something called Jamboard. It’s quite fantastic.

Re: Gitlab's Guide to All-Remote

#197

Post by kndjckt »

rdsubhas wrote: post #100

How 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…

You can share your iPad screen on zoom. I‘ll do sketches that way. Sadly the other person can’t interact with it.

Re: Gitlab's Guide to All-Remote

#198

Post by alkonaut »

flyingfences wrote: post #155
alkonaut wrote: post #76

Earlier quoted context omitted.

They buy your skill at the market rate, and sell the product at the market rate in a different market .

For an all-remote, international company, "the market" at both ends of that process is "the world".

The fact that I make X here while pay is 4X in SF is the only proof needed to show job markets and pay levels are local.

If a SF company wants to hire me remotely, I'll take the job at 1.5X, so they won't pay more than that. The simple reason is this: If I don't want the job at 1.5X the local pay, I my neighbor does, and he's every bit as good an engineer as I am. When they do hire me at 1.5X my current pay, they have bought my skill at the local market rate.

Re: Gitlab's Guide to All-Remote

#199

Post by zackify »

rdsubhas wrote: post #100

How 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…

This is going to be downvoted.... but I have never whiteboarded in my 7 years of professional development. It’s just not how all of us brainstorm.

Rather go try the code that I have ideas for, instead of talking back and forth. Most things I can be verbally told what they want and then I just go attempt it.

Post reply on HN