I'm finding that in this build fast and break things culture, it is hard to revisit a project that is more than 3 years old.
I have a couple of android projects that are four years old. I have the architecture documented, my notes (to self) about some important details that I thought I was liable to forget, a raft of tests. Now I can't even get it to load inside the new version of Android Studio or to build it. There's a ton of indirection between different components spread over properties, xml, kotlin but what makes it worse is that any attempt to upgrade is a delicate dance between different versions and working one's ways around deprecated APIs. It isn't just the mobile ecosystem.
I have relatively good experience with both Rust and Go here. It still works and maybe you need update 2-3 dependencies that released an incompatible version, but it's not all completely falling apart just because you went on a vacation (looking at you npm)
Build fast and break things works great if you're the consumer, not the dev polishing the dark side of the monolith (helps if you're getting paid well though)
As a consumer, I can not remember any feature that I was so enamored about having a week earlier than I otherwise would have, at the expense of breaking things.
No, they didn't do a "quick analysis". They were in a race with Linus Pauling to figure out the structure. Pauling's son happened to leak the fact that Linus Pauling's lab had a triple helix, so they asked the son casually for notes. That, along with Gosling & Franklin's XRays convinced them that their own original model (and Pauling's) were flawed.
I'm surprised they weren't already, if one discards the ethical and moral issues (like one would expect from an Amazon product), they do have a lot of opportunities for working with each others data.
This is just the systemization, scaling of what existed previously. It's a rather predictable pattern at this point in America. Introduction through innocuous means, expansion through a combination of convenience and fear, then systematic expansion once the slaves have become accustomed to the new state of things. It's a rather common ratcheting normalization staircase.
Even public information clearly describes how it is the "CIAs" one trick pony, whether it's orchestrating a "color revolution" for "democracy", instigating conflicts and war to feign innocent self-defense, implementing social engineering and Constitutional subversion, or implementing mass surveillance specifically. It's the same wife-beater and child rapist type pattern of grooming abuse that then feigns innocence and deflects blame to anything and anyone else.
Most people are really not all that different than any run of the mill battered wife (even if only in the making), psychologically. I get it a lot when I point out what a trap and an illegitimate, enemy entity that the EU is (not to pick on the EU, because it also applies to the US and many other places, but it's far more pronounced with the "EU-cultists")... You get the constant predictable defenses of the love-bombing "abusive boyfriend"/wife beater in the making responses. "you don't understand", "the EU really loves me", "you never want anything good for me", "he showers me with all kinds of benefits and slick marketing", "we are going to be happy forever".
It's sad, and as someone that has watched that cycle unfold even in my own family, it's really kind of demoralizing and somewhat depressing to know exactly where it's heading and being unable to counter the forces that have roots a long long time ago, forces of nature. So, the US and the EU will have to suffer that which is predictable and was preventable, no matter how much they wanted to see the world through rose colored glasses.
Maybe for humanity's sake, China can free the world of the scourge of this cycle and the psychopathic, narcissistic, maniacal group of people that causes it all... if they don't just kill all life on the planet because if they can't be in control then no one can be in control.
This particular example of thundering herd isn't convincing. First, the database has a cache too, and the first query would end up benefiting the other queries for the same key. The only extra overhead is of the network, which is something a distributed lock would also have.
I would think that in the rare instance of multiple concurrent requests for the same key where none of the caches have it cached, it might just be worth it to take the slightly increased hit (if any) of going to the db instead of complicated it further and slowing down everyone else with the same mechanism.
> The only extra overhead is of the network, which is something a distributed lock would also have.
Well, There's also the 'overhead' of connection pooling. I put it that way because I've definitely run into the case of a 'hot' key (i.e. imagine hundreds of users that all need to download the same set of data because they are in the same group). Next thing you know your connection pool is getting saturated with these requests.
To your point however, I've also had cases where frankly querying the database is always fast enough (i.e. simple lookup on a table small enough that the DB engine practically always has it in memory anyway) so a cache would just be wasted dev time.
Not sure the eras comparable. One _could_ argue that the earlier discoveries were lower hanging fruit, where it was possible for a single brilliant soul to come up with a new concept. Now it seems to require more and more collaboration.
That said, since the 60s much of the physics landscape has changed. Postulation and discovery of dark energy and evidence of dark matter, of the Higgs boson and the tau neutrino, the incredible LIGO and JWST projects, discovery of graphene, quantum computation in its entirety, topological insulators, memristors, and the entire array of body imaging techniques (MRI, CT) ...
I have a couple of android projects that are four years old. I have the architecture documented, my notes (to self) about some important details that I thought I was liable to forget, a raft of tests. Now I can't even get it to load inside the new version of Android Studio or to build it. There's a ton of indirection between different components spread over properties, xml, kotlin but what makes it worse is that any attempt to upgrade is a delicate dance between different versions and working one's ways around deprecated APIs. It isn't just the mobile ecosystem.
reply