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.
If you ask questions that are relative to the job and something you might run into or someone asking you for help, then that is different.
But, I've personally never been asked these kinds of questions in a live coding/whiteboarding session. It's always brain teasers or some sort of algorithmic problem. Usually they are things that aren't necessarily hard, but are about as far from everyday work as you can get.
Is it amazing that they can't do them at all, or they can't do them in the spotlight in a totally unfamiliar? I have a strong feeling that most of the people you think fall in the former are actually in the latter.
Yes, the solution might be a couple nested for loops. But if it's a new question to the interviewee, then they don't know the solution yet.
Sorry, but I don't see how this is relevant to what the other person said. Important or not, if you're too tired for sex then wtf are you going to do with an infant?
I mean, the iPhone was kind of the only good smartphone that was actually a "smart phone", when it came out. There was nothing even remotely comparable until they were a few years into Android. I remember even the first few lines of Droids that came out and they were substantially inferior products.
Redux definitely adds an extra layer of complexity to a project and a lot more boilerplate. That is what lead to Dan's famous blog post "You Might Not Need Redux" from 2016.
EVE can actually be played very casually. The grind is for money, but you can supplement that with real money. I know that sounds really bad in a world where every mobile game is a P2W nightmare, but it works for EVE. You cannot P2W EVE. Most people don't use real money, once you get to a point where you understand most of the game it's not really required. The only significant time sink Eve requires is learning how it works because it's an extremely complex game.
EVE has a really good Free to Play system in place and I definitely recommend checking it out.
I would not suggest getting an account then trying to throw a bunch of money at it until you really understand what that money is used for. We once killed a new 15 day old player who was flying high end implants that buffed their shields, in a ship that was armor tanked. In real money terms we probably blew up $40 that they were using completely incorrectly. There were 3 of us flying a total of less than $5 worth of real money ships. It's a very unforgiving game, but most players are nice to new players and we ended up giving that person a lot of advice on what they did wrong, what they can do to fix it, and which direction they needed to go to get better. We throw money at newbies often if we kill them, but since this one was flying several times more than our entire fleet we figured it was pointless. To put it into perspective, I've been playing for about 4yrs total spread across 14 and the most expensive thing I've flown cost about half as much as what this person was flying.
For the other payers: it was a full High-Grade crystal set in a blingy Apoc we found ratting in a Haven, so you know he was injected too. Almost 7b total on zkill.
You're making some kind of distinction of a web developer just being someone who splices designs in Dreamweaver or something.
It's not.
Every web developer or frontend engineer I've ever worked with in the last decade has been a software engineer in every sense of the word. Focusing on web based applications or architecture is just what they have chosen or fallen in to.