this post was submitted on 06 Apr 2025
14 points (88.9% liked)

Programming

19366 readers
159 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
 

Hi everyone! I’m a student currently working on a research activity for our Software Engineering class, and I’d really appreciate your insights. 😊

I’m looking to gather input from software developers, project managers, or engineers about the Software Development Life Cycle (SDLC) paradigms you've used in your past or current projects.

If you have a few minutes to spare, I’d love to hear your answers to these quick questions:

  1. What type of software did you develop? (e.g., mobile app, enterprise system, game, etc.)

  2. Which software development paradigm did your team follow? (eg. Prototyping Model, Spiral Model, Fourth Generation Techniques (4GT), Waterfall Model Agile Model, V-Shaped Model, Incremental Model, RAD (Rapid Application Development), Feature Driven Development (FDD), Big Bang Model, Scrum, etc)

  3. Why did you choose that particular paradigm? (e.g., client requirement, team familiarity, project scale, etc.)

Your input will be used for academic purposes only, and it would really help me complete this task with real-world insights. Thank you so much in advance!

you are viewing a single comment's thread
view the rest of the comments
[–] gsv@programming.dev 3 points 2 days ago (1 children)

I’m involved scientific programming tasks (climate models) and we are largely using a mix of prototyping, feature-driven, and big bang models. It’s a result of the requirements for our work. Important is, that our “user base” is extremely small and in the beginning of a project mostly ourselves. The required features are given by the scientific questions and timelines dictated by project timelines from soft funding. Iterations are thus mostly more like “that didn’t quite work, I need another method” kind of arguments. Hence, the implementation of modular and fast evolving design is important and often we try to build our software such that fast development can be done on individual models.
Sometimes theres an idea on how to solve a problem more efficiently or with better performance. And then it’s all about coming up with any proof of concept.

Finally, there is not really anything like a management in our line of work. The professor is usually satisfied if the results work out and papers go out quickly. The rest ist largely up to the group of devs.

[–] BackgrndNoize@lemmy.world 2 points 2 days ago (1 children)

How do you find such roles, coming from corporate roles this feels like it would be better for my mental health and WLB, plus your work contributes to scientific progress which feels better than just making rich people richer.

[–] gsv@programming.dev 2 points 1 day ago

There’s many pathways to get there. In my case it’s a classic science career. Whether that is better for the WLB is likely open for debate. 🙈 There’s a growing understanding in science that there’s a need for tenured scientific programmers supporting the compute infrastructure and development. These roles are quite rare though and thus there is tons of competition. Long story short: It’s a challenge. The good thing is that there’s many jobs out there with the meaning we seek.