skysight-inc/HackerNews huggingface dataset:
> There requires no empathy to conclude that providing for our neediest appears to be economically beneficial for everyone

Unless you have information on the distribution of returns, they conclusion is unwarranted. At best, you can say that if you find a friction-free way of taxing and equally redistributing the gains (including most of the redistribution to the poor), and paying it back (starting by paying back 100% to the people you took it from in the first place) you would improve things for everyone.

But of course, you can't: reversing the redistribution would reverse the gains from the redistribution.

So what it does is improve the mean. It maybe improves the median. But for everyone? No, it doesn't. At least, not in the narrow financial terms those figures address.
That's pretty hyperbolic. Are you implying that monolithic designs are just inherently inferior? I don't think that even approaches a reasonable take on the subject.
Not quite. Agile, when done right, by small-to-medium teams, can be effective. However, whenever a big corporation tries to jump on the agile bandwagon, it turns into nightmare fuel.
Thanks to everyone for their thoughts and insight into this. You make some good points on why an email sign up may not be effective. Therefore, I am currently running a test to see how the website performs when the email signup is removed - it's a direct download.

Thanks for your time an constructive criticism!

Cheers,
Robin
How to Permanently Disable Chrome Full-Screen Mode
That there are many different ways to measure something objectively doesn't destroy my point. While they might differ on the exact position, they tend to put the same people near the top, and the same middle tier people in the middle. Any that don't come at least somewhat close to each other will be wiped out as those who use the better measure destroy those who use the worse to select their players.
Failing to maintain product quality is an indicator of inability to scale.
Mostly just AT&T and Verizon, and Verizon is definitely the more "premium" one. I consider them premium because they cost more, they don't try to be the most affordable, they own other brands for that (cricket, etc.).

The biggest difference is their coverage. If you live in, and mostly travel within a metro area you're fine with sprint/tmobile, but anybody who's ever travelled will find that verizon is the only option if you work in, or go to the middle of nowhere at all. Basically Verizon has towers everywhere, including farmland that I can't figure out why they'd want to cover, but hey you get coverage while picking blueberries!

(This only goes for the USA, and includes my experience living in Michigan working in phone repair/retail, as well as my travels with other people/their carriers outside of Michigan)
As I said, I would not put the blame on the pilots. That is clear. Boeing made an unsafe airplane. Airline safety is a layered thing though. Even if it's Boeing's fault, it's possible that the pilots could have recovered, even though it looks like recovery is not necessarily easy.

I also have a fair bit more than 200 hours, and I can't say whether I would have made a smoking hole in the ground or not either. Still, if I were put in that position, I would much rather have an experienced pilot sitting to the right of me.

Having an inexperienced pilot that probably hasn't ever experienced a real emergency is a significant liability when you're trying to troubleshoot something like this without a lot of extra time. In this case, they would have had a better chance of surviving if they had identified that the problem was MCAS before the plane got so wildly out of trim, or they had made the decision to turn the electric trim back on sooner. This is a lot easier if you've got two fully fledged pilots instead of effectively a captain and an apprentice.

Say what you will about the 1500 hour rule, but there has been precisely one fatality in all of U.S. aviation in the ten years since the Colgan flight.
Does anyone know what Banks and/or services use same-day ACH? The article says same-day volume was up to $160B last year, but I've yet to see anything faster than next-day ACH.
Isn't it possible they didn't know the phones were fake? If the fakes are so good that even Apple can't tell, then it's possible they thought they were real. Maybe they thought they were buying genuine iPhones for cheap since they were broke and having Apple send replacements to make a profit? Or am I missing something?
I’m in between. I have an SO score of just 1000, but I vote a lot. Mainly because I’m logged in via oauth anyway so it’s no hassle to do so.
Holy smokes. I thought finding an ITX board for 2x8GB sticks of full size 240-pin DDR3 ECC UDIMMs was hard.
Developers and operations often love microservices.

If you make one small change you only have to test and deploy that one microservice. Instead of having to redeploy the monolith which not sure if you've ever done that before is often terrifying.
Synaptic Package Manager Still Lacks Wayland Support, Removed from Debian Buster
This bulletin notes that electric stabilizer can be used to neutralize the control column prior to STAB CUTOUT, which it appears the Ethiopian crew did not do.
The downside of that is that you end up with heaps and heaps of buggy queries and SQL code resulting in a maintenance nightmare.
This is why they are currently trying to beef up their second and third lines of defense.
Then you pay $O/month for AWS Enterprise Support (who are actually quite good and helpful) to help augment your $M/month employees and $N/month direct spend.
What about a single button to turn MCAS off and return to trim to a neutral position? Or a setting where the pilot is telling the system to ignore the sensor input.

Maybe a bit like a self driving car planes will eventually have a system where they can use visual markers as a check on what sensors are reporting.
Wow. This is one of those ideas where you immediately facepalm when you see it and moan, "Why didn't I think of that?!?" Good on you and keep it up.
And now, you are just a stranger with all my secrets
and they're using that very un-hip microsoft .net
I assure you, my feelings are well intact. Everyone I worked with hated the 5.56. And yes, I've deployed, and to some odd places. Not only did our unit do the sandpit, but a few us, myself included, assisted the Philippine Marines with patrols in various locales in the PI.

Try an M-14 out for size or even an AR-10. World of difference. The power factor between the two calibers is simply apples and oranges.
They can! That's exactly the point of agile and is how you get them onboard. When clients want a feature that is weird or complicated or whatever, the answer is never "no" the answer is "sure, now tell us where it fits in the priority list".
My general test for most new technologies is that the desire to use it has to have arisen out of the pain of not using it. If I'm looking at a framework for any reason other than having shouted "there has to be a better way!" then I'm not in a position to evaluate its merits, and even if it is the right choice I'm not in a position to understand why, and will thus be prone to using it in a stupid way.

It might seem expensive to do things the "wrong" way first every time, but I really do think it's necessary.
Exactly. There's no silver bullet, only trade offs.

In this case you're only shifting the complexity from "maintaining" to "orchestrating". "Maintaining" means you build (in a semi-automated way) once and most of your work is spent keeping the services running. In the latter, you spend most of your time building the "orchestration" and little time maintaining.

If your product is still small, it makes sense to keep most of your infrastructure in "maintaining" since the number of services is small. As the product grows (and your company starts hiring ops people), you can slowly migrate to "orchestrating".
More details on what prompted this decision: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818366
Can you share the context for the graph?

Do you have a formal definition for how you are using ‘fairness’?
I guess that's his point, you are not doing less work, all you did was moved your debugging from one place to another.
SQLite is good quality software, and very heavily tested. There's nothing wrong with using it so long as you don't outright misuse it, and they are clear about when you shouldn't be using it.
I wonder how the Asus Tinkerboard and the Pine64 RockPro 64 (RK3399) compare
Neat! It doesn't work on Oracle, but you implied that it's PostgreSQL-specific so I somewhat expected that. It's a lot cleaner than mine and, even though it's not something I've seen before, it's fairly obvious what it's going to do.

When I did my testing I did it on Oracle since I have it available at work. For my non-work projects I use PostgreSQL and, for the most part, find that I can flip between the two database without too much trouble. Of course, this also means that I don't know about some PostgreSQL niceties like what you showed.
If the AoA was truly way too high then insane trim would be required to correct that. MCAS and similar systems came about in response to AF 447 where the pilots entered a high AoA situation and stalled the plane into the Atlantic.
ACM ICPC World Finals 2019 Problem Set [pdf]
Other direction, deca-, hecto-, and kiloservices.

https://en.wikipedia.org/wiki/Metric_prefix
While I largely agree with the thesis of this article, I actually really like the entire "scalable microservice" way of designing things.

It's overkill for anything I need to do, but my home server is six 8-core ODroid devices, orchestrated with Docker Swarm, with most of my services on there being load-balanced, and glued together with Kafka if they need to talk to each other.

Do I need my internal video streaming server to be able to scale horizontally? Of course I don't, there's only ever three people max watching things from there at any point in time. However, I find that, overall, my brain thinks more-or-less in terms of these microservices, and it doesn't really hurt much to do it that way.

If I find it pleasant enough to do, why the hell not make it hyper-scalable and able to reach Google levels?

EDIT: Just a note, I know that Docker Swarm probably isn't quite capable of Google-size. Still, moving to Kubernetes or something wouldn't be terribly hard (the reason I didn't use it was because a few years ago I had some issues with Kubernetes on ARM and Swarm worked outta the box).
Excersice vs. Drugs to treat High blood pressure and fat
Thank you for that. Putting hundreds of aircraft into service before the simulators were available to airline pilots looks rather bad in hindsight.

I would hope that Boeing internally had simulators for the MAX while they were testing it - along with a borrowed supply of pilots who were competent but had no inside information. Even if they didn't, a pencil and paper exercise might have been useful:

1. AOA sensor fails at takeoff (A), the pilots receive an unreliable airspeed warning and the stick shaker activates. The pilots now mistrust their sensors and want to keep their speed up and the nose down.

2. At about 1000 feet above ground the pilots level the aircraft, raise the flaps and start the unreliable airspeed checklist. MCAS starts trimming intermittently.

3. The pilot flying is having to pull further back on the stick and trim correctively while the crew work through their checklist. At this point the crew need to avoid any over-focus, task saturation or over-stimulus from the many warnings and indicators and ask themselves why the aircraft is trimming the way it is. They have a fairly narrow window of time in which to do this and then disable the trimming with the plane in a well trimmed state.

(A) That this happened twice in relatively quick succession might be due to a common problem. Even if such a problem is found and fixed the AOA vanes and pitot tubes are delicate sensors sticking out of the nose of the aircraft; the system should be robust to failures in these sensors.
> Pretty misleading to write "... I want to demonstrate that monads are feasible in Rust." if that's not actually the case

When not taken out of context, I don't think it's misleading at all.

> You see, there’s a problem with talking about whether monads would be useful or not, and it’s this: there are a large number of design challenges to overcome to have any hope of implementing them at all — to the best of my knowledge, there currently exists no realistic (that is, practical) design for monads in Rust. In fact, there are so many obstacles that some people express doubt that it’s even possible.

> In general, I don’t think it’s worth talking about the virtue of a language feature if we think there’s no way we could actually implement it. However, I think there are arguments to be made in favour of higher-level abstractions in Rust. Thus, to facilitate discussion, I want to demonstrate that monads are feasible in Rust.
ACH in the EU is generally same day. The US is super behind the times in that regard.

The reason that it’s next day is that for most banks, the process of doing an ACH transfer is to effectively SFTP a file with the amount to transfer and account details to the receiving bank, and they batch process them nightly.

Also, with this system, there is no difference between a direct deposit and direct withdrawal. One just has a negative transfer balance. So once you approve someone such as your employer to direct deposit they can also withdraw from your account with no warning.

It pains me that a system so shitty powers the world financial market... that’s what you get from monopolies.
I miss Perl. Why did PHP win again, in the late 90s? (though I'm mostly Python these days and shan't complain, there was a good 10 year stretch of PHP there I'm not proud of).
It's a pretty good analogy actually. If you think back to the early Java days when everyone was obsessed with design patterns and over engineered code people said exactly the same thing. Why do you have these interfaces if the implementation will never change ?

So I'm not saying monolithic designs are bad but they simply don't scale well once you get to a certain size. Just like design patterns should only be used once your codebase gets to a certain size.
> The vast majority of Germans don't drive on the Autobahn at such insane speeds

It's not an insane speed, a new VW Golf can handle 170-180 kph pretty damn well, hell, my 12-year old 1.4l hatchback can do 130-140 kph for hours at a time quite as well, too.
Which is exactly why everything runs Linux instead of Windows.
What is meant by "“solve” the problem mostly within the problem domain, not the solution domain."?
Operation SaboTor Leads to 61 Arrests
All I'm saying is that it's not so easy to figure out how much value a person gets from the road system based on what vehicle they drive.

For example, I ride a bike and don't own a car. Should I pay taxes to maintain a freeway I never use? What about the day that I get hit by a car and the ambulance takes that freeway to and from the hospital?

Traffic is a problem, I agree. But to me congestion pricing seems like economic segregation.

(In the example, should I be able to, say, pay an extra $100 and get priority lane scheduling?)
One thing you can try is to leverage your existing local network to start a new one, by asking "do you know anyone there?" and go from there.

That part probably works even better with online networks as they're likely to be more scattered around the world.

You can then go from a few initial people in the new area and ask them if they have people they think you should meet.
well the "orm" is more like a database driver that can serialize to models than an orm.

but consider their stack there are better "starting" alternatives (they also used them before dapper), like Linq2Sql, EF Core, etc...

Also compared to other languages Linq and EF Core are way better than most alternatives (besides that some things are just not working, like lateral joins)
MCAS is not an emergency system, it is a trim control system designed to make the plane behave predictably in an otherwise unstable flight regime. If you wanted it to move fast, you would use a stick pusher; moving the trim takes many seconds.
With such a pliable device I consider every adaptation a person must make to be a deficiency. Perhaps a not-yet-addressable deficiency, but a negative nonetheless.
Fortnite Discovery Challenges
https://topworldnewsreports.blogspot.com/2019/04/Fortnite-Discovery-Challenges.html
all the hidden Battle Star and Banner locations from the loading screens-Fortnite Discovery Challenges.
#fortnite_game
#fortnite_discovery_challenges
#fortnite_challenges
#fortuite_hidden_battle_discovery
Great guide but there seems to be a typo/mistake regarding how to save the smtp password in step 2/gmail: should use sendemail.smtpPass instead of the non existing sendemail.password.
And let's not forget! Got a support contract so we can all BLAME someone not in the room and feel good.
I haven't set this up, but looking at the manpages, it seems you can set git to obtain the password from your password manager (which should keep your password encrypted). From gitcredentials(7):

> Without any credential helpers defined, Git will try the following strategies to ask the user for usernames and passwords:

> 1. If the GIT_ASKPASS environment variable is set, the program specified by the variable is invoked. A suitable prompt is provided to the program on the command line, and the user’s input is read from its standard output.

> 2. Otherwise, if the core.askPass configuration variable is set, its value is used as above.

> 3. Otherwise, if the SSH_ASKPASS environment variable is set, its value is used as above.

> 4. Otherwise, the user is prompted on the terminal.

So, for example, if you're using `pass`, the password-store, you can just set one of these to `pass smtp/me@example.com`, and pass will prompt you for your decryption password for your smtp password.
Yeah... Ruby's very nice and feels Perl-ish sometimes.
But high enough to re-enable a system you know is malfunctioning?

I guess we will have to wait for the final report but the pilot's actions are perplexing here. Even if we accept that they can't trim with the wheel, why enable electric trim and then not use it? Why not enable it, trim to where you want, and then use the cut out switch again?
Upwork to Begin Charging Freelancers to Bid on Jobs
Google put home-screen ads on Sony Smart TVs
Great advice, and to double click on it: google wasn't google either when they started and part of their value to investors was their bare-bones hardware infrastructure. That part of google is (philosophically) worth emulating.
Mostly younger people are choosing to jump around jobs.

The common advice and wisdom is actually not to do this.
That may be where they will go with this but it may require a new certification and training.
ACM ICPC World Finals 2019 Results
It doesn't sound like it the way the article frames it. A lot of shipments were stopped at the border by CBP.
The general fact of reality is that if you are building anything technical, then knowing and managing the details, whatever the details are, will get you a lot more bang for your buck. Reality isn't just a garden variety one-size fits all kind of thing, so creating something usually isn't either. If you just want a blog like everyone else's, then that comes packaged, but if you want something special, you will always have to put in the expertise.
OSU is in Corvallis.
ah yeah. got my initialisms mixed up. the apu is not an emergency source of power.
Musk was one of many founders of PayPal. SpaceX is actually run by Gwynne Shotwell.
They obfuscate the routing and account numbers because once you have them, there's little that prevents someone from debiting money from that account.
I'm Chilean. It just took me ~40 seconds to complete my tax declaration, skimmed through all companies involved (employer, banks and pension fund), typed in my bank account for my tax return and done.
> If you're massively overweight and someone tells you to just go for a run, you're going to get hurt

Massively overweight people can't run, even if they wanted to. Their "run" speed is slower than my "walk" speed.
Doesn't seem that complex to me. Insurance companies kinda do that already. It's not a technology issue, otherwise Google or Microsoft would have figured it out already, it's a governance and legal issue. Blockchain doesn't seem to be bringing to the table anything valuable in this case.
I typically "train" every day, meaning I run six days a week and ride my bike on the seventh. I do, however, have rest days; it's just that my rest days are shorter distances at a lower heart rate. My Tuesdays and Thursdays are rest days, so I run 8.9 miles @ 130 beats-per-minute heart rate.

I absolutely, do not recommend my training plan for others; it's taken me more than ten years to get where I am, but as an example of what can be done (at least with my body), you can see how I recently trained for the Bataan Memorial Death March[0] and also see a subset of my official ultra results at UltraSignup[1] as well as my self-reported marathon results at Marathon Maniacs[2].

FWIW, I think my sleep schedule and diet have contributed significantly to the gains I've made over the years, but I'm also well aware of survivor bias. Neither of my parents were athletic though and I absolutely hated running as a kid (although I really enjoyed ultimate frisbee in high school).

[0] https://github.com/ctm/Bataan-Memorial-Death-March
[1] https://ultrasignup.com/results_participant.aspx?fname=Cliff...
[2] https://www.marathonmaniacsdb.com/Maniacs/MyRaces?ManiacId=4...
Nope.

The Boeing/FAA directive re: MCAS does not instruct them to extend flaps.

Further, there's other things going on in the cockpit due to the malfunctioning AoA sensor that's the root of all this.

Specifically one of the effects is that they get an Unreliable Airspeed Indication, and run that checklist. That checklists memory items include maintaining the current flap configuration (in this case, flaps up).

The Boeing/FAA directive does not instruct them to deviate from this and extend flaps. They have a checklist memory item instructing them to in fact do the exact opposite, and not touch flaps.
Future of server is serverless? :P
It would be interesting to reverse-engineer this to figure out which paint splatters reliably produced "use strict;".
The flight data graph shows no manual electric trim inputs at that time.

So must be manual trim wheel movements.
Yes, but I think very broadly speaking the quirky behavior is stuff you bump into, learn about, fix, and then can walk away from.

The daily/monthly maintenance cycle on a self hosted SQL server is “generally understood” but you still have to wake up, check your security patches, and monitor your redeployments.

You can do some of that in an automated fashion with public security updates for your containers and such. But if monitoring detects an anomaly, it’s YOU, not Heroku who gets paged.

It’s a little like owning a house vs renting. Yes if you rent you have to work around the existing building, and getting small things fixed is a process. But if the pipes explode, you make a phone call and it’s someone else’s problem. You didn’t eliminate your workload, but you shrunk the domain you need to personally be on call for.
I love this footnote so much:

> This feature does enable a neat quine: the Perl program “Illegal division by zero at /tmp/quine.pl line 1.”, when saved in the appropriate location, outputs “Illegal division by zero at /tmp/quine.pl line 1.” The reason for this behavior is left as an exercise for the reader.