139 karma · joined November 9, 2014
I don't have the same reservations about using the work of problematic people, so I don't typically check for that info.
Off the top of my head, an example might be accepting opiods to manage pain, despite the tons of damage pushing the drugs has caused Americans as a whole.
Do yo actively avoid using technology invented or heavily influenced by problematic people?
The language would not be worth using without it.
If the source was checked carefully, you'd notice a checked-in node_modules dir.
If you didn't check the source properly, you could install a module that seems like it'ss using a known package, but really is using its own malicious version of the global package.
Currently trawling your archive
He built telemetry systems before the Internet was we know it.
The title and opening paragraphs gave me the impression they felt they were moving away from microservices, but maybe I didn't those bits correctly.
Sounds like they just redrew their service boundary, from Integration APIs to Business Function.
Centrifuge sounds like a new service deals with connecting to integration APIs, so they've replaced 140+ services with one.
Another service they've spun up is Traffic Recorder, and its responsibility is to eliminate the need for http requests when testing integrations.
Feels like the biggest change is going from so many repos to a monorepo.
I've been a huge fan of message-based architecture for years yet there was still a number of things for me to learn from this.
An example is "a message should be self-describing". Its something I instinctively do, but if asked about I'd never mention.
Good piece. Thanks for sharing!
In my opinion this trait exists for all genders.
It sounds like a valid reason for being able to auto-install add-ons.
https://www.disruptingjapan.com/taking-akiba-back-otaku-dmm-...
If you delivered the initial thing in 4 weeks vs 8 but you'd spend way more in future development and developer time, would you say you made the right decision?
To put it another way, delivering the wrong thing faster doesn't make it any more right.
Would have been nice to have something tangible to point others to ...
Do you write about doing this in vanilla js? Would like to keep a collection of "Just React please" docs that I can point people to.
Major Key: Avoid compile steps as long as possible.
No Babel, no Webpack, no browserify, no JSX. You can use React without any of them. You'll get to them when you really need them eventually. Maybe. Only one of the above I use is browserify.
Why?
As a developer, your key job is keeping complexity down. Doesn't matter if everyone else implicitly gets it. If it's complex to you, don't feel forced to use it. If you can get by without it, do so. When you eventually get it, it wouldn't be that much of a struggle.
You'll still need to look up apis, function args and options, but that's just forgetting how to tell the computer what you want. Very different from not understanding why you need each piece or how to put them together.
It's not easy to admit one's weaknesses and grow from them.
Glad you were able to and doubly glad you were able to share the story :)
What happens when there is a temporary network issue?
Might it be more useful to allow a reconnect period before the inbox disappears?
You think this is a game??