FWIW, some sites—like Amazon—allow multiple users on the exact same email address (distinguished by password or other identifiers)
2,815 karma · joined August 26, 2011
Declarative code describes the _output_ or final desired state of something.
* fat arrow functions
* classes
* template strings, multiline strings
* destructuring and ...rest values (splatting)
* elvis operator (foo?.bar?.baz - in TypeScript)
honorable mention
* list/iterator comprehensions (made some good progress in the ES speccing process, but ultimately didn't land)
I think I like it!
However, I think I'm still going to be using Yarn for the foreseeable future. Would like npm cli to prove itself for a while.
I believe it. Their new grocery was really quick to fill in (I walk by it every day, and was able to see progress while it was being built)
Their internal privacy controls are extensive.
As a human, it is nearly impossible to access someone's data, even when debugging code/ML models/etc.
And when you do need to, it requires exhaustive oversight/approval, and _everything_ is audited.
(I also think it makes sense for TypeScript given JavaScript idioms; it mainly falls over when the caller has to interpret some very complicated error messages, however)
Recent efforts to strip browsers down to their core functionality, and provide a world where the current web is effectively userland code:
* web components
* service workers
* Houdini
Imagine a future where browsers just implement these low level concepts, and HTML is defined as an (open source/community) library that all vendors bundle as part of their browser.
And then, also consider how much overlap there is here with traditional operating systems. Your next device OS could be just another layer on top.
I've worked in downtown Seattle for the last 10 years, and frequently use the bus system. (caveat: I'm a white male, so generally in less danger, and may be more oblivious):
* I've seen a few brawls (~5) in all that time; generally (all?) swiftly broken up by police
* Haven't experienced weapons (or items used as them), whatsoever
* I've seen (a handful of) needles in that time, but never on busses
* Lots of panhandling, people yelling things, etc.
* 2nd/3rd around Pike/Pike is _definitely_ sketchy, and will make you feel uncomfortable walking around there; but it's also where I work atm: so I frequently am in that area, and haven't encountered much.
Consolidation is also hard on the trucker side, where there's a ton of fragmentation in the kind of work they perform and access to it
> This problem is, by the way, the thing that takes most of my time, 60-70% of my time at a guess. I once spent over a week trying to get a broken LDAP server to work - my boss had forbidden me to implement my own LDAP server - but after a week of struggling with a broken LDAP sever written in C and badly documented I had a lapse of memory and forget that my boss said and accidentally implemented a server from scratch in Erlang during my lunch break.
> To be honest it wasn't a full LDAP sever, but I didn't want a full LDAP server. I only wanted a couple of commands to work, and that was pretty easy to fix
Knowing when to flip the table and reimplement is probably more challenging than anything else outlined in the article.
Joe probably had a good sense for that. Most programmers, however, do not seem to (requires tremendous breath of experience!).
It takes a certain amount of arrogance to assume that you understand (or can predict) the entire problem space along its warts. And if you're wrong, it's often another poor programmer down the line that pays for it—not you.
Source: worked there, on a ML focused team.
The best they get are aggregations (sufficiently large enough that you can't identity a person). Specific user information is only available if the user explicitly opts in to share it, and is scoped to the specific case for analysis.
It makes training/diagnosing ML models a challenge, to be sure
The thing with Big Ideas, is that they're often iterations of existing ideas, but just different enough that you can make a case for a fresh start. (And who doesn't want a greenfield project) Plus, the cost of experimentation is far less while you're not supporting a massive userbase.