Library

Written code is simply a side-effect of the real work programmers do; create and maintaining a theory as to how the system should behave given the domain and the real world constraints.

Many startups fail despite identifying a real problem and building a product that solves that problem. This explains why, so you can avoid their fate.

A deep dive into time management for early stage founders.

If you’re not willing to throw away your MVP once it’s proven (or disproven) your hypothesis, then it’s not an MVP. it’s a V1.

You never know what positive outcome might arise from a negative event, or vice versa. Remember to keep the big picture in mind, and not be quick to judge.

ELI5 for databases and the complex interactions that can arise in even simple use cases. Great for getting a fresh perspective on organizing data and data modelling problems.

Massive challenges face any startup, and in relation to those, the state of the economy is a minor concern. If you’re the right person making the right thing, now is always the right time.

A deep dive into splitting founder equity, and the pitfalls to avoid. Data is based on 1300 startups, and paints an interesting picture.