Though odds are highest for carbon-based, simple from it's abundance.
Onomatopoeia
joined 1 week ago
Thanks for this - a reasoned, easy-to-grasp explanation of missions, without a lot of technical jargon.
It's this kind of writing that's needed (from any technical field) for those not in that field to understand it. I'm in IT, and work diligently to provide this kind of explanation to decision-makers. It's not easy, when in your head you see all the "but this" at the technical level. We have to sacrifice high-resolution detail to provide a "good enough" image for people to comprehend. Sometimes that means being "technically inaccurate" - which then gets unnecessarily criticised.
I wish magazines like Scientific American (which has seriously gone down hill) wrote like this more.
Wow, I never made that connection
And we already do this - every culture has a form, some more ingrained than others.
During WWII (and the Cold War), Allied analysts, spies and diplomats found learning Russian particularly difficult for just this reason.
Are the links you added from the article or some others you found?
What kind of douchebag do you have to be to behave like this?
How many languages do you speak perfectly?
OP's English is pretty damn good.
Hahaha, so he does!
Please tell me you write opinion pieces for a living, and where I can find them.
Except decaffeinating coffee really messes it up.
You'd be surprised how hard it is to find manuals these days.
Manufacturers have taken to:
-
Not printing them at all
-
Hiding them behind paywalls with exorbitant prices
I've never met an engine that doesn't need valve adjustments, even with hydraulic lifters.
Now the adjustment period is far longer today, like in the 100k miles range.
Just be glad you rarely see shim/bucket adjustment these days. Boy was that a bitch.
Very good point about Agile.
As an end-user (that is, the IT staff that will be deploying/managing things), I prefer less-frequent releases. I'd love to see 1 or 2 releases a year for all software (pipe dream, I know). Once you have a handful of packages, you end up with constant change to manage.
I suspect what we end up with is early adopters embracing the frequent releases, and providing feedback/error reporting, while people like me benefit from them while choosing to upgrade less frequently.
There are about 3 apps that I'm a beta tester for, so even I'm part of that early-adopter group.
Another hero we didn't know we needed.
Have my grateful uovote.