548 karma · joined February 16, 2017
I'm certain correctly designed software can safely control critical functions, otherwise failure in a large category of aircraft systems would result in many more MCAS unrelated accidents.
This particular MCAS control philosophy seems to be a flawed control system. With reference to the the graph (link provided by obituary_latte):
https://i.imgur.com/WJuhjlO_d.jpg?maxwidth=1640&shape=thumb&...
With only one sensor being "looked at" at any time, and with the system not having the sense to know to stop commanding pitch down after 26 times with attempted pilot overrides, it would seem almost beyond belief that any competent team of on-the-ground engineers (as per Boeing) would not see that the system is flawed.
Would be interesting to see if this was the case, and how the likely good engineering decision was overridden by the commercial aspect.
With increased tech, comes increased scope for this kind of cost optimisation, and we must be careful in many more industries. Eg Automotive self driving cars.
Yes but no helmet is even worse for an unconscious person's brain function :)
I also think the word computation is used a bit too grandiosely by Wolfram. Which is evidenced in the writing here.
I do admire Wolfram for even advertising his CEOing meetings though. He goes into the detail to a level you would not necessarily think a CEO would do. Credit where credit is due, he is not shy. Many CEO's would not bother.
I mean, technically, everything is a computation, but we accredit actually complex things to that term, not everything. To use it "whilly-nilly" deflates the words impact.
It takes a certain kind of person, to be able to extract self value from seeing others directly create it, rather than directly creating it. Not everyone prefers that and some find more satisfaction when directly responsible for the added value.
It's the self consumption of a direct-value vs indirect-value effect that drives whether you will be good at one or the other.
The problem is that the mainstream mantra sways people into chasing indirect-value type roles, when they ought not to be (for the good of the individual).
One way is to try and get some sort of security cleared job. Once you do, you immediately elevate yourself away "from the crowd" of developers in the market and you will find major global companies want you and they pay well. And when you get your first gig, you can be sure that another company will want a security cleared engineer, so it's good for job security.
Just be careful how you say no when they ask you if you want to join on a perm basis :)
you become an "employee under guise" and then you will be taxed as such. then you get the worst of both worlds.
Nowadays I do a hybrid approach, so I have use NanoGUI and create my own "live data" "retained mode" controls. Now I have either the best of both worlds or the worst of both worlds. I think the best:
Pros: - I don't have to bother with data binding. As the control is passed a pointer to the actual memory for he value, it can "go get it" when rendering, rather than my application setting its state. - I still have classes to represent elements and state, so its conceptually simple to build controls on controls. I found this difficult with Imgui.
Cons: - renders 100% full speed, but I am working on way to speed up and slow down render loop depending on user activity, so that when sitting idle, the cpu is not burning.
Errm....citation required please? otherwise I may take offence.
This reminds me of other software package that was "free forever" but then became popular and lost its "free forever" title. (I forget the name)
How will this not happen here?
I'm just sceptical of wild claims like these. Surely if this software grew legs the devs would have to charge?