Windmill is exploring how to make developer tools (source control, build, and test) cloud-based, simple, and easy.
Every good codebase we’ve worked on has a testing document:
“If you’re working on the UI, run test suite X. If you’re working on the DB layer, run test suite Y. Running all tests in Y is slow, so use command Z to test one file. Or command ZZ to only do one test case. But don’t forget to run lint first to catch dumb mistakes. Install the linter with steps A-K.”
Every bad codebase we’ve seen locks this in the senior developer’s head.
The product we’re building will unlock this knowledge. Every time you save, Windmill uploads your change to the cloud and immediately runs the best analysis (lint, compile, test, etc.) It gives you live, intelligent feedback that makes your inner loop tighter.
Unlike your IDE, it’s faster and deeper because it runs in the cloud.
Unlike your CI server, it’s part of your inner loop, running on each save and keeping you in flow.
Windmill uses your workflow with no extra sync or push commands. We integrate at the Unix level (filesystem and processes). We use machine learning to run the right test first so you get fast feedback. You keep your editor and our plugins pull error messages from Windmill.
Developers waste time waiting for their development tools.
Continuous feedback makes developers more productive.
Our product is powered by new abstractions that make it easy to build reactive developer tools. Our insight is the common shape of developer tools: they’re composed of functions over immutable snapshots of filesystem state. When you express your tool in this framework, Windmill can run your tool at the right time, in isolation and in parallel.
Our technical hypothesis is that this framework will open up new possibilities for development tools, like how MapReduce opened up data analytics, or how Deep Learning opened up AI. More cloud capacity will let developers waste less time waiting.
Our business hypothesis is that we can turn cheap cloud compute time into valuable developer productivity. We’ll have revenue and positive gross margin starting with our first customer. Customers can make their developers more productive by increasing their budget.
Continuous feedback makes us all more productive.
We want to build an organization where everyone can succeed; not just white cishet male software engineers with good pedigrees. We need to be diverse to have enough teammates and perspectives to build good products.
We’ll do the work of inclusion to help everyone succeed. We’ve started by donating every month to orgs that make tech less toxic (e.g. Black Girls Code, Code2040, Hack The Hood, Project Alloy). We want to help explain why these orgs are important. We’re a partial sponsor of the diversity tickets for this year’s GothamGo.
We’re currently tiny (two people, NYC-based, VC-backed).
We’re publishing this post because we’re looking to hire people that want to help build the next generation of tools, and figure out how to make our peers more productive.
Dan Bentley — Ten years as a software engineer at Google: Google Code, Open Source Programs Office, internal build tools/continuous integration, Google Sheets. Two years on internal development tools at Twitter. $2.56 check from Donald Knuth.
We saw Google change office productivity tools by building a technical foundation for cloud-based collaboration. We’d love to do that for developer tools.
Originally posted on the Windmill Engineering blog on Medium