One of the best tutorials on really “grokking” git concepts, and it’s online and interactive: https://learngitbranching.js.org
For programming, start with buildings things for yourself. Be practical, start small, and iterate, regardless if you consider the previous iteration was a success or failure. I’ve heard good things about https://automatetheboringstuff.com/ (in Python) in this regard.
Can address it by writing code that doesn’t depend much on indentation, which also makes code more linear and easier to follow.
In recreational climbing, skin calluses and surface abrasion aren’t usually much of a concern compared to tendon health. Skin heals light damage quite easily.
However, it’s not uncommon for a new (or experienced) climber to develop their muscles beyond what their own tendons can take. Since it takes tendons so long to strengthen, it’s common to need managing the risk of finger pulley tendon injuries in climbing.
Also, I do not know how these nuances apply in your context of your medical condition.
Call their bluff!
If they’re SO concerned and want help signing bans for imaginary problems into law, there are plenty of real issues worth trading for in exchange.
E.g. from now on, schools nationwide are additionally funded to both prohibit litterboxes for students that identify as cats and provide free and healthy school lunches.
There’s the practical distinction between “everyone can do it with some dedicated intent” (so few actually bother) vs “everyone can do it on a whim”
Not surprising that PDF comments were being used as a task list/tracker. In the same manner, Google Docs supports “@-mentions”, “assign to”, and “resolved” functionality for comments.
All you can do is send feedback to Adobe somehow and hope they add that feature back in. In the meantime, best to find an alternative workflow.
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
I’ve created a Google spreadsheet to accomplish this sort of thing: Split Payment Calculator
It’s got formatting and locked areas to help layman usage, but it’s ofc still a spreadsheet UI and not a dedicated app. A bit of math proficiency and spreadsheet formula knowledge helps.
Could be replicated on other spreadsheet software like Excel or Calc, although Sheets solves a lot of problems at once, like accessibility, sync, versioning, sharing, etc
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 .
Seems more applicable to an imperative style, and IMO even still the advice is too dependent on special/actual case details to be generally applicable as a “rule of thumb”.
This is just one specific example amongst many of how redundant logic could be simplified because sometimes the branch is an implementation detail and you want to push it down, and sometimes it’s not and you want to push it up.
Just the commonly repeated mediocre rules-of-thumb-you-should-follow (but not always) stuff.
Yeah, the article’s takeaways are of little substance and perhaps even misguided
If you’re coming in from zero, a good place to start is https://www.hedycode.com/
Hedy is a language specifically designed for learning. The things it does to ease the learning curve:
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.
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”.