mawburn

It's on there. You have to scroll.

> which is about ~110k a year

$310 * 5 days a week * 52 weeks a year = $80,600

I used to name projects of funny names, but then I started realizing that I had no idea what other people's cute names were for their projects.

We have one in our company named right now named Harbinger, neat name... but wtf is it? Boring names are boring, but they tell other people, and future you, what they are or do.

My favorite interview experience was when I passed a live coding exercise on Monday and had time to optimize, then completely failed the exact same problem on Friday with a different company because my nerves hit me.

Please don't move the goalpost. My comment was responding to your comment about average tenure, not unions specifically. You didn't raise any questions on how unions played into average tenure or provide any example of how they could help.

Its employee choice. People get bored, they get tired of processes, and there are plenty of companies willing to hire them that will allow them to try something new, do something different, and deal with different processes.

Maybe unionization needs a disrupt? I'm not against unionization in a lot of industries, but it just doesn't make sense in its current form for the tech scene or any other high demand position. It feels like an outdated mechanism used for people who were happy to sit in the same role, doing the same thing, for 45yrs.

That could have been it, but when they pivoted they had a very complete beta product. Probably more to do with investor pressure or something along those lines.

I think Blue Mars was started when there was a huge surge of them after Second Life took off. Even Google and others were developing something in the space.

There was an up and comer a few years back called Blue Mars, that was shaping up to be something really cool. It allowed content creators a great deal of control over their virtual landscapes.

But, for some reason they abruptly changed direction to some kind of weird mobile avatar creator on mobile and shut down shortly after.

Well, we went through the transition at my last job so I kind of have some incite. We had 3 or 4 people on my project who had came over from Invision, who are a fully remote company and I have a good friends at other well known fully remote companies that I gleamed things from to help us transition from 0 remote company to a fully remote project team (50ppl-ish).

1. Every meeting should be video first. Going without video should be extraordinarily rare. Even if that's just an impromptu meeting with 2 or 3 people. Kill conference phones completely. Get used to screen sharing. Good reliable tools like Zoom are invaluable. You miss a lot from body language and facial expressions if you use audio only, which will fix your major issue. It also makes people feel more included and that the people working somewhere else are actually real people and not just voices. Make good use of Slack video

2. Every meeting should be able to be taken as remote, even if that means just from your desk (or personal meeting room if you're in an open office). This means that the people who are in a conference room must be on video with an open mic, unless there is uncontrollable excessive background noise or something. No cross the table talk on mute.

3. Don't be afraid to make temp rooms with multiple people when you have conversations on Slack (or whatever you use), it'll help more people get involved as if you were talking at someone's desk.

The first 2 things are extremely important. Invision has recently released some blogs about cultivating a good remote culture that are pretty good. I don't have any links handy, however but it's worth a look if you're interested.

Having people work remote in a non-remote culture is a completely different experience than working with a fully remote culture.

If the entire team/division/org doesn't fully embrace it, it usually just doesn't work. That doesn't mean everyone had to be remote, either.