Linux

So whether you work as a developer, SRE or with devOps, a big part of your work happens in the terminal. And what ever you do, if you do it a lot of times, you will get faster. But repetition alone can only get you so far. And more often than not, when only comparing one to one self without seeing what is possible, you never evolve. I don’t know how many times i have hold down the left arrow key, watching the cursor slowly move left because i need to switch out k get with k describe, or add sudo, or fix a typo in the beginning of the command. At the same time thinking “I should really look up what the hotkey for jumping to the beginning of the line is. But now I’m already half the way, so I’ll just keep holding down the left arrow key and look it up later.” ...

tl;dr: rwx = 0111 = 7. -rwxr-xr-x = 0111 0101 0101 = 755. Ok, I want to make my file read/write/execute for me, and read/execute for group and others, easy: chmod 755 my_file.txt. Of course I know this. Want all permissions for everyone? 777. But, whenever I want anything else, I always have to google it. Well… NO MORE! Understand it to remember it After years of always forgetting and not really knowing how the permission for files are in unix like systems, I finally, when looking it up, found a way to remember it. And I found the way to remember it so cool that I want to share it with you! (Also I wanna make sure I remember it, so writing a short post is the perfect way). ...

tl;dr: Use Flameshot to take screenshots and edit them directly before saving to a file or to the clipboard. Download at flameshot.org/download. Flameshot Flameshot is my favorite screenshot app and I have been using it for years. I’ve shown this app to lots of co-workers over the years since I find it super practical. I have to admit that windows and mac has stepped up their screenshot tools the last years, so everything isn’t as unique as it was the first time i tried out Flameshot. Still I find it the best tool for taking screenshots and I use it daily. ...

tl;dr: After installing docker-desktop, I needed to use sudo to run commands even though my user is in the docker group. Fix: Change docker context back to default. Introduction - The problem After installing docker-desktop, running docker commands only returns errors. How did this happened? It was working just fine earlier. Let me start from the beginning: Recently I’ve been thinking about learning Kubernetes. And I’ve started doing some research also thinking about completing some of the Kubernetes certifications. ...