I think a better term should be "minimally proficient pilot". One that passes all the requirements, but not by very much. That's the lowest common denominator you should be targeting for certification.
JSON Resume needs more contributors, pretty badly. It's a great project, but it's languished a bit over the years and some tooling have broken. I encourage anyone who uses it to throw a little time into the codebase. It's not that hard/complex of a project.
> Equip fully the world with solar and wind and the trains will have to leave their stations when the wind blows and not at any other moment.
Wind just doesn't stop blowing across the world all at once. When one place is in the doldrums, another is likely windy. With a sufficiently connected grid, a large deployment of wind turbines can smooth out production in ways smaller, regionally focused deployments cannot. I posit that a global distribution of wind power is _more_ available than a regional one, not less, as your comment seems to imply.
Here's the thing: this settlement is remarkably near Vancouver. Like a 20 min drive from downtown, maybe 20km total distance. This isn't some remote part of the province, this is literally in Vancouver's backyard.
It goes even further than that. Building bigger rocket engines is really hard because turbo-pumps and nozzles don't scale well. Smaller rockets are exponentially cheaper to design and produce. See the RD-170 program for example: it was easier to just use 4 nozzles instead of 1 to achieve the same output.
Not all bottom-outs are created equally. I bottom out on my MX Clears but the increased stiffness dampens the force to the point where my typing is comparable to the latest apple keyboards my colleagues use. I don't even use rubber dampeners which would further reduce sound.
Interesting that this article is posted on the eve of Burning Man. This year should be especially hot. Every year I bring a simple swamp cooler, this year I'm going a step farther and bringing 2, plus an active ventilation fan and ducting. My total power consumption is about 18w, not too shabby to bring down the temps about 15f in ~1000ft^3 space and well within my modest solar panel setup.
Look inward. The problem is likely in your company's management style. Instead of designing a big complex thing all at once, design a truly simple MVP-- and have your engineers involved in pruning back complex or low value features. THEN build the product. It usually far far far harder to debug a broken system than to build a new system from scratch. What your engineers are telling you is to reduce your requirements, think carefully about them and to build a stable system you can then develop on top of.
You're right. I goofed on my analysis. Instead of chose, it's indeed a factorial. You're also right, you can chose up to 9 dots, so indeed it is up to 9! combinations. Thanks for catching that.
On my Galaxy S9+, I have 4 buttons: power, vol up/down and a stupid useless bixby button. Ignoring how to put it into 'password' mode, each of these buttons is effectively a bit. I assume you need at least 1 key to register an input (otherwise wait for a pause which I won't consider), so you get 15 possibilities. I think you could make a reasonably strong password using 4-8 chords (15^4-15^8 possibilities). Anyways, it's certainly better than those swipe passwords with an effective length of 9 Cr 4 == 128 which are readily seen and copied by nearby people.
Any idea what the switch mechanisms look like? I'd like to dream that you can customize your keyboard with an array of cherry switches to your own preference.
I agree. It's VERY hard to believe a 14 year old wrote and produced that content. It's too complex and engages in content that a child would have no real interest in talking about.
Great article. I had to integrate SAML 2.0 in a product not-too-recently and it's absolutely horrible compared to Oauth workflows. Maybe it's the different ecosystem: most IDPs are big, bureaucratic institutions with tons of middlemanagement where OAuth providers tend to be tech orientated players looking to scale their product with minimal friction. Anyways, tons of documentation is outdated, or too light on details or orientated towards management rather than developers.
passport-saml [0] really deserves more love for how (mostly) wonderful it is at making integrating SAML into node applications.
A lot of people are saying that the new-but-not-really-new React Context API and useReducer hooks are sufficient to cover redux. My team isn't convinced, we see immense value because we're big fans of using Redux Saga-- a model that isn't well covered using Context or hooks, although we do use those APIs as well when needed.
That's the sign of a good checklist. The idea is to free up mental processing to focus on harder issues. Let the doctor focus on the hard stuff and not spend excess time trying to remember the simple stuff.
When I read the title, I got excited thinking that there would be a discussion about how the law of averages tends to fail to represent a diverse population of humans. It turns out that if you build around a set of average (statistical mean) measurement, you'll end up building a product that fits _nobody_.
That's the thing though. Is my team really the exception? When you look at the highly immersive web that product managers and customers have come to expect, you simply can't build it without javascript. Once you've crossed that bridge, is it really easier to finagle some event handling using vanilla js/jquery or pull down create-react-app and get all the tooling necessary to 1-click-deploy to Heroku, S3 or Github pages and not have to deal with the multitude of bugs that hand rolled events and state can cause?
Why do we keep seeing posts like this? My team absolutely needs React/Redux/Sagas/Webpack/whatever-you-want-to-hate-on-today, to ship and yeah we ship our backend with Docker. Why do I know we need it? Because we have years of experience in our workflow and we understand the problems we need to solve in the development workflow and timeline our company uses. Do you know who doesn't understand our needs? Someone writing a low-quality post about how _their_ specific needs can be met with existing technology. Please just leave me be and go focus on solving your own problems, I wouldn't be using this technology if I didn't think it worked better than anything else.
If you don't persist JWT in localStorage or sessionStorage, how would you handle page reloads? You'd have to rely on a session cookie and get a new JWT from your auth service. You'd solve XSS but get CSRF.
Storing a JWT in localstore isn't the same as storing a password in plain text. JWTs are indeed non-revocable, but they are also non-durable (ours expire after 24 hours) and cannot be renewed without a refreshToken. Most people also do not rely on JWTs to write important information (like password reset) because there are more secure alternatives for these specific use cases.
As an aside, if someone gets script access to your SPA, you're already very far up shit creek. If your user types in any sensitive information like a password to login you've lost the war. Securing the JWT is the very least of your concerns at that point.
Choosing a trade-off between half-life and radioactive mass would be a fun engineering task. Plutonium-238 has a half-life of 87.7 years and would be long depleted before 55 million years are up. Longer term isotopes would need a ton of mass to get you there.
As someone who lived in Palo Alto for almost a year without a car... there is so much to be desired for public transit. Outside of the few blocks near University, it quickly becomes a walking wasteland. My bike, on the other-hand, was a divine gift from the heaven and, when combined with CalTrain, enabled a fairly large world-bubble.
The US has banned overland commercial supersonic flights, so yea, going cross country is still an issue but there's still very lucrative oceanic routes that would be unaffected. Also, there's large, sparsely settled parts of the US, Canada and Russia that aircraft routinely fly great circle routes over where sonic booms would be of little to no concern.
California has as many people as all of Canada. There's _tons_ of people in this state to null your point. Maybe in the midwest your argument might hold true, however.
Suspicious how this comes right on the heels of negative publicity about Huawei's IP theft and possible infiltration of global telecom networks. I suspect someone might be wanting to apply pressure and forcing Huawei to respond.
I love reading about the Chinese efforts in developing a modern turbofan engine. For whatever reason, they just can't build a good medium- or high- bypass turbofan in-house. They're latest WS-20 is basically a clone of the CFM-56 and previously they spent decades developing the WS-6 and WS-10 that never met expectations.
This is a big deal because the Comac 919 is ready to go but without a powerplant, they're having to turn to Western sources for an engine. The same thing happened with the J-10 project a decade ago and again recently with the J-20. Without a reliable powerplant, you can't build good airplanes and you can't easily reverse engineer a precision turbofan.