I am just getting started after many failed attempts but the goal is to have a place where I can do deep writeups on things I am interested in like software and mastery.
The first post is somewhat meta and shows how to build the site in AWS using Terraform
Watch Band of Brothers - Dick Winters I think is the best example of a good leader.
Doesn't ask from the team things that he wouldn't or isn't capable of doing.
And as many of the other comments have said you are there for the team. They will produce the real value.
What can you do to get them all the things they need to succeed? What can you do to shield them from the nonsense? Poor requirements, unnecessary meetings.
I think you want to give chances to fail but also provide that safety net so they don't fail too hard.
I have been working on this idea for a little bit. Started putting together a list of intermediate projects for people that finished a bootcamp. It is still in its infancy. I ran a programming bootcamp for a year and a half and think there is a need for this, but still figuring out the right way.
- Learn a new skill/craft. If you are in tech, maybe something more physical, cooking, woodworking,etc. Six months is a good amount of time to build a base.
- Learn a foreign language, again 6 months is a perfect amount of time. Highly rewarding.
- Work on holes in knowledge, build a self-course around it. Algorithms, dbs, whatever.
- Pickup an new programming language.
- Build a side project, doesn't have to be commercially viable, could be open source or not. Build a redis replacement for no other reason than to understand it.
- Travel. I understand the constraint of wife/kids, but there are ways to fit it in. Don't have to live in Southeast Asia, but travel, I feel is a great brain boost. Awesome rush of new.