epmatsw

It's amazing how many awful comments this is drawing. Is this just bots getting autotriggered on keywords or something?

Yeah. And payoff times are like 12-15 years. It sure doesn’t seem cheap here.

Since it’s (imo) default-wrong in English, I’ve chosen to think of it as a nice way to point devs to something that’s locale-aware like Intl.Collator instead. If it “just worked” in English, most of us would never think to use the correct utility instead.

There’s an accessibility feature called Screen Curtain that turns it off completely https://support.apple.com/en-us/HT201443

I think they’re saying that TS won’t add the feature until JS does. Still kind of a strange take IMO, but makes a little more sense.

In this case, master is derived from a master/slave concept in BitKeeper, so it falls into your second category.

https://mail.gnome.org/archives/desktop-devel-list/2019-May/...

For those of us here who receive stock compensation, you can donate that directly too! If the stock has long term capital gains, the tax savings can let you donate even more.

https://www.aclu.org/gifts-stock

True. I wasn't sure how to interpret that section either. Compensation (or Total Compensation) might be a more interesting measure

I'll say that GetAround at least was great when the guy renting our car totaled it. Got the full value back, he was on the hook for the deductible and everything.

> because developers mostly would build high-end units

This is such a frustrating perspective.

I’m about halfway through and also did my undergrad at GT. Overall I’ve been pretty disappointed. The lectures are just YouTube videos played through Udacity, and the quality has varied from okay to bad. TAs make a big difference, but the quality there is a huge range. Some classes have had really good interesting active Slack communities, while others are basically just a Piazza page with people asking for help on projects. If you were disciplined and didn’t care about the degree at the end, you’d get a lot more bang for your buck just by watching the YouTube videos and reading the textbook, since that’s basically the level of instruction you get.

I think so. If you watch someone like Katie Ledecky, she breathes every 2 strokes.

https://www.youtube.com/watch?v=bQU_VWBF1uw

The most recent Hardcore History episodes are about WWII from the perspective of Japan, and they’ve really opened my eyes a bit to just how much of their side of the story was left out of my education.

Stryker is a JS version. Google has some interesting whitepapers about their usage of mutation testing as well: https://ai.google/research/pubs/pub46584

At least a few years ago, when I was at Epic (not on a medical-user-facing team), the issue that caused this wasn't the data storage of the timestamps or whatever. It's figuring out how to display events during that repeated hour in charts that assume 24 hour days in patient-safe way.

Say you see on the chart that a patient received medication at 1:30. It's now 2:30, and the patient is supposed to receive medication every 2 hours. Do you give them another dose? Did they get their does at the first 1:30 or the 2nd 1:30? Expand that by the literal thousands of super (almost frustratingly) customizable workflows, custom charts, etc., and the problem gets pretty big.

Considering most (maybe all?) Epic upgrades require brief downtimes, a lot of hospitals chose to take their downtime to install updates during the DST changeover time and rely on their doctors/nurses/etc. to be extra careful on paper during the doubled hour. Is it a great system? Not really. But it kind of works I guess.

Casey Liss (host of Accidental Tech Podcast, among others) has a small writeup about that work at https://www.caseyliss.com/2014/11/22/how-i-make-podcasts

Wow, I guess it has changed a lot since I took it in 2007ish. My recollection is that it was almost all theoretical, with only a little bit of tinkering with a toy game program as a practical bit.

Or you’d have to not have walked around downtown SF lately. It’s a rare day where I don’t see multiple self-driving cars.

The CSP info is a little off. Specifically, there are some directives of CSP (in this case frame-ancestors, the replacement for X-Frame-Options) that are specifically ignored if specified in a only <meta> tag. The header is the only way to have access the full set of CSP features.

Radium Girls is a fairly well-reviewed book about that: https://www.goodreads.com/book/show/31409135-the-radium-girl...

This is super interesting. Seems like the real ruling is that the federal government can’t compel states to implement/enforce non-federal laws. I wonder if that will affect things like the drinking age...

This is super interesting. Seems like the real ruling is that the federal government can’t compel states to implement/enforce non-federal laws. I wonder if that will affect things like the drinking age...

If anyone is interested, The Box is a book that covers this topic in a lot more depth. It’s truly excellent

If I had to guess, this site is super old. Using JQuery 1.7.1, Coffeescript, a bunch of script tags (no bundling, etc), calling CSS "CSS3" and including "HTML5" in the title, pre-iOS7-style icons, etc. Looks like somthing made in 2010ish.

Edit: Last updated 2015 https://github.com/Ivanca/PresentationIvan

Even that is probably overcomplicating it at this point. npm install —save-dev create-react-app. Done!

I’m psyched for sideEffects: false and better dead code elimination. So much more treeshaking!

Most browsers already did, and some (not all) of the ES2015 stuff requires property ordering. Probably easier to just keep everything ordered since it could be needed by those methods.

Interesting to choose Epic as an example. In my exit interview there (leaving for SV), the whole interview was about how they could be more competitive when hiring against Google etc (obvious answers were vacation policies and equity, where Epic was woefully behind). So Epic is (or was, ~3 years ago) definitely competing for the same developers as those big companies.

For HSTS, it’s based on the spec. There’s not supposed to be a user-accessible override for HSTS errors, which is why Chrome hides it behind that easter egg. Firefox has no override of any kind.

Pro-tip: On Chrome's certificate error page, you can type "badidea" (or "thisisunsafe" in 66 or later) to force it to let you through.