Well, you know, engineers are famous for "can't code their way out of a wet paper bag" even though they sounded great in an interview. That's what FizzBuzz is

Well, you know, engineers are famous for "can't code their way out of a wet paper bag" even though they sounded great in an interview. That's what FizzBuzz is for - to find out quickly if candidates can code at all. So it's not like imposters are only in non-technical roles. > > Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. > This basically normalizes product managers being incompetent. No, it normalizes product managers doing their jobs. If external circumstances change, do you want to keep building the wrong thing, or do you want to respond? Agile is all about responding when things change. But you need a product manager who is competent to do the right changes, and only those, rather than changing with every morning headline. But if you're not doing agile, you still have the same problem. If your product manager isn't competent to steer the delivery as circumstances change, how are they competent to get the requirements correct enough that they won't need to change for a year-long project? Answer: They aren't. (But agile may make their incompetence more frustrating day-to-day to the engineers, instead of letting them enjoy the sense of accomplishment of happily building something to completion, even though it's the wrong something.)