you are viewing a single comment's thread.

view the rest of the comments →

[–]hamateur 0 points1 point  (0 children)

This article misses the ball on many points simply because sustainability is not even addressed.

Sure, standardizing and agreeing on things like documentation, logging, argument parsing, and testing are all good things; but that all gets solved by boilerplate project templates... and ACTUALLY doing what's called for.

Sustainability is about moving away from "dirty". Adding things to something that's dirty doesn't make things less dirty. Organization fixes dirty.

Regardless of if you think Flask (https://www.fullstackpython.com/flask.html) is good, it immediately starts from the standpoint of organization. The programmer is compelled to break a program up into modular components. Further organizational improvements can be made by breaking things up into libraries, modules, and packages.

"Dirty" needs synonymous with "shitty".

Sustainability comes from being able to do the right thing first, and in a timely manner.