I get to “indulge” in the tech now because the developers that was hired to develop the MVP has been doing a terrible job.
I know once the product is in a better place i will need to shift my attention elsewhere and not go back to what feels “comfortable”.
On one side, you have technical knowledge. At the extremes you have people who can’t even power on a laptop and expert developers in 10 languages and SREs and everything else.
Something (almost) completely orthogonal is how often you apply your technical knowledge in tasks that don’t fall into your job description. On one side you have a completely hands off manager. The other extreme is full-on micromanaging.
This basic analysis means there are at least 4 kinds of managers:
1) the non technical manager who is also completely hands off,
2) the non technical manager who always interferes with technical people’s work (maybe only based on buzzwords),
3) the technical manager who is also hands off,
4) the micro-managing technical manager.
More technical knowledge is almost always a good thing (although too much knowledge can be pointless for work purposes - if I can write ASM blindfolded but we are just writing restaurant websites, I’m not getting a real professional benefit).
More technical action is not always an advantage, to you (more work) and to others (micromanaging).
The reason this works with startups at an early stage is, simply, that few tasks are outside the manager’s job description, since they are essentially founders+marketing+finance+everything else. However, when you have to scale, you need to act less from a technical standpoint even if your knowledge is useful to understand stuff.