Comments URL: https://news.ycombinator.com/item?id=49294044

Points: 3

# Comments: 0

University graduates are often considered min-bar for white-collar work hiring, so if it takes 4 years to train someone, how are people supposed to decide on a career path when it takes less time than that to completely alter the workplace?

My daughter is entering her first year of nursing, a career path that she is greatly looking towards. Who says in 3 years that robotics companies don't actually deliver on their promises and completely up-end the care industry? While I think that unlikely, it's not like people aren't trying to automate nurses away.

I would always get a chuckle out of seeing some poor soul waiting 3 hours to go down a few floors after work, only because I failed to add stairs to the lobby.

It was incredibly fun, but afterwards driving my car home I felt like the driving experience wasn't "real", and I had to put more conscious effort into my driving than usual to remain a safe driver. It took a few hours to wear away.

(This was a very distinct experience from what I have felt when binging a VR game like Half-Life: Alyx at home, where I get urges to teleport-move around my house and my hand-perception is off).

But people gotta eat and all so who am I to blame.

Each team has 4 attempts to move the ball forward 10 yards, where if the ball moves >= 10 yards they get a fresh set of 4 attempts. These are called "downs".

If the team has any downs left when they kneel then they can maintain possession of the ball and can thus run out the clock. Most (all?) of the time the teams end the game even if there is time left on the clock.

Note that either team can call a timeout pre-snap which freezes the game clock. Certain plays also result in the game clock freezing between plays. There is also a 2-minute warning at the end of the 2nd/4th quarter that also freezes the game clock.

IMO clock management adds a very interesting strategic layer to NFL football.

"Cracked by The Vulture" was something that I was very used to seeing upon booting up a game.

I have to admit the game is a little overwhelming but maybe I need to stick with it a bit more.

Part of PoP's charm is that the game is very simple, yet the parry mechanic has nuance - you can buffer parry/attack/parry/attack/... sequences and the timing is just a bit faster than normal enemies, meaning you can wear them out (these fights have a very Errol Flynn Swashbuckler feel to them). Eventually your attack lands before they can begin their parry animation.

Later in the game you meet enemies that hit faster than you can respond to with a parry, so you need to change up your tactics.

I only realize it now but it had some very unique game mechanics that even today you don't see very often (ok maybe that's a bit of a stretch but the mechanics were novel to me back then):

- Notably you have 60 minutes to finish the game. Dying doesn't reset the timer, so there is constant pressure to keep moving.

- There is a satisfying parry mechanic. This is still rare to see in 2d platformers.

- Incredibly smooth animation. This could be nostalgia goggles but the rotoscoped animation really stood out compared to other games of the era.

Just today I had my agent diff two logs to find a very nitpicky difference that was the cause of a problem, I pointed it at a ADO extension that was having issues, it downloaded the VSIX and decompiled the .NET binary to verify. Based on that information it suggested a workaround which I was very skeptical of, but well it worked.

All of this I technically could have done but I probably wouldn't because it would have taken too long without a clear payoff.

I think they make a great "second device" where you have something meatier to fall back to if something doesn't quite work right. I'm not sure if it's ready to take on the "main device" role just yet. But it's a far far better experience than the Surface RT days.

I run into this with AI-generated PR comments. I think where I work we are still grappling with the "right point", because LLMs can certainly provide valuable feedback, but they are not at the point where they can do so unsupervised, and to do so just feels unprofessional.

And there's another layer where it is even worse when a colleague spends the time critiquing code and someone (or something) replies to the comment with mostly useless filler. It's like being handed a small hand-crafted gift and then throwing it into the garbage in front of them.