I'm not sure how many parts this is going to take. I think most authors actually write the whole article and then find sensible places to split the article. Here's what I'm thinking about for the moment and the basic outline:
- Tools and libraries
- The implementation
- The final project
- Next steps
Over the last 8-10 weeks I have been writing reports using SQL. The database I've been connected to is SQL Server and I have had to export the reports in many different formats including: dot, csv, tsv, text, table, html, and even xlsx. I also needed to email the file to a distribution list and I needed to upload it to an s3 archive. One thing I was hoping to implement was that I was going to be able to produce the same export just in different format. That meant that I needed to store my SQL in glossary form and that I could be assured that the one SQL statement would produce exactly the same results regardless of he format.
I've been using .sh files (bash) and some bash script-foo to get things going. Now I have nearly 50 reports and I feel like I'm losing the library battle. And so the Turbo project begins.
As a historical reference Turbo Pascal, C, C++ and Assembler are where I lived for a stretch of time that represented my greatest learning. (most learning in the least amount of time). So, in part homage and part fond memory and hopes for the future, I named this project Turbo.
(anyone wanting to contribute in any way is welcome)