There is a reason why we have prioritisation and bug triages.

I am working on a project with an associate and one of the first things I did was install a kanban board to keep track of issues and features, and to have a place where we can share information on the state of the project and build.

This way, we can be honest and communicate about the compromises between time until a feature is ready to use, and not worrying about things that they are not concerned about. If a feature is going to make things much better for their business, and not break things that are already there, and the current bugs only occur in unlikely circumstances? Ship time.

All software has bugs. We need to test the software to be aware of the bugs that exist and take appropriate action.

The alternative is Duke Nukem Forever and Time

Of course, this is an engineering tradeoff. You can also ship broken code that makes things worse. The engineering aspect is that you make the correct tradeoff between the reality of what can happen in reality with what you are trying to achieve in theory.

https://newdawnowl.itch.io/microtonal-grid

I made a pure code, microtonal step sequencer that makes it really easy to try out what microtonal music is like.

I’m also very proud of how quickly and easily I implemented the conway’s game of life into it, only took me about an hour or so.

I’m not proud of how long it took me to get rid of the “clicky” bug.

I made a basic 16 step sequencer using many of the ideas shown there, using pure JS. You can check out the source code in gitlab to see how they can be implemented.

It also allows you to go beyond the 12 note western scale, though it doesn’t do any ratio tunings.

https://newdawnowl.itch.io/microtonal-grid
https://gitlab.com/NewDawnOwl/microtonalgrid