The Valuable Dev - A Guide to the Zsh Auto-Completion With Examples
Sunday Greetings Valuable Developer,
I hope you had a great month and that everything’s going well on your side!
I’ve spent a lot of time the last month trying to figure out where I want my career to go. After doing a lot of brainstorming and digging in my experience, values, and purposes, I think more and more about becoming a technical consultant for companies fighting the climate change. I’ve some sort of strategy to achieve this goal, but it will take some time…
If you have any thought on the subject, I would love to hear them. Don’t hesitate to hit “reply” and let me know!
Meanwhile, I’ll soon begin a new job as a developer in a promising startup, hoping to be a team leader again soon.
But enough about me. My series to learn Vim continues this month with:
A Vim Guide for Veteran Users
We’re going deeper and deeper into Vim to discover keystrokes for completion in INSERT mode, abbreviations, why the viminfo (or shada) file is useful, how to use sessions, and more!
Updates
- I’ve made two videos for my Youtube channel explaining the basics of the CLI find (part 1 - part 2).
- I’ve published an article about awk on my other blog The Mouseless Dev.
Resources
- Avoiding the alignment traps - An old article from 2007 but still very actual. It’s about the misconceptions the managers of an organization can have about IT, thinking only about alignment between IT and the business but forgetting the cost of complexity.
- A day in the life of a professional software engineer - This is a funny parody showing how much technical interviews have nothing to do with the daily job of a developer.
- git for computer scientist - If you want to know how git works under the hood, here’s a visual summary.
- A brief history of containers - Interesting article about how containers evolved overtime.
Speaking about technical interviews, I’m thinking about writing an article about them; I would love to hear your opinion and experience on the subject!
Mouseless Tools
When parsing plain text in your shell, it’s sometimes a challenge to filter and get the result you want because the structure of the output is different from one CLI to the other. A possible solution: always having the same structured output you can parse the same way whatever the CLI, like JSON for example.
The tool jc transform the output of common CLIs (like ifconfig or lsblk for example) into JSON, and jq let you parse the JSON.
If you want to have a shell which is designed to always have structured output, you should try nushell. It’s far from being a standard, however, but it’s an interesting concept.
Let’s Connect
If you want more information about the content of this newsletter or if you have any question, you can hit the wonderful “reply” button. I’m always happy to receive emails.
Similarly, if you think this newsletter is boring, if you didn’t like my last article, or if you have any feedback of any sort, don’t hesitate to reach out.
Thanks a lot for your interest in my work and see you in a month!
Matthieu