Focused on creating wonderful user experiences by attending to folks needs with empathy and creating spaces of safety. Senior Frontend Developer/Tech Lead at Dolittle.
I really like how you've broken your definition of "blaming others" into steps / levels. I especially like that you frame these as levels to progress along, and that no matter where you are you can improve or help others improve 👏. Really speaks towards having a growth / open mindset.
I do however think there is more to it than just acceptance and avoidance of external factors. Sometimes doing the work itself is part of the problem and the only way to actually fix it is to raise the issue and reassess. An example could be "building the right thing vs building the thing right" ie: does it even make sense to build this feature / product?
Thank you @pavsaund
for such a positive feedback :)
I very much agree on your last paragraph, but in this particular post I was concentrating on avoiding constant blame on external factors, and focus on what you can do as an individual or as a team to make your environment independent.
I believe what you imply here, is that necessary dose of criticism must be presented inside team all the time, not just take tasks for granted. Am I right?
Thank you once again for your awesome comment, it really means to me :)
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.
thanks for this post @damnjan !
I really like how you've broken your definition of "blaming others" into steps / levels. I especially like that you frame these as levels to progress along, and that no matter where you are you can improve or help others improve 👏. Really speaks towards having a growth / open mindset.
I'm reminded of this quote from Viktor Frankl:
I do however think there is more to it than just acceptance and avoidance of external factors. Sometimes doing the work itself is part of the problem and the only way to actually fix it is to raise the issue and reassess. An example could be "building the right thing vs building the thing right" ie: does it even make sense to build this feature / product?
Thank you @pavsaund for such a positive feedback :)
I very much agree on your last paragraph, but in this particular post I was concentrating on avoiding constant blame on external factors, and focus on what you can do as an individual or as a team to make your environment independent.
I believe what you imply here, is that necessary dose of criticism must be presented inside team all the time, not just take tasks for granted. Am I right?
Thank you once again for your awesome comment, it really means to me :)