What kinds of problems make you curious enough to investigate?
Not necessarily problems, but I often take a look at what I or others take for granted or as a given.
I'm always curious about what could possibly be overlooked due to familiarity or investigating what assumptions we've all been making.
Question 2 of 7
How do you decide what to work on next?
I ask myself or others "what sucks" or "what's fun?" and then I try to make less suck or make more fun.
Question 3 of 7
What got you started on this?
Frustration with the millions different tasks that everyone has to do all the time. What's especially frustrating is all these tasks are just slightly different enough to demand our full attention.
I want to reclaim all that time for everyone so we can spend time on things that matter to each of us.
Question 4 of 7
What have you learned about yourself through this project?
My bias i'm constantly fighting is to not overcomplicate. It's a constant process of learning what to drop and how to simplify anything I make.
Question 5 of 7
What does progress look like for you at this stage?
When a user is so happy with something I've given them that they can't censor themselves and say something like "holy shit bro, this is fucking perfect" completely unprompted.
Question 6 of 7
What’s a constraint that’s shaping how you build?
We're a small team who have given ourselves a pretty aggressive timeline to demonstrate value in our idea(s).
So, our biggest constraint is *quickly* choosing the right directions to focus our energy and *quickly* being honest with ourselves and changing direction when something won't payoff as expected.
Question 7 of 7
What’s one thing you’d want to share with first-time builders?
You absolutely must understand your limits and manage your energy appropriately. Without knowing how far you can safely push yourself you'll risk being out of gas at very critical points when it matters the most.
FreeScan.app
Developer tools
Free website audit for SEO, security, accessibility, and design