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.

WET/DRY-ness is like a property of code -- a metric or smell perhaps, but not something to goal towards. That's like asking whether you drive fast or slow and whether we should all drive faster or slower.

https://www.hedy.org/start

For someone learning programming from zero, it was specifically invented to be:

Hedy is the easy way to get started with textual programming languages! Hedy is free to use, open source, and unlike any other textual programming language in three ways.

1. Hedy is multi-lingual, you can use Hedy in your own language
2. Hedy is gradual, so you can learn one concept and its syntax a time
3. Hedy is built for the classroom, allowing teachers to fully customize their student's experience

Adding to the points above:

At the end of the gradual progression, Hedy becomes vanilla Python.

An aspect of the 3rd point is having an online editor & execution environment, so you don't need to deal with setup.

After completing the Hedy lessons, can follow up with other learning resources like freecodecamp.org or codeacademy.com.

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.

Wonder what makes it so difficult. "Cobol to Java" doesn't sound like an impossible task since transpilers exist. Maybe they can't get similar performance characteristics in the auto-transpiled code?