1,413 karma · joined January 19, 2012
http://willstamper.name
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.
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.
> 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.
Does moderate alcohol factor in? Being obese? What’s your line where a personal choice that has some risk disqualifies you?
Git already has an established format for machine-readable metadata, trailers. There's even a built-in command for working with them, git interpret-trailers. This pulls data-for-computers into an area that should be data-for-humans.
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.