Programming

Oh and as for reasoning why, another few points, all projects I've been in just kept being worked on and had constantly changing requirements. There was no real need to plan very much except maybe some rough estimations, that were allowed to be wrong.

There were like some very rough aspects of scrum in professional development, but only in the sense that we'd talk about what we'd like to do in the next sprint, we didn't do multiple plannings or estimations or cared about our velocity or did retrospectives often, and even the sprints were adjusted to last longer or shorter based on what we're going to do, there were a couple of roles people should have missing, and idk what. In the end, the resulting system was just something in the direction of agile/kanban, work just came in, and was handled based on some prioritizing by someone.

My personal projects could be really close to waterfall as well, I thought about a problem, made a rough plan on how to solve it, then just kept solving until I was done. Open source projects, no one organized anything, everyone just works on whatever they like.

Basically, you're the expert in software development paradigms, I'm just a developer that works on problems with code until solved, either given to me by someone or myself. The only ones who care about the paradigm are the business guys who wanna plan some shit.