Nice tool to test:

Git hook scripts are useful for identifying simple issues before submission to code review. We run our hooks on every commit to automatically point out issues in code such as missing semicolons, trailing whitespace, and debug statements. By pointing these issues out before code review, this allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks.

As we created more libraries and projects we recognized that sharing our pre-commit hooks across projects is painful. We copied and pasted unwieldy bash scripts from project to project and had to manually change the hooks to work for different project structures.

Read More

https://github.com/minimaxir/hacker-news-undocumented

My true personal opinion based on what customers asks and what co-worker uses:

1. docker , docker-compose is still the dev winner
   1. Podman is rising but it has no extra feature, because docker support the rootless mode too.
   2. Ignite – Use Firecracker VMs with Docker images (github.com/weaveworks) Super-fast VM based on container are gaining traction. Driving force are cloud providers, but this idea can eventually be helpful for some service providers.
2. K8s + Helm keep going K8s is "the" abstraction layer for Cloud providers, to some extent. K8s offers tons of extension points, for automation tools and for cloud providers. The only downside is its heavy lifting: for very simple deploy (less than 3 physicals nodes) it is still an overkill in pricing and management overhead. Also it needs at least a speedy 2-Core CPU to work. Cost rising due to inflation can have a negative impact on "Fat"-K8s solution.
3. Jenkins pipeline sucks It is sad to say, but GitHub actions & similia (like GitLab pipelines, Bitbucket pipelines and Cloud provider similar services like AWS CodePipeline) are a winner. Jenkins declarative pipeline are elegant, but its declarative language depends on Jenkins plugins, so you must keep track of them. Also, it is frequent to build groovy library on top of it And when you need to upgrade Jenkins from time to time, you face a lot of refactoring on pipeline syntax, and it is increasing difficult to estimate.

As a mid-life greabeard that started my career on Z/OS / MVS writing JCL and running COBOL and SAS jobs, I like JavaScript. It doesn't have the obtuseness of C, the ultra-strict type-checking of Pascal, the verbosity of COBOL, class chaos of Java, the mind-bending notation of PostScript, nor the escapee from the loony bin mentality of SQL

I was trying to explore a way to build a client/server application in Typescript; after some failed experiments, I found something better: Next.js offer the ability to build a React application and to render server-side its dynamic components.

So you can have the best of the two words: static pre-rendered pages pushed to the browser, and server side components (for doing your overwhelming BORING queries you know :)

You can easily use bash to search-and-replace on variables…

f="/home/alice/myfile.md"
$ echo ${f//.md/.pdf}
/home/alice/myfile.pdf

$ echo ${f//alicee/bob}
/home/alice/myfile.md

$ echo ${f////-}
-home-alice-myfile.md