Only calling os.Exec over and over again is not what I envisioned when I started building my own shell. So, in the spirit of first things first, I implemented a few of the commands I use on a daily basis to make the shell actually usable. This makes the whole thing immediately feel a bit more real and also provides some good learning opportunities.
I needed something light and simple to take my mind of work, side projects and have a break from dealing with AI all day long. So what is more logical than starting to build your own shell. Totally makes sense, right? Right?! I am not exactly sure where this will go, but I got a few ideas of what I am missing from most shells.
Learning something completely new you have never done before is not always the most straight forward process. While working on the 3D avatar for my personal assistant I started to pick up 3D modeling and some very basic drawing skills. Well, mostly 3D modeling, drawing is on the back burner right now. The thing is once you hit a roadblock things get frustrating really quickly.
It has been some time since I last looked at peripherals for my gaming system. The last change I made was to replace a falling apart keyboard with a Keychron Q3 with wooden keycaps. (Sadly not the best idea as I learned 18 month later.) However, I got curious, and that’s how I spent this week testing two new mice: The Logitech Pro X2 Superstrike and the Pro X Superlight 2 Dex. Bad news: Both are being returned. Good news: I’m gonna write about why.
I think this is the first week in which I do not have spent any time on feature development on the coding part of LazerBunny. I was using my coding agent, router and controller every day and things just worked. A pleasant surprise to be honest. Instead of rushing into working on the rest of the stack I only implement a single feature for the brain.