No, not at this point and age in my career, I will let anyone force me to work long hours.
I know from experience that working long hours solves problems in short term only and it only creates more problems at all levels in the long term.
If I was a fresh graduate with a chance to work for him, then perhaps ’Yes’ but then again I will convince my younger self to work for myself instead; start a youtube channel or company just like he did.
In my experience and practice, “it” works very well when the team and management understand why and how they do, what they do.
Its about working in a way that makes the development process both receptive and responsive to change. Focus shifts from requirement specification to early prototyping and quick release cycle.
To be agile is to be adaptive, not fast. You do that by working closely with customers / End users. You deliver small changes more frequently (sprints). To enable that you setup CI and CD infrastructure.
If most or all of these things sound unfamiliar, you need to question your own understanding of your process and focus on the “why” of it.
There is no set-in-stone way to “do agile”, therefore your criticism sound like someone pissing in the wind and shouting to everyone else about why its hitting you in the face.
I know from experience that working long hours solves problems in short term only and it only creates more problems at all levels in the long term.
If I was a fresh graduate with a chance to work for him, then perhaps ’Yes’ but then again I will convince my younger self to work for myself instead; start a youtube channel or company just like he did.