And who's to say you can't put the reason in the body and still keep the code? What are you hurting by sending back 400? Unless you have lb's taking out nodes because of excessive 4xx's (which sounds like insanity) I don't see a reason _not_ to send 4xx's. At the very least it's a useful heuristic tool.

The payoff of using 400 is you can watch your 400 rates with almost no effort (HTTP is well established and there's many many tools out there.) If you somehow start accidentally munging the card number sometimes or if your card processor starts doing wacky stuff you'll see a spike in 400 rates.

If it was really that troubling that declined cards are expected, I would personally at least want to see 200 come from the internal API and 400 go out to the client.

And if your "intermediate devices" start doing goofy stuff to 400's then you've got bigger problems... 4xx's shouldn't be taking nodes out of prod. That's wack.

Maybe that just escaped you from some reason, but I would think it's perfectly understandable for just about anyone.

Curious if anyone else here had a hard time parsing it...

"Ever" vs "human history" almost seems like a nitpick. _We_ have never seen it this hot, ever.

Is F# still the red-headed step-child of Core?

Last I fiddled with it F# was looking pretty unloved, but to be fair C# was still having a hard time with Core itself.

> If I wait exactly one second, Unix time advances by exactly one second

How does UTC jumping around affect this? If a leap second is removed it doesn't mean you've waited 0 seconds.

I feel like this is wrong too:

> If there’s a leap second in a day, Unix time either repeats or omits a second as appropriate to make them match.

It's not Unix time doing that. It's UTC.

Check out Cuberite for comparison. It's a Minecraft server built from the ground up in C++ and it's waaaaaaaay faster than the official server. Advantages of a rewrite I suppose...

There's no chance we "look towards the stars" if we can't fix the ground.

I feel like this is a universal absolute, doubly so when it comes to enterprise apps (the lone exception being when we switched from Lotus Notes to Gmail -- then only half the company hated the change).

I would've liked to know how long the changes were in place and how it affected productivity metrics, especially the amount of training time spent on new users. As is, the article seems kind of obvious. Enterprise users abhor change; who knew?

> Just like you wouldn’t appreciate a dictionary with only 10 words per page (so many pages to flip through!)

This also makes me question the veracity of the article. It's a really terrible metaphor that makes me wonder if they were _solely_ concerned with pretty design on the outset.

I want a dictionary that shows me 1 word per page, with a search bar. The page flipping functionality is useless and can be removed entirely. It's a bad workflow.

I can definitely say that over the past 20 years, our in-house LoB app has developed some really bad workflows as well (business changes a lot over 20 years). Removing these bad workflows would give us back a ton of screen real estate without losing productivity.

The causality is backwards. I don't want to create whitespace by changing the design and ruining the functionality. I want to change the functionality which will create more whitespace and allow room for beautiful design.

I had a similar experience. I explored their API and got stuck on how to implement my use-case and how to ensure it's legally binding. Sales and "technical" resources assured me it was possible, didn't explain how, and everyone balked at any sort of legal questions and basically told me that was all on us to sort out.

I decided I didn't need help creating a box for users to scribble on. E-signature isn't a technical challenge at all.

The dictionary definition is: a widespread occurrence of an infectious disease in a community at a particular time.

"Infectious disease" being the key. If we limit the definition to "took off" then any new and popular software becomes an epidemic.

It's naive to assume that something like this couldn't possibly be politicized simply because it relates to health. His points absolutely could be relevant to how the Surgeon General chooses to describe the uptick in vaping.

Overall tobacco usage is still going down: https://www.cdc.gov/tobacco/data_statistics/fact_sheets/yout...

The CDC's website[1] says there's been a 0.6% increase in vaping in middle school and 1.5% increase in high school since 2011. This advisory however says "E-cigarette use among U.S. middle and high school students increased 900% during 2011-2015, before declining for the first time during 2015-2017." Was there a nearly 899% drop in 2015-2017?

https://www.cdc.gov/tobacco/data_statistics/fact_sheets/yout...

My particular doctor shoots for an AHI around 10, which is still mild sleep apnea (5 is the threshold) and is still high enough to get you diagnosed and provided a CPAP in the first place.

So for 6 months my AHI hovered around 8 or 9, occasionally spiking to 12 (which made me really feel like crap).

My technician won't adjust without doctor's orders (and incidentally also told me I'd fry the entire machine in days if I used non-distilled water in the humidifier, which is just absurd.) The doctor books appointments months out, and is OK with my current results anyway.

So I tried bumping my pressure up by 1 and lowering the exhale comfort feature on my own. Tada! After a month my AHI averages 4, sometimes spiking to 6, and I feel much, much better.

Take for example the NPOSL-3.0:

A variant of the Open Software License 3.0, this license requires that the organization using it is a non-profit and that no revenue is generated from sale of the software, support or services.

https://tldrlegal.com/license/non-profit-open-software-licen...

The source is open, but you can't use it outside of non-profit orgs. It's "Open Source™", it's approved by OSI, and it can still get you in legal trouble.

Bingo. I work in an AS/400 shop. I simply can't invest myself personally in the work because I know my access to that environment is predicated on working for this particular company.

I can hone my Linux skills and even my Windows Server skills any time. I can bring it home. I can use it myself. I can own it.

I can't do that with the AS/400. Just spinning up a "virtual machine" in the office to play around on is a licensing mess, and there's no "cloud" where I can rent one for a reasonable fee (that I've found). I have no sandbox.

Since my continued access to that environment isn't guaranteed or even convenient, I don't really want to dive in. And if I don't want to dive in then learning about it at all feels like a waste of time. Which then means I end up learning the absolute minimum before moving back to familiar territory.