I am not too comfortable in mixing ‘software engineering methodology’  and the resultant debates about waterfall vs Agile and Scrum and the like as this mixes up structural dimensions. To me, the critical decision in software engineering/development is the language chosen, and this is dependent on what sort of software is being developed. IMHO,  software is grown, over time, from its initial capabilities onward. In aeronautics, though of course, the product, an airplane, does not fly a little bit. Software can be improved, expanded/extended over time. Also there is a great difference from web based, HTML ‘software’ and industrial strength compiled software that are more fundamental than project management methodologies, Agile,Waterfall and the like.

The choice of programming language and platform plays a critical role in how software evolves and scales, often more so than the development methodology itself. While Agile or Waterfall provide frameworks for managing the project, it's the underlying technology stack that dictates how flexible and maintainable the software will be in the long run. For instance, the needs of web-based applications, often built with dynamic languages like JavaScript, differ greatly from those of complex, industrial-strength systems, which may rely on compiled languages for efficiency and stability. Therefore, making the right technical decisions early on is crucial, as it sets the foundation for how the software will grow and adapt over time, regardless of the methodology used.

The choice of programming language and platform plays a critical role in how software evolves and scales, often more so than the development methodology itself. While Agile or Waterfall provide frameworks for managing the project, it's the underlying technology stack that dictates how flexible and maintainable the software will be in the long run. For instance, the needs of web-based applications, often built with dynamic languages like JavaScript, differ greatly from those of complex, industrial-strength systems, which may rely on compiled languages for efficiency and stability. Therefore, making the right technical decisions early on is crucial, as it sets the foundation for how the software will grow and adapt over time, regardless of the methodology used.