Sure, some of the choreography wasn’t up to par with modern standards. But the script was actually interesting, whereas the prequels are just an illogical, boring mess.

Check out Red Letter Media’s review for tons of arguments for how bad the prequels are. I agree with pretty much all of their points. And while the original movies also have problems, they aren’t anywhere near this many or this bad.

And the dance!

Except the old movies are much better when compared side by side to the new ones, nostalgia or not.

Hideo Kojima is 61 years old. How old is that picture!?

It’s a school activity, why isn’t the school paying for the materials

I found that the most impractical thing with these was that the user interface for selecting songs was typically “you have 200 songs and I’m gonna play them in sequence, if you want a particular song you must skip ahead until you hear it”. It worked for a 12-track audio CD, but felt like an underdeveloped toy feature when used with MP3:s.

Well maybe many of those communities are actually filled with 14 year olds

When he says “idiot” I could swear I’m listening to Napoleon Dynamite reading the bible.

Yesn’t.

Not exactly what you’re asking for, but Subnautica slowly builds on a primal fear without resorting to jump scares. It’s increasingly unsettling and you start finding excuses to just stay in your habitat to decorate instead of going outside. Possibly the best horror game I’ve played.

Life is strange has elements of it (think Butterfly Effect: the game) during parts of the game, although it gets pretty explicit rather than subtle.

Oxenfree also has elements of it, with people behaving weirdly etc. But it also mostly gets fairly explicit. Still, no jumpscares.

Eating the crispy chicken while thinking of the people who burned alive

It’s a compliment. You’re skilled and valuable enough that the company won’t dare to give you any bullshit for leaving on time.

sometimes, it feels like managers hate engineers

They hate engineers because the engineers ask difficult questions that somebody needs to answer in order to really automate a process, and they take the time necessary to do so.

SQL was explicitly designed to allow “normal humans” to query the database. Nowadays even “normal developers” aren’t able to use it properly.

Oracle has a product called Oracle Policy Automation (OPA) that it sells as “you can write the rules in plain English in MS Word documents, you don’t need developers”. I worked for an insurance organization where the business side bought OPA without consulting IT, hoping they wouldn’t have to deal with developers. It totally failed because it doesn’t matter that they get to write “plain English” in Word documents. They still lack the structured, formal thinking to deal with anything except the happiest of happy paths.

The important difference between a developer and a non-developer isn’t the ability to understand the syntax of a programming language. It’s the willingness and ability to formalize and crystallize requirements and think about all the edge cases. As an architect/programmer when I talk to the business side, they get bored and lose interest from all my questions about what they actually want.

I mean he could say “Hey, I’m going to take you out of your life for a minimum of 8 years, I can’t tell you what or why, but as compensation I’m paying you enough to make you set for life.”

Why wouldn’t they send the best and brightest? Weyland is infinitely rich and has a personal stake in the success of the mission.

The catch is that they all need to run in the same transaction to be unaffected by other things going on in the database and to make updates atomic. A single transaction means a single connection, and ODBC/JDBC has no way of multiplexing or pipelining queries over a single connection.

It’s probably theoretically possible to run some things in different transactions. But with all the different layers and complexity of the code (including third party components and ORMs like Hibernate), understanding all the failure modes and possible concurrency issues becomes intractable.

Their latest iteration of Teams runs on https://teams.cloud.microsoft.

I work for a company that has operated like this for 20 years. The system goes down sometimes, but we can fix it in less than an hour. At worst the users get a longer coffee break.

A single click in the software can often generate 500 SQL queries, so if you go from 0.05 ms to 1 ms latency you add half a second to clicks in the UI and that would piss our users off.

Definitely not saying this is the best way to operate at all times. But SQL has a huge problem with false dependencies between queries and API:s that make it very difficult to pipeline queries, so my experience has been that I/O-bound applications easily become extremely sensitive to latency.