[bikingbismuth]

I enjoy reading things like this. It’s posts like this that have helped me build my command line text processing skills over the years.

If you are early in your career, I suggest you work on these types of skills. It is surprising how often I have found myself on a random box that I needed to parse application logs “by hand”. This happens to me even in fancy, K8-rich environments.

[cassianoleal]

I agree.

Just FYI, Kubernetes is abbreviated to k8s, not k8.

> K8s as an abbreviation results from counting the eight letters between the "K" and the "s".

https://kubernetes.io/docs/concepts/overview/

[tentacleuno]

This is very similar to "a11y"[0] and "i18n"[1]. The abbreviation of words using this technique has become surprisingly common in the software industry.

[0]: https://www.wordnik.com/words/a11y [1]: https://www.wordnik.com/words/i18n

[JohnMakin]

Some code challenge sites offer all their challenges in bash - I highly recommend working through these if you want to get better at this type of stuff. Some problems are surprisingly simple, others torturously difficult.

[s3arch]

can you suggest few?

[reidjs]

Is there something like leetcode for string manipulation exercises like this?

[keybored]

> If you are early in your career, I suggest you work on these types of skills. It is surprising how often I have found myself on a random box that I needed to parse application logs “by hand”. This happens to me even in fancy, K8-rich environments.

It’s surprising how many times you have to ad hoc parse due to the tools being so poor. It’s endemic.

[eternityforest]

Regex can help you with fairly complicated source code edits too, like changing the order of parameters in some multi language project where there's no automated tool that can just do it.