I switch between Solarized light and solarized dark.

A few shortcuts that I use a lot are really basic, but very powerful. Frankly, I’m always surprised when I’m pairing with a co-worker and they don’t know about them.

Cmd+p to open the fuzzy file finder search. This is a huge one and I’m shocked when I see people hunting through the file explorer to find the file they are looking for.

Cmd+shift+f to open the fuzzy workspace text search. Basically grep your workspace for code.

F1 or Cmd+p+> - Action menu. So many good actions in here from running formatters, to toggling light/dark mode, reload window, etc.

Ctrl+r (mac) - Fuzzy search for recently opened projects/files. Hitting Enter opens it in same window or Cmd+Enter opens in new window. I use this sooo much and most people don’t know about it.

Cmd+n to open a new vscode window. Although I rarely use this as I almost always just use Ctrl+r.

VSCode has great fuzzy search and if you use it, it lets you move around your code and codebases so much faster.

Installing CLI tools so when in the terminal, you can run code <path> to open vscode at that working directory.

Can’t remember the last time I used File->Open to open a new project window.

Cmd+b to open/close the left drawer

Cmd+shift+e to open the file explorer.

Came here to say exactly this.

I was going through these motions a few months back and bearblog was a top choice of mine. However, after doing a little more research, I found Hugo and a hugo-bearblog template. Combined with Github hosting I’m able to get the power of bearblog, but a lot more control over it. I’m free to take the entire thing anywhere I want, and it’s all under my own domain.

Separately, I had originally tried Jekyll, but I found the install process to be cumbersome. I pegged it as being a ruby-based install. I loved being able to just brew install hugo and having it just work from the get-go.

Zero-downtime for us using Kubernetes. It’s built-in. Deployment gets updated, new pod comes online, once it’s healthy, the old pod goes offline.

We do have a little code to handle graceful shutdowns to properly finish any active requests before going offline, but that was a trivial addition.