Used to do DevOps before they even called it that way: Linux. Python. Perl. Java. Docker. For fun and profit. CTO level generalist working for a mid-sized tech-centric company.
Dresden, Germany
Maybe this sounds thoroughly vague or stupid, but as far as I see things by now, managing unknowns in software is the very thing you need agility for. Not "agility" as in "Agile" (capital A) which often seems to be misunderstood as yet another formally described project management process these days, but rather "agility" in terms of following the four principles of the agile manifesto, encouraging a load of communication between relevant people and, in each and every situation, try to find ways to minimize the unknowns as good as possible - and find good solutions that suit your organization and working culture to address the remaining unknowns. This might differ between different unknowns, and of course I am convinced it will differ between organizational units depending upon how they work: If you have a very small (startup'ish) dev team with a product owner closely tied to both development and market requirements, this will be different than in a larger environment where there's a bigger distance between development teams and sales / marketing, for example. Just as an idea. :)
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.
Maybe this sounds thoroughly vague or stupid, but as far as I see things by now, managing unknowns in software is the very thing you need agility for. Not "agility" as in "Agile" (capital A) which often seems to be misunderstood as yet another formally described project management process these days, but rather "agility" in terms of following the four principles of the agile manifesto, encouraging a load of communication between relevant people and, in each and every situation, try to find ways to minimize the unknowns as good as possible - and find good solutions that suit your organization and working culture to address the remaining unknowns. This might differ between different unknowns, and of course I am convinced it will differ between organizational units depending upon how they work: If you have a very small (startup'ish) dev team with a product owner closely tied to both development and market requirements, this will be different than in a larger environment where there's a bigger distance between development teams and sales / marketing, for example. Just as an idea. :)