Some say coding is the new literacy. We disagree. Our goal should be for machines to understand humans, not the other way around.
Google and OpenAI are developing amazing algorithms to make engineers more productive. But that's not much help if you can't write code in the first place.
So how do we go from ideas to code? Could machines do that for us, if given the right information?
This is what Stepsize is all about.
Luckily, there's plenty of data lying around describing how people created software.
Developer inefficiency costs $300 billion in global GDP each year.
The number 1 cause for inefficiency? Technical debt. Engineers say they could be 50% more productive.
So why do companies let technical debt get out of control?
There's a vicious cycle at play.
Engineers hate tools like Jira — they weren't designed for them. They're in the browser, and engineers spend all their time in their code editors. And you can't even attach code to issues, but that's what technical debt is all about!
So technical debt doesn't get tracked, or if it does it languishes in backlogs.
Without visibility on technical debt, engineers can't manage it. Tech debt piles up, productivity drops, and bugs creep into more and more releases.
Enter Stepsize, the engineer's frontend to issue trackers.
We let engineers interact with tools like Jira directly from their code editors. And being in the code editor, it's super easy to link code to issues, without even uploading the code itself.
That gives teams the visibility they need to break the vicious cycle.
Every engineer knows about the issues affecting their codebase thanks to inline annotations.
And during planning, it takes a couple of clicks to dig up all the issues that could impact a feature's delivery.
No more surprises. Teams can make deliberate decisions about which debt to pay back, and when.
Our customers include scale-ups like Snyk and enterprises like Sainsbury's. They address 50% of the issues they track and say they've been gifted time to work on features.
Once we have access to all this data describing how software was built, we can start working on our AI.
At first, it'll do a small part of the work for engineers. But we'll keep improving it, and engineers will need to write less and less code.
Until the AI is so good that we don't need to write code anymore.
Join us on this incredible journey to empower anyone to create software! You’ll have a huge positive impact on the world.