It is the defecal standard though.
So a bunch of people who fail on their first attempt, and they pass the second (or third) time. So, of all people who eventually pass, 70-80% took the test twice or more.
Corollary: in any given exam, 20-50% of all exam takers are there for the second (or more) time. So the total number of first-timers is considerably less than 100% and I’m guessing that their failure rate is greater than 50%.
All junior devs should read OCs comment and really think about this.
The issue is whether is_number()
is performing a semantic language matter or checking whether the text input can be converted by the program to a number type.
The former case - the semantic language test - is useful for chat based interactions, analysis of text (and ancient text - I love the cuneiform btw) and similar. In this mode, some applications don’t even have to be able to convert the text into eg binary (a ‘gazillion’ of something is quantifying it, but vaguely)
The latter case (validating input) is useful where the input is controlled and users are supposed to enter numbers using a limited part of a standard keyboard. Clay tablets and triangular sticks are strictly excluded from this interface.
Another example might be is_address()
. Which of these are addresses? ‘10 Downing Street, London’, ‘193.168.1.1’, ‘Gettysberg’, ‘Sir/Madam’.
To me this highlights that code is a lot less reusable between different projects/apps than it at first appears.
Couldn’t agree more.
And now that this occurred, and cost $500m, perhaps finally some enterprise companies may actually resource IT departments better and allow them to do their work. But who am I kidding, that’s never going to happen if it hits bonuses and dividends :(
Typically you need about 1GB graphics RAM for each billion parameters (i.e. one byte per parameter). This is a 405B parameter model. Ouch.
Edit: you can try quantizing it. This reduces the amount of memory required per parameter to 4 bits, 2 bits or even 1 bit. As you reduce the size, the performance of the model can suffer. So in the extreme case you might be able to run this in under 64GB of graphics RAM.
I think that’s a better plan than physically printing keys. I’d also want to save the keys in another format somewhere - perhaps using a small script to export them into a safe store in the cloud or a box I control somewhere
You need at least two copies in two different places - places that will not burn down/explode/flood/collapse/be locked down by the police at the same time.
An enterprise is going to be commissioning new computers or reformatting existing ones at least once per day. This means the bitlocker key list would need printouts at least every day in two places.
Given the above, it’s easy to see that this process will fail from time to time, in ways like accicentally leaking a document with all these keys.
I agree, so much legislation is broken, the legislators aren’t doing shit, so we citizens need to fix it!
But we could start with the right to repair.
What about the people who lived in the Americas or the Pacific 1800 years ago? These people could not have heard of Jesus as missionaries could not have spread any word to them at this time.
(And while I’m about it, Christianity was a whole different thing back then - the Trinity hadn’t been invented, there were multiple sects with very different ideas, what books would be in the New Testament had not been decided, etc etc. People with beliefs of that time would seem highly unorthodox today, and the Christianity of today would be seen as heretical by those in the 3rd century, so who’s going to heaven again?)
Purgatory was invented for the purpose of not sending good people who had not heard of Jesus to hell. But still, these people were denied their chance to get to heaven which seems mighty unfair.
I had a Sinclair QL which pioneered the keyboard. It wasn’t great - it was far behind the Acorn BBCs and the Commodores) but it was quite usable.
There was significant vertical travel, and there was variation in the push the key gave back - increasing to a point of no return, then a quick downward movement to the thunk of the end of key travel.
I could type moderately fast on it.
The reference if you haven’t seen it.
Dara Ó Briain is a legend!
If you’re pushing everyone’s buttons it’ll end badly.
stop using it
Are the MAGA crowd actively cancelling products now?
“DI frameworks” are Satan’s farts. Classpath-scanning nonsense that turns compile-time errors into runtime errors. Not only is your Ctr still coupled to your Svc, but both are now coupled to Spring.
Let’s qualify this: DI frameworks that use configuration files to specify the dependencies are Satan’s farts. You can use the DI pattern but do the injection in source code to get full compile-time type checking and all the benefits of a fully packaged JAR or similar binary. The root of the evil is having text files as part of the packaging, and not having the tooling to treat those files as part of the source code at build time.
Not even if the pole was the meanest, toughest slav in eastern europe
Note the caveat:
With PYTHON_GIL=0 set, I spot-checked a few tests and small programs that don’t use threads. They all seem to run fine, and very basic threaded programs work, sometimes. Trying to run the full test suite crashes pretty quickly, in test_asyncio
This is exactly the answer.
I’d just expand on one thing: many systems have multiple apps that need to run at the same time. Each app has its own dependencies, sometimes requiring a specific version of a library.
In this situation, it’s very easy for one app to need v1 of MyCleverLibrary (and fails with v2) and another needs v2 (and fails with v1). And then at the next OS update, the distro updates to v2.5 and breaks everything.
In this situation, before containers, you will be stuck, or have some difficult workrounds including different LD_LIBRARY_PATH settings that then break at the next update.
Using containers, each app has its own libraries at the correct and tested versions. These subtle interdependencies are eliminated and packages ‘just work’.
This commenter heiroglyphs!
In many texts, writers play with different or unusual ways of sounding out words perhaps to make the visual representation better. Ugh. Here’s a link if you’re interested in learning more
Not quite. The drug causes heart irregularities in some people at therapeutic doses, and this killed some of those 17k people. It just doesn’t quantify it here.
You’re in the process of describing a Cybertruck, just the misfitting panel ‘teeth’ aren’t rotating