Solid advice.
One thing that I also became aware of is to not care a lot about workflows, and don't let workflows from the engineers leek into the system.
The reason why I say that is that at some point I worked on a system (first to design and implement it) that for me was very nice and ergonomic, but in the end was full of some quirks and patterns that mostly worked for my workflow. When other engineers joined I clashed with them a lot over those decisions and me imposing a hard structure onto others work/workflow.
When I became a manager and had the opportunity get familiar and re-implement another system, those types of choices and clashes, now from the opposite perspective (I didn't know the code and disagree with all of their implementation choices) really showned me I) the importance of the system design to guide improvements/features and II) how useless it is to dictate how someone should do their job.
I essentially learned that micromanaging sucks, but you get the point :D
The reason why I say that is that at some point I worked on a system (first to design and implement it) that for me was very nice and ergonomic, but in the end was full of some quirks and patterns that mostly worked for my workflow. When other engineers joined I clashed with them a lot over those decisions and me imposing a hard structure onto others work/workflow.
When I became a manager and had the opportunity get familiar and re-implement another system, those types of choices and clashes, now from the opposite perspective (I didn't know the code and disagree with all of their implementation choices) really showned me I) the importance of the system design to guide improvements/features and II) how useless it is to dictate how someone should do their job.
I essentially learned that micromanaging sucks, but you get the point :D