I think when you're starting a company, it's really useful to ask the question, why now? And this is like, pretty cliche for startup stuff, so if you've heard of it already, apologies, but I do think it's a really useful framework. And that question of why now? Can be societal. Maybe there's some new cultural trend, perhaps it's regulatory. Some law has been passed or appealed. I like the technological version. And for us we saw drones in 2012 and WebGL as few technologies that were happening where because these technologies were happening, new possibilities were suddenly there.

But we're like, why would you do anything in photo editing if you're not on the phone? And so we felt like we were kind of building the wrong place and then eventually sort of shifted our attention to design, which I had been a design internet flipboard and that helped kind of help me realize what would be possible there.

And I would just say don't just go for an idea because it's kind of working. Go for an idea that you really care about because even if it doesn't work, you'll still learn from it and you'll still have one.

In software development, technical debt (also known as design debt[1] or code debt) is the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer.[2] Analogous with monetary debt,[3] if technical debt is not repaid, it can accumulate "interest", making it harder to implement changes. Unaddressed technical debt increases software entropy and cost of further rework.

Common causes of technical debt include: Ongoing development, long series of project enhancements over time renders old solutions sub-optimal.

Parallel development on multiple branches accrues technical debt because of the work required to merge the changes into a single source base. The more changes done in isolation, the more debt.