cereal_cable

I would only assume the other side of this entire conversation, from the recruiters view is that it is also a numbers game. Recruiters are effectively sales jobs just a different contract to close on. Get enough leads and eventually they close.

I'd expect that don't care if the resumes are perfect. There's very little lost for being wrong.

Quality can also become it's own trap as the entire org chases metrics aimed at quality. Soon you have loads of brittle tests that likely aren't adding great assertions but you have code coverage.

Because that doesn't work soon you keep adding layers upon layers to reduce the risk and your time to delivery suffers.

All knobs have consequences and long term they can really compound. The balance of picking quality over features isn't something I've seen done amazing. I'd like to work somewhere that could pull it off.

There's more to life than a job as well. I've stayed at a job for the comfort of not needing to add to my or my families plate while my wife was in grad school. It was absolutely the right choice.

I've also had a job that I left because I wasn't enjoying because of a lack of challenge and lack of management backing for the projects I was working on.

Life isn't purely black and white and my reasoning is pretty simplistic. There are vastly more complex situations than just my wife went to grad school.

Everyone I work with is constantly badmouthing Teams. It's buggy and flakey and they killed Linux support which my company actually made use of. Either way, it doesn't matter since it's bundled. Literally killed any chance of competition getting a fair shake at our usage.

Teams doesn't have to be better, they're just bundled.

I can't imagine why any ISP would do such absurd things when in my experience you're given sufficient resources on your first allocation. My small ISP received a /36 of IPv6 space, I couldn't imagine giving less than a /64 to a customer.

I dived deep into RSS feeds and decided to really just try and follow content creators instead of relying on a single site.

It's been a process.

We bought a Maytag set because it's capacity was larger than the Speed queens. I've never been more angry at a company. We threw in the towel and junked them they were so bad. Literally couldn't give them away bad. Apparently everyone I knew either already knew or trusted my experience so I couldn't unload them.

Now, we have speed queens and I no longer am using buckets to fill our washing machine, don't have to babysit it, it doesn't randomly jump in the air suddenly as it's gotten out of balance for the 4th time in the day. I would never willingly wish that upon someone.

There's also a giant speed difference plus the fact that a car will decelerate even if uncontrollably for basically any mechanical failure. Even at speed vehicle accidents are quite safe comparatively to a plane that has lost its ability to fly. A plane tends to have all or nothing incidents while vehicles have lots of accidents with a wide variety of severity.

Naturally that tends to push aviation towards avoidance of mechanical issues and on cars we are much more tolerant. I've seen people driving cars with their door duck taped on!

How much of our ingredients come in plastics though? I'm thinking about how all of my condiments and oils come in plastic containers. Heck even my potatoes come in a plastic bag as well. It's near impossible to avoid plastic contact right now.

I bought a new Maytag washer/dryer when I moved. We were so frustrated by it that we decided we would replace them and then give them away. Had friends who were interested but, they couldn't get them to work at all either. They were literally junk straight from the factory. We had them serviced under warranty as well, just a huge waste of time and money.

This has to be a race to the bottom and yeah, technically somehow it did sort of wash our clothes, but it was a huge hassle.

WFH for me gives me more flexibility in the childcare options. It doesn't eliminate my need to have my family needs met. I can't just watch my toddler and not work.

However, I can be more flexible and drop my toddler off at daycare after my daily stand-up since he mostly is fine watching shows during that. Then I pick him up right before his nap time. This scenario is awesome, but albeit just temporary until my family resumes our previous arrangements that was interrupted by a surgery.

My responsibility hasn't changed and I'll fill in randomly throughout the week as needed but, now I just have extra flexibility that I would never have in an office. Even comparing it to a small city, living in the suburbs easily meant a 15-30 minute commute and wouldn't allow me to have the opportunities I have now.

No, I won't return to the office and I'm not sure anyone will actually convince me to do so. I'm mentoring interns and juniors developers without any concerns remotely.

I love the mandates to RTO to only get onto Zoom or Teams meetings with people in multiple timezones and offices all traveling to the office to fulfill the RTO mandate and yet...the only thing that changed was the blurred backdrop.

Agreed, but having a door meant you could put the "do not disturb" sign up. Of course that's pretty specific to your companies culture, but if someone closed their door at my office, I'd stroll around later.

One of the biggest benefits of course is that you have a lot less sound travel. Doors open and you'll still be able to have a neighbor that has an open door meeting, phone call, etc and it won't interrupt you.

After moving from a private office with a door to a team space, I missed it severely. Now I'm WFH and when my kids aren't home generally my door stays open.

This happened with copper lines for telephony providers. Incumbent Local Exchange Carriers have to provide access for Competitive Local Exchange Carriers to enter the market and break up their monopoly. This effectively made DSL and T1s available via CLECs as they could acquire access to a copper circuit directly.

Internet has yet to be regulated that way and fiber lines aren't considered the same as those copper lines.

Also, fiber to the home is done using most often a PON system purchased from a specific vendor and is a time shared medium. You might only get 1Gbps service but you also aren't getting 100% of the fiber to yourself. The home side device will filter information from your neighbors for instance.

There's always ways to do this of course but, it wouldn't be as straightforward as patch the fiber from your home in the same way that they did with copper lines.

Sounds like standard operating procedures these days.

Technology doesn't seem to be the sticking point that keeps people at particular streaming sites. It's the content that rules the decisions about which service, at least based upon all of the discussions amongst the internets and friends and family.

Plus layer 2 switches when they don't know the destination port will flood. With so many hosts that would be absolutely horrific.

I've seen computers at moderately sized LAN parties (talking 100 nodes, far from the large or even massive events) that were literally crippled by the broadcast traffic. At some point the flooding and layer 2 discovery (ARP) would do the same as well.

Limiting the broadcast domains with layer 3 really makes the Internet possible. Sure, you can have less overhead and simply do layer 2 only, and really it is completely possible. It's just such a rare use case that it in practice isn't important enough to actually do.

A switched port learns the Mac address for packets sent into it. If port 1 sends a packet with Mac a, the switch associates that address (a) to port 1. When another node sends a packet onto another port with the same mac, say on port 2, the switch will move the learned address a to port 2 and remove it from port 1.

When a switch has learned a mac address all traffic destined to that traffic would be immediately switched to that port. If the switch has no record for that specific mac address it floods all ports except the ingress port. This is expensive and means other devices receive traffic that isn't intended for them so they waste time dropping it.

So in networks that have no protections against those attacks then this could very well be a problem if there are multiple access points and the two nodes are on different access points.

I often find that the tooling I have at work helps speed up the development of more complicated solutions. So saying that FAANG solutions are easy to use and you can be fast at is easy when you have that FAANG support. Even just non-FAANG but large enterprises allow for that, but for startup's is easy to forget how the environment (including tooling) helps speed up all of that work immensely.

So yeah, I find a lot of the more complicated solutions to be simple, but mostly because it's well supported and not by just me.

I'm pretty confident you're wrong there. The state param mentioned is a part of PKCE to verify to the originating source code that you've received the code. The original source of the request then can use that state and compare it to the starting request (or even use it to look it up) and then generate a verifier code to send to the token endpoint along with the code to exchange for tokens. This attempts to prevent a MITM attack by keeping something secret.

I believe what you are actually wanting to discuss is the aud claim, or rather the audience claim.