I stumbled across this anecdote from former Netscape CEO James Barksdale. I'm sure this concept is not without its defects, but it is an interestin...
For further actions, you may consider blocking this person and/or reporting abuse
Working at enterprises TOU kind of see two opposite viewpoints. I think a lot of it is tied to experience and where the person is in their career.
The first is, you have people and teams that focus on making sure no animals make it in, snakes includes. The spend a lot of time planning solutions to simple problems. Multiple meetings are set up. Multiple departments are called in. You small simple issue or problem is now a full blown war again the species of future snakes that may never come.
You then have people that are afraid of snakes and don’t tackle the actual problems. They do there Jira ticket when it’s put in front of them. They avoid the hard and complex things. They like to show progress and meet timelines, and don’t want to solve something that takes effort.
These are by far extreamly different examples. And I see them in different times in a developers career. The former is typically with some experience. Either someone who is new to a architecture role. The later is typically someone who is a year or two into the field and starting to “float on by”.
The more experience people may have conversations of the issues and the risks. And then make a decision, understanding the trade offs and how a zombie snake my bite them back in the future. These are best had with the team and transparently with business. Because it is a trade off. Progress now, or possible instability and interruptions later.
First I think the world is going wild with this hoolywood-like what you say and what you don't. A snake wouldn't mind killing you if it finds you're a threat though. And same I'm more empathetic towards animals.
Enough real snakes, this actually reminds me of some clients where we try to discuss the products they want to make. We tend to go explore a lot of problems and the discussion goes on and on (my mistake). What I learnt is to limit the problems, discuss solutions then COMMIT for one solution, don't come back! It's like that snake will reproduce and it's so time and energy consuming.