Why aren't there more startups based on programming languages and software analysis?
There's definitely a need for SOMETHING, as developers have so much pain.
I was recently on a panel where someone asked this question. I didn't have time to answer then, so here's a thread. 1/
There's definitely a need for SOMETHING, as developers have so much pain.
I was recently on a panel where someone asked this question. I didn't have time to answer then, so here's a thread. 1/
There's often a gap between the creators of "principled" programming tools and the needs of working developers.
There are two common technical assumptions: 1) code correctness is a top priority and 2) it's possible to understand the whole system.
Often, neither hold. 2/
There are two common technical assumptions: 1) code correctness is a top priority and 2) it's possible to understand the whole system.
Often, neither hold. 2/
In programming languages and formal methods there's the dream of "soundness:" if there's a bug, the tool will find it.
People don't want to know all of their problems. They want a prioritized list of problems that matter. This technical goal is often at odds with user needs. 3/
People don't want to know all of their problems. They want a prioritized list of problems that matter. This technical goal is often at odds with user needs. 3/
Developer may want perfection, but what they need is something that fits with their everyday lives.
A big part of this is fitting in with existing work flows. Asking someone to switch over their tools, or use a language or tool disconnected from other tools, is a nonstarter. 4/
A big part of this is fitting in with existing work flows. Asking someone to switch over their tools, or use a language or tool disconnected from other tools, is a nonstarter. 4/
I also often see programming tools people ignore design.
Design isn't about increasing prettiness, it's about reducing friction to solving valuable problems.
Today, there's a design gap in between many cool programming technologies and the tools they could become. 5/
Design isn't about increasing prettiness, it's about reducing friction to solving valuable problems.
Today, there's a design gap in between many cool programming technologies and the tools they could become. 5/
tl;dr to get wider adoption, programming tools need:
+ meeting developer work flows where they are
+ interoperability with existing dev tools
+ incremental improvements
+ design that fits developer priorities
- focus on 100% guarantees
- focus on building a new universe
6/
+ meeting developer work flows where they are
+ interoperability with existing dev tools
+ incremental improvements
+ design that fits developer priorities
- focus on 100% guarantees
- focus on building a new universe
6/
Obviously this is easier said than done! I've been on a multi-year journey of this at @AkitaSoftware and we're still figuring a lot of stuff out.
But the more we talk about this, the more we have hope of making developers' lives better with what is technologically possible! end/
But the more we talk about this, the more we have hope of making developers' lives better with what is technologically possible! end/
• • •
Missing some Tweet in this thread? You can try to
force a refresh
