sunasra

Thanks for the feedback.

The main motivation behind building this tool was to make onboarding easier on Apache Airflow. There was no standard structure for a airflow projects and setting it up on local can be a nightmare sometimes. The simple CLI tool makes it very easy to create and test your project locally before deploying it to your production or staging environment via your CI/CD.

Right now we are using a docker-compose file which brings up all the Airflow services but we are also currently working on providing a command to control individual process.

Qubole is not a cloud but a self managed Data Platform. Deploying on Qubole means just putting all the Dag files on the machine (AWS/ GCP/ Azure) where airflow is running. Qubole provides out of the box solutions for running airflow on your cloud with a click of a button. We offer bunch of different things (Spark, Presto, notebooks, etc) and have a great eco system build around Airflow.

Unconference - a meeting twice in a month where anyone from team present on any topics except controversial topics like politics. This helped everyone to learn completely different things

Initiatives: More and more initiatives and idea discussion - because of this everyone started thinking everyday to build innovation and became adaptable to take risk.

1. Research & Finalize architecture design before jumping to code

2. Take code as documentation. This helps to debug things faster

3. Focus more on problem solving than language/tool priorities

4. Listens more and always towards exploring and experimenting new things. This improves breadth knowledge