Ataraxic

It should be noted in the doomed Air France 447 flight, the plane activated the stall warning because of a high angle of attack that was leading to stall. (thanks pdx for the corrected info)

At some point the system rejected the data and stopped the stall warning because the angle of attack was so severe that it considered the data erroneous. This is speculated to have caused the co-pilot to keep pulling back on the stick and to maintain the stall because everytime he let the nose of the plane come down the stall warning activated again as the AoA was decreasing into the range that the airplane considered a real signal. https://www.vanityfair.com/news/business/2014/10/air-france-...

A plane's instruments, the actions software takes, and it's interactions with the humans that fly the plane isn't as simple as an if statement.

If anything, fewer and simpler controls or automated systems are easier to debug and work around than a plane that has an internal calculus of what is valid data.

Air France 447 crashed because of a stall caused by a severe AoA that MCAS might have prevented (if MCAS simple pushes the nose down at high AoA it might. I am unsure of the exact implementation). MCAS obviously had a different impact on the Lion and Ethiopian Air Flights.

Basically, it's complicated.

A little late to this discussion, but although I'm a big fan of many of the concepts in Concourse, I think it's lacking a lot of polish.

For example, I have actually implemented patterns within Jenkins to force all jobs to run inside of containers. A job is just a container + command with some linking using the jenkins pipeline plugin that reads some json configuration to determine how jobs are linked.

The primary issues I have surround the fact that my company uses kubernetes, thus we have no insight into the runc containers. Load balancing in concourse is non-existent. If a worker goes down due to load, if you bring it back up, it's going to go down immediately from all the jobs that have been triggered while the worker was offline. Not only that, the resource requirements seem pretty high. Recently a concourse worker stalled because the amount of volumes/images it was caching was over 100 gigs, and not knowing the internals, I wasn't sure what the best way was to clear this cache. Having to tell the infrastructure team that we just need to spend more money is a hard sell when we've upped the cpu, memory, storage, postgres disk, all more than once. I understand that different images have vastly different sizes, and jobs different amounts of work, but their need to be some clear suggestions for sizing. If there exist them now, I apologize but I haven't seen them.

So yeah I've had some fun developing in it, but more help making it reliable would be really nice. Also if kubernetes is absolutely the wrong way to run it, which it seems like, I'd have to be provided a better/easier alternative to really become an advocate.

Final note: has anyone actually setup metrics/monitoring for concourse that doesn't know BOSH? The docs describing it seem huge unless you already have the infrastructure pieces. Let's setup riemann (we already have statsd and no experience with riemann), emit to influxDB (we have prometheus, no experience with influxDB), then use Grafana (ok we already have that). I just wanted a better idea of disk, cpu, mem, # of containers, lifecycle without having to setup all these new pieces of infrastructure. Finally, just not that interested in BOSH, which all of the example metrics repo's are.

Webpack dev server simply serves up compiled assets for convenience, because it serves new assets as they are compiled and blocks when compiling. It should be fairly trivial to serve up static production assets as needed. I say this as a person who just converted a production rails app to use webpack as first class citizen.

I tend to support euthanasia, but its practice in that article scares me.

I guess I believe that people ultimately do have a responsibility to others. Her son did not ask to be born and Tom's quote "You’ve just taken away the suffering of one person and transposed it to another!" convinces me that euthanasia is not as clean as we might believe. What if Tom having suffered this triggering event and having a genetic predisposition to depression applies for euthanasia? It seems euthanasia for the whole family is ethically above board in Belgium, but I still feel that outcome is unacceptable.

The only thing that really bothers me is that so many ethicists in Belgium (as far as this article describes) believe this is clear cut. I generally don't have too many disagreements with most concepts of western philosophy, but if this is the end result of the application of self-determination, I definitely have plenty of reservations.

Finding out that your parent committed suicide after the fact is just unacceptable to me, especially because the parent in this article did honestly express to the doctor that she cares for them.

I mean if you engage in agreements with unions that are fundamentally impossible for the company to meet, I wouldn't exactly call that union busting. In fact from what I remember about this bankruptcy specifically, in order to continue operations they absolutely had to negotiate a new contract with all the unions. Every union but the bakers agreed. Because the bakers walked, they had to file bankruptcy.

I feel like this is an example of the failure of unions. It also seems selfish that given that if you know bankruptcy is coming, one union would bankrupt the company when all the others were for it. If you hated the job that much, you can leave. In the end, it didn't save jobs, it didn't protect their livelihood, and I think it's quite possible that it delayed what is obvious now: automation was inevitable and layoffs were necessary. Their workforce of 8000+ is now ~1200 and only now are the becoming profitable again.