itsdanweston

Yeah, the main tools I use are:

- Alacritty with ZSH for my terminal

- Neovim as my IDE

- TMUX for multiplexing (different terminal windows/panes/etc)

- Colima so I don't have to use Docker Desktop

Everything else is just the standard CLI tool, like git, docker, etc.

My workflow is that I open a new TMUX session per project, use Neovim to edit the code and then commit with git.

Neovim has plugins for things like debugging, database access, and basically anything you could possibly need.

There are two main things I do. The first is to make sure everything runs as expected, with no faults, no security risks, deployments are successful, etc.

The second (and personally more important) thing I do is try to remove as much friction from the dev's experience as possible. I go and chat with the devs, find out what parts annoy them, where they get stuck, and what level of control they want to have. Then I go away and try and resolve those issues.

For me, DevOps is more about Dev than Ops. I started as a dev, and nothing kills productivity for me more than waiting for the pipeline, not being able to find where logs are being sent, not being able to get access to the Kube cluster and so on. So I do what I can to make the devs happy, happy devs generally equals better outcomes.

I like making microservices, and bonus points if you run it locally on Kubernetes as well. Something were you have to coordinate multiple moving pieces, internal/external traffic, etc.

I try to use as few things as possible, here's the highlights:

- Alfred -> Launcher and some small tools

- Rectangle -> Simple keykinds to move windows around, easier/simpler than a full tile manager

- Alacritty -> Anything other than the default Terminal

- Obsidian -> Best note-taking app I've found

- TickTick -> Todolist, Calendar and Habit Tracker, syncs with phone, love it

Uncommon Sense Teaching, it's about how we learn from a neuroscience perspective, and how these insights can be applied to teaching kids (and ourselves).