Discussion about this post

User's avatar
Ayse Guvencer's avatar

Working with startups, and being in tech for over 2 decades, I have learnt something- that coastal- grandmother- adjacent wants you to prioritize incessantly. Period.

The -shall we build this, kill it, add a new feature, bin it- doubts are real, and rightly so.

One thing I find putting sense in the chaos is debugging from the below.

Your startup is an OS- kernel, driver, shell, Gold master release- the churn and retention symptoms that seem like product or GTM issues have a cause at the kernel layer (market, buyer, problem). If the shell (solution) is built on a driver or kernel that never loaded, then that ‘panic’ you talk about sets in along with what I call ‘invisible burn rate’

It is hard to grasp when you are ‘in it’.

Debugging publicly is no fun. But stack fallacy is less and less fun.

Great post!!

No posts

Ready for more?