I didn’t know that! I just subbed to their service for Make Some Noise so I kind of feel better about shelling out for it now.

We do. A24, for instance, is still making a couple movies by agreeing to work under the proposed terms by SAG. As far as I know, no one else has made such agreements yet. The more of such exceptions that get made, the weaker the AMPTP’s position will get.

First thing I thought of as well: https://youtu.be/rBQhdO2UxaQ

Am I taking crazy pills? Except for 76, an MMO, Bethesdas record has been pretty good for single-player games, no?

I’ve played all of their games since Morrowind on Launch and always had a blast.

I could not disagree harder. Bethesda puts a ton of work into making their games as extensible as possible and I think that’s not a deficiency at all.

This but like, unironically

I think it depends on the project. Some projects are the author’s personal tools that they’ve put online in the off-chance it will be useful to others, not projects they are really trying to promote.

I don’t think we should expect that authors of repos go too out of their way in those cases as the alternative would just be not to publish them at all.

That’s a really interesting perspective I didn’t think I’ve seen before. Thanks for posting.

Imo that’s still not enough. Plenty of crashes or failures happen in a way where loading screen animations still keep playing. Having a cursor you can move around to validate that the process is still responsive is important feedback.

I also remember lots of games that did exactly what you are saying and there was no way to tell if it had hung during loading or not because you couldn’t check if it was accepting feedback.

Formal licensing could be about things that are language agnostic. How to properly use tests to guard against regressions, how to handle error states safely.

How do you design programs for critical systems that CANNOT fail, like pace makers? How do you guard against crashes? What sort of redundancy do you need in your software?

How do you best design error messages to tell an operator how to fix the issue? Especially in critical systems like a plane, how do you guard against that operator doing the wrong thing? I’m thinking of the DreamLiner incidents where the pilots’ natural inclination was to grab the yoke and pull up, which unknowingly fought the autopilot and caused the plane to stall. My understanding was that the error message that triggered during those crashes was also extremely opaque and added further confusion in a life-and-death situation.

When do you have an ethical responsibility not to ship code? Just for physical safety? What about Dark Patterns? How do you recognize them and do you have an ethical responsibility to refuse implementation? Should your accreditation as an engineer rely on that refusal, giving you systemic external support when you do so?

None of that is impacted by what tech stack you are using. They all come down to generic logical and ethical reasoning.

Lastly, under certain circumstances, Civil engineers can be held personally liable for negligence when their bridge fails and people die. If we are going to call ourselves “engineers”, we should bear the same responsibility. Obviously not every software developer needs to have such high standards, but that’s why software engineer should mean something.

My experience has often been the opposite. Programmers will do a lot to avoid the ethical implications of their works being used maliciously and discussions of what responsibility we bear for how our work gets used and how much effort we should be obligated to make towards defending against malicious use.

It’s why I kind of wish that “engineer” was a regulated title in America like it is in other countries, and getting certified as a programming engineer required some amount of training in programming ethics and standards.

IMO it’s a good feature and it’s a good thing it’s required. I remember the days when I would boot up a game and never be sure if my system crashed or not.

This requires the game to start giving you feedback before you start wondering if you should do a power cycle.

More good options is always a good thing.

In many cases it should be fine to point them all at the same server. You’ll just need to make sure there aren’t any collisions between schema/table names.

I’m not saying there aren’t downsides, just that it isn’t a totally crazy strategy.

You’re being sarcastic but even small fees immediately weed out a ton of cruft.

Lol, Texas and Florida are doing a good enough job of knocking themselves down without help from me.

Except in a true free market zoning laws wouldn’t keep adorable, high density housing from being constructed to artificially boost housing prices.

Other than that I agree with you.

I agree with the other poster that you need to define what you even mean when you say free will. IMO, strict determinism is not incompatible with free will. It only provides the mechanism. I posted this in another thread where this came up:

The implications of quantum mechanics just reframes what it means to not have free will.

In classical physics, given the exact same setup you make the exact same choice every time.

In Quantum mechanics, given the same exact setup, you make the same choice some percentage of the time.

One is you being an automaton while the other is you being a flipped coin. Neither of those really feel like free will.

Except.

We are looking at this through an implied assumption that the brain is some mechanism, separate from “us”, which we are forced to think “through”. That the mechanisms of the brain are somehow distorting or restricting what the underlying self can do.

But there is no deeper “self”. We are the brain. We are the chemical cascade bouncing around through the neurons. We are the kinetic billiard balls of classical physics and the probability curves of quantum mechanics. It doesn’t matter if the universe is deterministic and we would always have the same response to the same input or if it’s statistical and we just have a baked “likelihood” of that response.

The way we respond or the biases that inform that likelihood is still us making a choice, because we are that underlying mechanism. Whether it’s deterministic or not it’s just an implementation detail of free will, not a counterargument.

And often if you box yourself into an API before you start implementing, it comes out worse.

I always learn a lot about the problem space once I start coding, and use that knowledge to refine the API of my system as I work.