I am a big advocate of flexible hours and I personally feel that development is not same as working in a manufacturing assembly line, where everyone has to do their job at the same time for a product to finish.
Even with flexible hours, teams have to define their own overlapping time where people are available for collaboration and working over something as a team when you have a issue or a person needs help.
And eventhough it's cliche to say 'failures are lessons', I see it as a fact every day. Feedback loop of defects and incidents are critical for your development process and team efficiency to improve. Every RCA of the issue tells us something important that needs to be understood and incorporated in your processes.
And eventhough it's cliche to say 'failures are lessons', I see it as a fact every day.
Absolutely! Post-mortems were compulsory after every incident in my previous job. And you had to make sure it was shared with the entire company so that people would not repeat your mistakes.
Another one as a Product Manager was to realize that your hypotheses are wrong 60% of the time. It's more important to learn quickly and correct the course rather than trying to hit a home-run of truth.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am a big advocate of flexible hours and I personally feel that development is not same as working in a manufacturing assembly line, where everyone has to do their job at the same time for a product to finish.
Even with flexible hours, teams have to define their own overlapping time where people are available for collaboration and working over something as a team when you have a issue or a person needs help.
And eventhough it's cliche to say 'failures are lessons', I see it as a fact every day. Feedback loop of defects and incidents are critical for your development process and team efficiency to improve. Every RCA of the issue tells us something important that needs to be understood and incorporated in your processes.
Absolutely! Post-mortems were compulsory after every incident in my previous job. And you had to make sure it was shared with the entire company so that people would not repeat your mistakes.
Another one as a Product Manager was to realize that your hypotheses are wrong 60% of the time. It's more important to learn quickly and correct the course rather than trying to hit a home-run of truth.