Leaving Notion for...

Andrey Yurchenkov — Sat, 12 Feb 2022 23:00:38 +0000

This post isn't about development, but it also can be helpful in the day2day work for the software developers.

Why do I decide to abandon Notion in the first place?

I've been Notion-fan for a long time joined it at the early stages. But time passed, and I noticed that it became slow, messy, and complicated. No offline mode makes sometimes the whole thing non-usable.

Obsidian

The main reason I choose Obsidian is because of its approach to storing notes. It uses a local vault which can be located in cloud storage like google disk for the sake of being able to work with notes on another pc and not worry about losing them in case some psycho(could be me???) burns the laptop.

Is it worth it?

In my case, yes.
There is a significant feature gap between these two, but I use it mainly for note-taking so I probably find the ideal tool

I don't:

Use my phone to work on the notes
Use the templates
Share my stuff with others
Use it for database or project/task management

If your use case is similar, consider switching too.
But we'll see how it goes in my case.

Also I have the idea of using private Github repo as a backup storage just in case. Stay tuned.

5 tools for k8s every developer should have

Andrey Yurchenkov — Mon, 07 Feb 2022 03:04:41 +0000

After working very closely with Kubernetes, I created a list of tools used every day. Of course, you can use raw kubectl, but let's be honest - we like comfort and user-friendly tools (for the most part)

Lens | The Kubernetes IDE

Lens IDE for Kubernetes. The only system you’ll ever need to take control of your Kubernetes clusters. It's all-in-1 easy-to-use desktop UI tool for managing your k8s resources.

K9s — Kubernetes CLI To Manage Your Clusters In Style

K9s provides a terminal UI to interact with your Kubernetes clusters. The aim of this project is to make it easier to navigate, observe and manage your applications in the wild. K9s continually watches Kubernetes for changes and offers subsequent commands to interact with your observed resources.

It's something similar to Lens but built for terminal use. Also my favorite one over the Lens. In my workflow I split my terminal: 1st part is k9s , 2nd part is helm apply smth

Kubectx and Kubens

A faster way to switch between clusters and namespaces in kubectl. It's something you'll need when you have multiple environments. Boosts your productivity when you are constantly back and forth switching environments

kube-ps1: Kubernetes prompt for bash and zsh

A script that lets you add the current Kubernetes context and namespace configured on kubectl to your Bash/Zsh prompt strings (i.e. the $PS1).
For multiple environment workflow so you not mess everything up.

For zsh there is a simple plugin superbrothers/zsh-kubectl-prompt which you can also use

kubefwd (Kube Forward)

kubefwd is a command line utility built to port forward multiple services within one or more namespaces on one or more Kubernetes clusters. kubefwd uses the same port exposed by the service and forwards it from a loopback IP address on your local workstation. kubefwd temporally adds domain entries to your /etc/hosts file with the service names it forwards.

When working on our local workstation, my team and I often build applications that access services through their service names and ports within a Kubernetes namespace. kubefwd allows us to develop locally with services available as they would be in the cluster

P.S.

As I mentioned before, I've used these tools for some time while working with the k8s environment. There are a lot of helpful tools for k8s, but I suggest keeping your tooling tight and minimal.

Forem: Andrey Yurchenkov