Open Source Guidelines

Open-sourcing software follows Thinking Machines’ values of being a builder and a team player—only this time, within a larger community. Open-source enables us to participate in the larger practice of peer production, and gives us the opportunity to understand our users and co-developers well. To such, there are two main open-source guidelines that we should follow:

Technical Guidelines

We must strive to maintain a baseline quality on our software projects, this goes even outside our open-source work. A well-maintained project says a lot about the company, so we need to exert rigor in keeping our codebase healthy.

On Documentation

Documentation should be given equal priority to a program's business-logic. Remember that when we write documentation, we write for the person next to us.

On Code

Code is the core of our project and if left unkempt (especially with multiple contributors from multiple backgrounds, coding styles, etc.), might grow into an unmaintainable mess. Open-source software also demands a certain rigor in writing code.

Community Guidelines

Once a project is open-sourced, we should expect that Issues and Pull Requests will come from the community. As representatives of the company, we should act in the most professional way as possible. Below are guidelines that should codify how we would relate to our co-creators.

Some tricks and tips


Understanding poverty in the Philippines with artificial intelligence

Using publicly accessible datasets, we developed a low-cost AI model to estimate wealth for the entire Philippines and analyzed what geographical factors are associated with wealth levels.

Send Your Friends a Digital Holiday Card With Our AI Holiday Greeter!

Generate your own digital holiday greeting card with artificial intelligence and beautiful data visualization and share it with your loved ones this holiday season!

Thinking Machines wins Best Paper Award at NeurIPS 2020 ML4D Workshop

Thinking Machines presented at NeurIPS 2020 workshops, ML4D and AI + HADR, and won Best Paper at ML4D!