slezakattack

Interesting post but was really hoping to understand why some of my saves wouldn't transfer to other 360 consoles. Back when the "red ring of death" was more common, I would be issued a replacement console. When I snapped my hard drive back in and turned on Ninja Gaiden 2, I wouldn't be able to continue my progress. I had the unfortunate luck of this happening several times to me and I eventually quit playing that game.

Years and years later, I worked with someone who used to be at a gaming company and he claimed that apparently it was a quality assurance requirement from Microsoft in order to be published..

You're not wrong. However, even if you make an all-cash offer and remove every single contingency, you're still looking at roughly 2 weeks minimum to close. You're making the assumption that title companies are competent (they are not) and move quickly (they do not). Wire transfer takes a few days, need to find a notary to sign all of the closing docs, and title companies are slammed with all of the other home purchases happening as well.

Like most things, it depends what your web application is doing. I've been working in Erlang professionally nearly 6 years, and I'm not super convinced it's great for building web apps. If you want to utilize the Erlang VM, many people have found Elixir/Phoenix to be super helpful in building their web apps. I encourage you to check that out if it piques your interest.

As a seasoned Erlang developer, it's really foreign to me that people can go so far as to never need a GenServer since they are everywhere in Erlang. Have you had any experience with ramping up an Erlang engineer to use Elixir? After interviewing an Elixir dev for an Erlang position, it was interesting that so much of what they used in their day-to-day abstracted away the components of OTP and the Beam. Didn't really have a firm grasp of supervision trees, process linking vs monitoring, etc.

I've also seen the bait-and-switch with recruiters. Many years ago when I was young in my career, I decided to respond to a recruiter who worked for a recruiting firm. We had a good talk and there was a company he was working with that I expressed interest in and felt I was qualified for.

Nope. He kept pedaling this small, 10-15 person startup to me that I clearly wasn't qualified for and honestly was not interested in as there were some red flags. The commission must've been fat cause he didn't pitch me any other company and kept "circling back" if I changed my mind about them.

I felt the same way when I read they waited for 20 minutes. Unfortunately, it doesn't seem to be stated if the cops initially showed up with vests and guns drawn or if more showed up after failure to comply. If it was the former, I could understand the shock and cloudy judgment experienced by the scientist when you've realized your house is under siege.

What was particularly fun for me as a kid, regarding video game rentals, was that consoles like the N64 and SNES had saves on the cartridge and sometimes you'd pick a game with a save slot where someone already unlocked a huge chunk of the game. Hitting the "jackpot" with a cartridge that had everything unlocked made the game even more fun. Suddenly that one level I was stuck on in Donkey Kong Country has been passed and I'm on to checking out other levels..

Yes, I've seen this as well and from my observation, it seems to boil down to company culture and a lack of product direction. A company that refuses to accept that errors and faults happen tends to permeate into the code. A lot of people that work on the product side will say "I want us to have no failures" without understanding that things simply WILL fail at times and we need to understand what the user experience should be if this were to happen. This is especially true of external services that you have no control over (i.e. the usage of a push notification system).

I'm simply curious if the protocol was ever brought up in discussion and if there was a conscious decision to not go that route due to product needs.

I'm not going to speculate on what the advantages/disadvantages would have been as I honestly have no idea. I suppose if a competing product comes out that is XMPP-based then maybe we'll have some good comparisons. ;-)

I'm curious if Slack ever considered using XMPP in their stack for core chat? As an outsider, it seems XMPP would fit like a glove (even signing in to a work "domain" screams XMPP).

There's no hard-and-fast rule on this but generally junior projects are isolated where you may only have one stakeholder. Growing into a more senior role, your actions generally have greater breadth that affect more teams/clients/orgs. Technical chops are worthy but I can guarantee that your stakeholders would rather have amazing communication for things like progress, deployment, etc. than how efficient or beautifully written the project is.