Transparency in Development

In these days of collaborative, open source development, it makes sense to be transparent in the process of building software, so that users can know whether to trust a product and invest time in learning about, using and sharing the product with others.

In the past, design agencies have been known as environments where open source software development was not a priority, where secrecy, bourne out of a desire to build proprietary products that could be sold to customers, was, more often than not, the goal of the effort.

My approach comes from a different point of view, where transparency in development creates anticipation, fuels excitement about ideas, inspires participation and builds community as the act of building something together demystifies the process, revealing the steps necessary to move towards a common goal.

I have built many experiments over the years as proof-of-concept projects to try to inspire a different way of working that integrates processes into a unified ecosystem. I have been trying to solve the question of how we integrate business processes into web-based systems. Many of these questions are already being answered by several products. So, the ideas that I had in mind to solve these business process problems are in many ways redundant.

However, the destination is not necessarily more important than the journey. So, my personal blog, newly revived as an update of the Symphony Piano Sonata ensemble, designed by Rodrigo Galindez, developed by Fazal Khan, and updated by me, will detail the steps of my journey. There will likely be missteps and rabbit trails as well. As with many journeys, the path may be fairly mundane for the average traveller. But I may chance upon many pleasant surprises along the way.