You might find my survival guide for founders who depend on devs to get things done useful. It covers topics like how not to lose key information if a dev leaves, preventing endless rebuilds and framework switching, keeping devs busy vs. keeping them productive, and ensuring product builds don't go off the deep end.

As an example, here's the chapter on estimates: https://superstruct.tech/blog/estimates