svsucculents

That's the tip of the iceberg. You can do anything in awk.

for a in *.c do awk 'function lensort(a,zerp, x,tmp) {for (x = 1 ; x < zerp ; x++) {tmp = a[x]; if (length(a[x + 1]) < length(a[x])) {a[x] = a[x + 1]; a[x + 1] = tmp}}} /^(int|void|char|struct|long|float)/ {while (x < 2) {getline ; arr[$1] = (substr($0,1,1) == "{") ? "\n" : $0 "\n" ; x++}} END {lensort(arr,v); for (c in arr) {printf "%s\n",(length(arr[c]) > 0) ? arr[c] : ""}}' ${a} done

It's C. Learn C and you know awk. The only awk worth using is G(nu)awk anyway.

This is what glue languages do with data. Not what SQL does with data. Why ever would you want it to?

Almost every small company with the sole survivor has this story. You know where all the bodies are, have done everything once and then discover some uncomfortable truths. You are right to get out in your early 40s. Don't wait.

10 years and looking for an out. One thing to be aware of is that long stays are probably better with a large company with a slower rate of change. Staying at a small company for a long time is riskier in that you end up becoming more of a generalist, become the goto and the goat and are in real danger if the company changes leadership late in the game. Find that as an older individual trying to get back into a 9-5 workplace after 10 years in a specialized environment (doing everything) does not translate well to the current market.

You are speaking to the inmates writing the asylum. Give it up. This is the 4chan of the enlightened.

Totally disagree with this parental assessment of a language. It certainly doesn't apply to spoken languages or most ideal communication modalities. I think you want to fix your problem: which isn't a problem for someone else. See this everywhere on this site: SV kultur and the catch22 pronouncements of the correction generation.

What a mess.

RCS stored directory based modules with tasks in subdirectories. Make or shell script style module execution as part of each task dir + variable files containing settings for the install task. Json configuration files that define all necessary module params (ex:log, task selection, stop on error, initialization, build command per task, etc...) remote scheduling of module/task execution via per agent sysv ipc command queue serviced by a JSON-RPC microsvc which allows both serialized and non blocking task scheduling by queue priority.

devops as a field of serious study is pretty pathetic. I wouldn't trust a devops 'grad' to do anything or know anything. But with the resurgence in certs and boot camps and other snake oil making $$ why not?

That's why you don't use AWS 'auto' scaling. Every application has it's sweet spot and it's simpler to roll your own when you know best.

After years of working with cfengine then ansible I finally went to a bespoke BSD ports work alike with optional client/server and json configuration components. Never looked back.

Le Guin is hard to stomach as you get older. I can read CS Lewis and Tolkien with a forgiving eye but not Lewis. Rowling is terrible. Susan Cooper should have had her success.