I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
Good leadership is the difference between failing teams and successful teams. Companies invest lots of money in strong leaders, and for good reasons. It is not easy, but without it, you end up in the place that you are describing. Chaos.
Coding methodologies are a framework to help flawed humans work with more discipline. Call it manufactured discipline, in a world where humans are far from being perfect.
There is always somebody that fights against coding methodologies, leadership, etc. I'd say 10% of developers think that way. For those kinds of engineers, I recommend to not attempt to work in teams. Working in teams is difficult for some folks. It does require structure, experience, and discipline. Those are not just words, they are realities, skills, things that you build over time. Look at it this way: Mastering coding is level 1, mastering coding in teams is level 2, mastering technical leadership is level 3, mastering people leadership is level 4, and a lifelong pursuit.
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.
No, it is not easy, at all.
Good leadership is the difference between failing teams and successful teams. Companies invest lots of money in strong leaders, and for good reasons. It is not easy, but without it, you end up in the place that you are describing. Chaos.
Coding methodologies are a framework to help flawed humans work with more discipline. Call it manufactured discipline, in a world where humans are far from being perfect.
There is always somebody that fights against coding methodologies, leadership, etc. I'd say 10% of developers think that way. For those kinds of engineers, I recommend to not attempt to work in teams. Working in teams is difficult for some folks. It does require structure, experience, and discipline. Those are not just words, they are realities, skills, things that you build over time. Look at it this way: Mastering coding is level 1, mastering coding in teams is level 2, mastering technical leadership is level 3, mastering people leadership is level 4, and a lifelong pursuit.