The _Autobiography of Malcom X_ was co-written by Alex Haley, the author of _Roots_. _Autobiography_ was required reading in a "Black Political Thought" course I took years ago. But it was inspirational for me too.

At our company, we actually built ETL-Framework-agnostic wrappers, monitoring, logging and scheduling tooling around the different ETL tools we used for four different ETL Product Frameworks we used: Microfocus COBOL, Torrent Orchestrate, Datastage (which incorporated Torrent) and Abinitio. The wrappers invoked the ETL command, reformatted and consolidated logs. For scheduling, we relied mostly on CA Autosys, instead of whatever scheduling mechanisms came with the ETL Product.

We found this approach made it easier to transition from one product to another. As it consistently faster to plug the ETL framework into the supporting framework than to implement everything a new ETL Product offered.

As we move from our on-prem environment to the cloud, we hope we can implement a similar strategy even if we have to switch the support frameworks.

That would be invoke tasks. https://docs.pyinvoke.org/en/stable/getting-started.html, which I first encountered in fabric: fabfile.org, which has the fab utility and fabfiles (analogous to Makefiles) but is so much more.

It is a pain to work with invoke now. It is all find and dandy for the basic features but you going to hit the seams soon you start trying advanced stuff. Looks like the project is going to be abandoned.

What is advanced?

btw, the project is old and it is useful with the current feature set. There is an issue with the bus factor but is common for many tools.

Awk is advanced in the sense that it is a programming language by itself. Years ago I had to migrate an old version of an Informix database to a newer version. The old version did not have tools to export the database as DDL and DML statements. So I had to create a tool myself to do it. The system did not have perl installed so I had to use awk. It worked nicely enough.

Generally, that mutable data is on externally mounted volumes or stores though and not in the container itself, right? Except for what is read into container memory and written out to temporary or work files.

True, but restarting a service, remounting all the data, waiting until everything has synced etc, just to apply a security patch is a big downside of the immutable approach

Right, but my point is that a bad deploy can cause data corruption, which usually isn't fixed by just redeploying the previous version.

"Scrumfall" sounds like a rejected James Bond movie script.

Is this post about being willing to look stupid or about not being afraid to ask questions? In my own experience, I was more afraid of asking questions because I was afraid it would expose me as not paying attention in class or not being prepared. I was afraid of being embarrassed by the question. I suppose one could say this might also be read as afraid of looking stupid, but stupidity itself is ironically not as simple as some might believe.

I remember the first time I heard the statement: The only stupid question is the question you don't ask. This statement bewildered me, because I thought I might be the one that asked "that" question. If this sounds confusing, I most likely read that statement as "the only stupid question is the the one you shouldn't ask and if you don't know what makes a question stupid, you're probably too stupid to know."

This fear of asking stupid questions made me unwilling to take math courses beyond Geometry. I ended up getting further math education when I started my IT career in 1990. I overcame my fear of asking questions in the course of doing my student teaching assignment before that.

Yes. I bought this on vinyl when it first came out. This was my first introduction to King Crimson. And surprisingly, when I bought Court of the Crimson King in college, I could hear the thread that connected their first album to the first album by them I ever bought. The more I listened to it, the more I took it apart, the more I broke it down, it remained consistent.

I still think it's good! I wish you were here to hear it!

One of the links to wind cowls in London suggests they finally found a peaceful use for the Daleks!

Incorporating the "learning x the hard way approach", which is about typing the code, rather than just copying and pasting the code, also aids with learning quickly and giving more lasting power to the lesson. The best part of this is the mistakes you're more likely to make by typing, which forces you to look more closely at the original code so you can retype it correctly. I remember much more that way. Even more than that, making such mistakes may draw more attention to the object in error and consequently learn more about that object and how it fits into what you're trying to do.

Came here to mention typing vs. copy/pasting. When going through a tutorial, don't copy and paste. Type out the code. I turn off code-completion in my editor as well.