Can address it by writing code that doesn't depend much on indentation, which also makes code more linear and easier to follow.
Kache
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.
Idgi -- is it saying that every game is either named "X" or "Y's X"?
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"
Seems it depends on which elite/establishment, going by Wikipedia's definition: "populism" is the political stance of "the people" against "the elite/establishment"
So by that defn, both of these examples qualify:
- The people being distrustful of the establishment of medical science
- The people condemning the unfair practices of a monopolistic/oligopolistic establishment
wanted to add something to the end of a for-loop, but had too little indentation
To address this, I prefer reducing length & depth of nested code, so the for
/while
is rarely ever not visible along with everything inside it. Others have success with editors that draw indentation lines.
opening up new/anonymous scopes
I occasionally use Python nested functions for this purpose
I find it's possible to operate Python as a statically typed language if you wanted, though it takes some setup with external tooling. It wasn't hard, but had to set up pyright, editor integration, configuration to type check strictly and along with tests, and CI.
I even find the type system to be far more powerful than how I remembered Java's to be (though I'm not familiar with the newest Java versions).
All methods? Of course not. Just methods like these.
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.
I agree with the author overall, and I think it can be more straightforwardly stated. IMO it's the idea that wrong abstractions are even worse than other ills like duplication or god classes/modules. It's also reminiscent of "modules should be deep".
I prefer that, though (it's in my calendar, but I don't have to accept). I really can't stand Outlook's email-based calendar workflow.
One of the best tutorials on really "grokking"
git
concepts, and it's online and interactive: https://learngitbranching.js.orgFor 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.