Welcome to the Bars Cadence Technical Blog!
Bars Cadence started as a simple script—a small experiment that quickly turned into a passion project. Over time, it has evolved through multiple iterations, driven by my curiosity in music theory, algorithmic composition, and software engineering.
This blog will document the technical journey behind the app, highlighting both the successes and the challenges along the way.
This is the first post of the technical blog for the Bars Cadence project.
What is Bars Cadence?
At its core, Bars Cadence is an experimental application born out of a love for both music and programming. Rather than following a strict roadmap, development has been guided by curiosity—trying out new ideas, learning along the way, and refining the tool through continuous iteration.
Many of the features in Bars Cadence are exploratory, often inspired by interesting problems in music theory, generative composition, and algorithmic creativity.
Why This Blog?
Throughout development, I’ve had the chance to work with technologies and techniques that I wouldn’t have otherwise encountered. Many of these experiments — some successful, some scrapped — have led to fascinating insights that I’d like to share.
This blog will serve two main purposes:
- Technical Documentation – A resource for those interested in the inner workings of the app.
- Engineering Insights – A collection of lessons learned from experimenting with various frameworks, algorithms, and design patterns.
Whether you’re here as a developer, musician, or curious reader, I hope you find value in these posts.
What’s Next?
Future posts will dive deeper into the technical aspects of Bars Cadence, including:
- The evolution of its architecture
- Music theory concepts embedded in the code
- Experiments with AI and generative composition
- Lessons learned from building a small but evolving application
I’d love to hear your thoughts! If you have any questions, feedback, or ideas for future blog topics, feel free to reach out.