Sounds like RC quadcopters society -- everyone knows DJI, but they make fan guards a part of the frame. Guards and props are the most fragile parts, a consumable really. Something an enthusiast often carry spares for, to quickly swap on the field for any other RC quad, but with DJI you need what, send the whole frame to factory?
1. Maintain a large enough project. Not create, but support.
2. Do it for at least couple or few projects.
If project is too small, any architecture works fine. "Large" can be in terms of lines of code, but better in terms of people who ever worked on it, or even better -- teams.
At least two different projects is to have something to compare. I've seen people stuck for decades on one project and not knowing any modern ways to solve a problem.
But often the architects who get promoted because they created, not maintained a project. Especially visible in Google, as you don't get promoted for maintaining anything, only for shipping something new (and better jumping off as soon as possible afterwards).
Counterintuitively, people in the best position to be architects are actually side contractors from head shops, who get invited to maintain an existing project no one from a company is willing to (as they all jumped off where promotions go).
First, they have to maintain an architecture, and second they did it on several projects, so can compare. The downside though, is if they bill by the hour, the tend to over-complicate architecture to bill more hours.
2. Explicit types give context, and if a project guidelines do not enforce type hints, as many don't, then it's hard to see what happens there.
3. Monkey patching and operator override -- I mostly stumbled upon that with "smart" types like ORM objects. Combined with 2. makes it very hard to review.
So I almost always had to download the change and review with IDE help. So it's not just code review anymore, it's manual testing.
Sometimes they are wrong (as they are more like a comment than a compiler directive).
My first task in any project was to figure out why devs don't have error highlighting on for bad types (often it's "it was red so we turned it off"), but good luck forcing others who don't do type hunting to start doing it when "it slows us down".
Printing munitions is not as long as scaling up production to print up munitions. Russian war showed that it will be too late to scale anything once the enemy trench in.
No, they wouldn't, and they don't have it because they have chosen not to. There is something called an escalation ladder: you do not threaten to leave or kill your partner just because she spilled milk on your floor. That is the same reason Russia did not use nukes, and why other nuclear armed countries involved in conflicts have also avoided using them. The same logic applies here. Another example is that the US could bomb the Kharg island containing Iran's oil infrastructure, but that would be a major escalation. Iran would then have no reason to show restraint and could bomb the oil infrastructure of the Gulf states, creating a worldwide crisis.
US stopped bombing Iranian oil infrastructure when Iran responded by taking out a chunk of Qatar LNG infrastructure for a few years [0]. This example shows the escalation ladder and also proves that Iran does not need nukes for this conflict (so far at least....)
There are far more dangerous countries with nuclear weapons than Iran (such as Israel). If Iran had nukes, we'd all be safer as Israel/US would be faced with MAD and would be unable to use nuclear weapons against Iran.
My understanding is that brain is composed of way more neurons than required, for resiliency. So if it gets a "bruise" in some part, when even a large portion of the cells are dead -- it can still function at 100%. Like a programmer without a finger. The problem is visible only when all the cells in some part are dead.
That's why crows, with their low brain mass are pretty clever (and why all arguments equating brain size and smartness are wrong).
Crows (and certain other bird species) have a peculiar forebrain (different in structure but similar in function/evolution to the neocortex in mammals) with neuron counts rivalling primates. So the nr of neurons still matters, but likely not across the entire brain.
Yep. And my point is that too many people seem to judge intellect by brain size or mass. Something like "Neanderthals must've been smarter than Sapiens, because their brains were larger". Or "chimpanzees are smarter than gorillas because gorillas have very small brains", which is all true, except for the word "because" (gorillas are leaf-eaters, so they did not have evolutionary pressure to be smarter, no need in more complex hierarchies, and maybe less proteins for the brain).
Obviously an M1 chip is “smarter” in terms of raw accuracy for eg matrix computations than any equivalent wetware despite being much? smaller. Performance per watt at least at that task has to be an ocean of a difference.
my understanding is that extream migrators actualy consume (use as energy) parts of there own brains durring there epic flights, and other species do something similar in the winter and regrow parts of there brains every spring.
It is true that they can shrink some organs to reduce weight and store extra fat, but the brain is not one of them. Would be pretty bad, because brain cells can't regrow like e.g. a liver can.
Which target audience of github needs extra verbosity in the commit hash, though? Once you know it you know it; if you don’t know git you aren’t the target audience; etc. Saying /user=foo is no better than ?user=foo if your audience can work it out without confusion from your unadorned paths. We have a great deal of history with filesystems showing that people are capable of keeping up with paths that lack key names if exposed to and familiar with them, and if the filesystem isn’t being constantly randomized.
reply