Also: https://youtu.be/PmLH_M2B-bM?si=jvJ5UCFD9dlpZfc7

So gamble? The only proven way to reliably make money on investing are things like index funds, which you will need a fair amount of starting capital to make a living off of.

Much of the gaming-adjacent internet are teenagers. It will always feel cool to be against [popular thing]™ when you’re still figuring out what your identity is as an individual.

They’re talking about the visions of sci-fi authors, filmmakers, and artists. The tech Bros are the ones being drawn towards those artists’ visions.

Bing!

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

IMO if we ever get to a point that pulling information from the Internet is as simple as “remembering” it the same way we remember any other information, that could have both significant advantages over having to first read the data visually to ingest it, and terrifying potential to implant “facts” into someones mind.

I think this was an Orville episode, wasn’t it?

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.

Yeah, actually moderating an online space with even modest activity is fucking hard and takes a shitton of time.

I think a lot of people underestimate the effort involved and quickly lose interest once it becomes apparent.

I don’t think a medical-focused Trek show would have to take place during war time. Medical Ethics in general is ripe for the sort of show Trek lends itself to.

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

deleted by creator

Why shouldn’t we, as engineers, be entitled to a small percentage of the profits that are generated by our code? Why are the shareholders entitled to it instead?

I worked in Hollywood before becoming a programmer, and even as a low level worker, IATSE still got residuals from union shows that went to our healthcare and pension funds. My healthcare was 100% covered by that fund for a top-of-the-line plan, and I got contributions to both a pension AND a 401K that were ON TOP of my base pay rather than deducted from it.

Lastly, we were paid hourly, which means overtime, but also had a weekly minimum. Mine was 50 hours. So if I was asked to work at all during a week I was entitled to 50 hours of pay unless I chose to take days off myself.

Unions fucking rock and software engineers work in a field that is making historic profits off of our labor. We deserve a piece of that.

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.

I know I learned it in high school at one point but definitely isn’t something I would have been able to recall on my own.

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.

We’ll always DRR DRR !

I actually think the radio signal is an apt comparison. Let’s say someone was trying to argue that the signal itself was a fundamental force.

Well then you could make the argument that if you pour a drink into it, the water shorts the electronics and the signal stops playing as the electromagnetic force stops working on the pieces of the radio. This would lead you to believe, through the same logic in my post, that the signal itself is not a fundamental force, but is somehow created through the electromagnetic force interacting with the components, which… It is! The observer might not understand how the signal worked, but they could rule it out as being its own discreet thing.

In the same way, we might not know exactly how our brain produces consciousness, but because the components we can see must be involved, it isn’t a discreet phenomenon. Fundamental forces can’t have parts or components, they must be completely discreet.

Your example is a really really good one.

Self driving cars could actually be kind of a good stepping stone to better public transit while making more efficient use of existing roadways. You hit a button to request a car, it drives you to wherever, you need to go, and then gets tasked to pick up the next person. Where you used to need 10 cars for 10 people, you now need one.