building a development environment

I just got my desktop computer out of the shop. It has a fresh installation of KDE Neon, Developer Edition installed, with one terabyte SSD and one terabyte HDD of hard drive and 64 gigabytes of RAM, with an Intel I7 processor, with 16 cores. I figure that is lower mid-range quality.

I will be slowly build a development environment on it. I’ve never really done that before, so it will be a learning process for me. I have spent a lot of time learning how to set up and use some of the tools, like Zsh, Vim and Tmux, but I’ve never really used them in a development environment before. I’ve just been reading books about it and tinkering with the tools.

I will use this blog as a journal, describing the process along the way. Many of the posts will be simple notes. Others will be more elaborate stories.

I’ve been working on writing books this summer and neglecting the website. This will give me a good reason, and a good way, to start adding content. This blog will be my journal.

KDE Neon

So far, the developer edition of KDE Neon is not like a normal operating system. It is not like the high-performance desktop on my laptop. I’m having to turn things on manually.

I have installed several applications that I like using. At first, I started using the command line, but then stopped doing that and started using KDE Discover, for installing all the applications as Flatpaks.

Flatpaks will make my individual applications just a little bit more secure. Figuring out how to get all the right libraries installed in all the right places will be another adventure. Take your time. Keep reading the manuals and other literature about the software.

Figuring out how all the pieces of Linux fit together and work with each other will be a complicated puzzle. Figuring out how to manage all the different facets of Linux will be a complex learning adventure.