this post was submitted on 06 Apr 2025
14 points (88.9% liked)
Programming
19366 readers
156 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The paradigm in my work life I followed most of the time on most projects is "do whatever the project manager decides is important at the moment". I'm not aware of it having a particular name. Technically, they might call it scrum or something else, but really it's not even close to any of these labels. It really was always just "whatever sounds good to them at the time". I guess you could call it "agile", but not by choice necessarily. Please ask more questions on this or provide more options for me to choose if you want a better answer.
On my personal projects, I follow the "start programming and see what comes out at the end of it" paradigm, I'm also not aware of it having a particular label.
Edit: sorry other questions. Type of software is desktop application, web applications, browser extensions, game modifications. And for why these particular paradigms were chosen, they were chosen because a customer/user wants to be happy and doesn't care about what paradigm is used, only the result. As such, the paradigm essentially follows some humans' whims, which mostly doesn't make sense and definitely is nothing "formal" at all.
Thanks for sharing your experience! It sounds like the approach you’ve followed is quite flexible and adapted to each project’s needs. It definitely seems more like a mix of Agile and a bit of improvisation based on what the project manager or client prioritizes. I appreciate your insight!
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.