But would you pay for it?
My employer's paying for my access, and I only find it a bit useful here and there
Maybe my company gets a great discount or something, but if they would pay me the subscription cost to give up Copilot, I wouldn't miss it
I think your ideas are too non-practical/specialized/advanced/low-level for your stated goal of 'digital literacy". They read more like college intro/followup course material and are too esoteric to be readily absorbed, esp by generic teenagers, even if they've self-selected to be "lightly interested".
I really dislike code like that. Code like that tends to lie about what it says it does and have non-explicit interactions/dependencies.
The only thing I can really be certain from that is:
doAnything();
if(doAnything2()) {
doAnything3();
}
I.e. almost nothing at all because the abstractions aren't useful.
Must be proprietary, bc TOTP shouldn't be blocked by age of the device
If you were reviewing a "non-trivial" PR from me, I'd recommend not squashing because I would've broken it up into readable atomic commits.
You're getting a lot of conceptual definitions, but mechanically, it's just:
keeping state (data) and behavior (functions) that operate on that state, together
At minimum, that's it. All the other things (encapsulation, message passing, inheritance, etc) are for solidifying that concept further or for extending the paradigm with features.
For example, you can express OOP semantics without OOP syntax:
foo_dict.add(key, val) # OOP syntax
dict_add(foo_dict, key, val) # OOP semantics
But surely there's a practical middle between "shoot first, ask later" and "sit and wait an hour"
A title as uninformative as the single . commit messages he suggests writing.
Bare minimums of typo, refactor, whitespace, comments are barely any effort -- less than the thought it takes to name variables and functions.
I really can't agree with completely meaningless messages like minor and .
Unfair how? It's paid by employers, so kinda makes sense to me, i.e. employer caused the loss of livelihood, so they pay for the benefit to the recently unemployed.
This claim site's privacy policy seems to reserve their right to use your submitted data for marketing and promotional purposes...
to improve our marketing and promotional efforts
We want to provide you information that is valuable to you. If at any time you wish to be taken off our mailing lists ...
That route already exists today as "the web", where the "latest" JavaScript source is downloaded and JIT-ed by browsers. That ecosystem is also not the greatest example of stable and secure software.
Dedicated incremental static type checkers for dynamic languages already exist. In particular, Pyright for Python is fantastic and in many ways surpasses the type systems of classic typed languages