It's been a while since my last posting and I feel compelled to say some things as well as introduce everyone to my curses project.

This is the second of two interrelated posts talking about the IDGAF development process, using my setlist management software project as a prime example of what not to do when developing software. This part examines the workflow process itself and the resulting codebase of technical debt.

The first of two posts talking about some software I wrote to solve a need, which does in fact do its job really well, but because I'm following the IDGAF approach to the development process - the thing is a trainwreck under the hood and you could say I totally get why windows is closed source. This first part talks about why I needed to make the software, walks through the user-interface and other such surface level things. In the next article I will cover more specifically what clear examples of technical debt are shining brightest and how they can be paid off properly.

Taking the Hugo site I made for One State DJ, I'm now re-freshing this personal-slash-info-tech-related site.