NFC-capable dongles work great for this.
678 karma · joined June 22, 2014
There is demand for all sorts of things the society in general considers harmful.
If one chooses to offer it anyway, be prepared for the criticism.
Excuse me?
https://www.theverge.com/2019/1/25/18197137/amazon-rekogniti...
The code referenced here is pretty extreme NOT providing the guidance, hence my response to the poster defending the extreme and ridiculing the good practice.
Ridiculing the value of documentation does not make you look smart.
It rather hints at lack of experience with truly complex systems or collaboration in teams.
I still doubt you cover "all cases". Even for a simple problem (e.g. given three integers interpreted as side lengths, decide if they result in a equilateral, isosceles, or scalene triangle), the number of cases will be daunting (in our case: 65, see Robert V. Binder, "Testing Object-Oriented Systems. Models, Patterns and Tools").
Despite the effort you chose to invest into your framework, I still doubt you achieve anything close to this depth within your system and the underlying stack.
That‘s a bold claim. Reeks of hubris though.
Healthy scepticism would convince me a lot more that we can trust your products.
You may also consider if maintaining that test suite for „all cases” is a good investment of your time.
Back in the 80s some "minifigs" may have had sad faces, but never angry/violent ones. That changed a lot over time.
I'd really want to see the data on which you base this belief. Watching US politics from Europe I see the Democrats roughly matching the European center. European "left" has no voice in the US!
http://euromaidanpress.com/2021/05/26/protasevich-is-a-dissi...
Where truth dies so easily, make your own judgement.
That was 20+ years ago, and Python filled this space with its easy definition of classes and candy syntax. Where Perl overdid on hackery, Python may have overdone on sugar -- but it clearly won the love of the masses.
Now, 25 years later, the ship has probably sailed for Perl, and -- while I still prefer it to sed/grep/awk and Python for simpler tasks, I don't see it conquering Python space for more complicated processing.
I recommend the whole Guide wholeheartedly.
A good card is one that highlights what is important for you to memorize. While preparing the card, one should reflect what are these parts and how it fits into the larger whole so as to reflect this in the card. This helps go beyond mere memorization, and apply spaced repetition also to some higher-level concepts.
Example: for a recent exam I took I had to memorize extinguisher types and to which types of fires they can be applied. You can stuff it into a dumb deck ("[Class A]= [common combustibles]"), or you can put it into a hierarchy or turn it into a relationship ("[Class A] extinguishers cannot be applied to [electrical equipment]] because [...]. [Class C] should be used instead.")
For more information, see e.g. https://medschoolinsiders.com/medical-student/anki-flashcard...
Please check out platformio. It made a whole world of difference to me.
IANAL, but can well imagine this could have an impact on the interpetation of purpose.
In shortest words: variable declaration is also used as I/O format specification. Pretty much all of IO is just reading into a buffer, and the values are automatically mapped for your use. Sure you can use the same method in pretty much every general-purpose language (mapping C structs etc), but here it comes just natural.
Not if you started dealing with real-life record format specifications, including fixed-precision numbers for currency, dates etc.
The use case was processing of record-based inputs in an administrative context, based on a technology millions of times less powerful than current hardware, yet still able to sustain a massive administration (old-school banking, anyone?)
No, you will not write a compiler or a kernel module in COBOL, just like you won't write it in SQL, APL or Matlab. But for the purpose it was built for, you'll be a lot more comfortable than in most alternatives.
If we educate our front-end developers like that, web security will remain an unwanted bolt-on providing minimum protection and no regard for privacy.
It is a shame these topics are not addressed in more detail, as they will likely remain more useful than the tool of the day.
May I suggest treating that as an opportunity?