HN user

epmatsw

1,413 karma

Shiftless stupid jungle bum

http://willstamper.name

Posts1
Comments461
View on HN
Visiting Us 1 year ago

There’s also a strong culture of ownership of quality for individual developers. Design documents are expected for even minor changes, and each change goes through at least 2 rounds of well-documented testing by 2 other developers on your team. Compared to other companies where automated testing is the norm, it’s startling how few bugs they manage to ship.

Another thing I thought was interesting given modern dev practices is that you don’t even touch production code until after about 6 months of training, including exams and testing on the actual functionality of the product, even bits you’ll never interact with personally. They’re serious about making sure you know what you’re doing before you get within a mile of something that could affect patients.

They also have a pretty strong accountability culture. I shipped two fairly embarrassing bugs my first year and had a very serious conversation with my manager about whether I should continue to be employed since I’d used up about 50% of our team’s allowed bugs for the year. But on the other side, once I got my feet under me, they were very good about recognizing improvement.

Visiting Us 1 year ago

Ha, we were pushing complexity metrics back in 2012. The Security team added it as a PQA step in 2013 when I was there, no idea if that stuck around.

Visiting Us 1 year ago

The state of MUMPS has progressed a lot since this article was written, to the point where most MUMPS developers would probably only vaguely recognize this. Even the "MUMPS" they were using back in 2014 or so was really a higher-level dialect + higher-level framework (Chronicles) that was transpiled down to actual MUMPS. It was more like writing ES2015 + JSX or whatever and then actually executing ES3 + DOM operations.

Source: was on a team that was performance sensitive enough that I spent a lot of time in the actual transpiled MUMPS code that did look more like this article.

And yet, per the spec, new syntax features are allowed to break ASI:

As new syntactic features are added to ECMAScript, additional grammar productions could be added that cause lines relying on automatic semicolon insertion preceding them to change grammar productions when parsed.

So really, the rules are “there are currently 2 exceptions and an infinite number allowed to be added at any time”. To me, that’s worth letting prettier auto-insert semicolons when I hit save.

23andMe's Fall 2 years ago

They've been doing that for months. Scummy behavior tbh. It happened right after the hack, but there's also a new crop of competitors that let you upload your raw 23andMe data, so there's speculation that it's trying to stop the outflow.

If you email them about it, you just basically get a copy-pasta reply restating the message on the site, and if you keep emailing them 3+ times asking for a refund (ask me how I know), they'll tell you you can manually upload identity verification and they'll get back to you in 6-8 weeks with the data.

Svelte 5: Runes 3 years ago

This looks like it’s moving closer to React Hooks, but using the compile step to optimize them out? Kinda like a better React Forget?

It helps that the Colorado Republican party is about as ineffective of a political group as I've ever seen. If they were even moderately competent Boebert's district, Colorado Springs, and to a lesser extent the new district (Caraveo's) would be much redder than they voted the past cycle.

Gotta be this. Spent hours and hours on Folding when Bitcoin was just getting started, if I’d spent a single day mining I’d be retired now. Doubt I’ll see an opportunity like that again in my lifetime.