13

ughh, studying about various software project management methodologies and lifecycles is so boring.

every different model looks similar, saying :
you got an idea?
- check weather its needed and if its practically / financially possible
- get investment and resources,
- design,develop, test, release
- repeat .
why name them waterfall or spiral or rad or agile or shit?

and we know how project go in reality: "fuck its 2 days to release and 5 features left? push to prod, make breaking features, leave the tests and release"

Comments
  • 2
    Just a bunch of boomers pretending to understand all this slang and "applying" it because these are such stylish words. You've probably heard it from someone, but here I am.
  • 3
    I have an entire class about information assurance.

    I literally struggle to focus more than 5 minutes in that class. I feel sorry for the professor. He's such a sweet guy but the material is dry asf.
  • 5
    Well, agile isn't a project management strategy. Anyone who asserts it is either process or procedure should be ignored.
  • 10
    Because there are differences in how you approach the problem.

    Waterfall for example requires big front-up planning, and you have to go back to previous phases to fix that. Which sucks if you discover design problems late in the project and have to go back all the way to the planning phase.

    Another strategy is to drop front-up planning and improvise as you go, that's agile. You can react quickly, but you have no long-term planning and will run into architecture rot and tech debt.

    Since every strategy sucks, fashion oscillates between mostly these two extremes because by the time people find out the current way sucks, the suck of the previous way has already been forgotten.
  • 5
    There are two kinds of people:

    Those whi learn by heart and those who adapt.

    Sadly the latter isn't taught by education.

    You can learn a lot from these techniques, but in the end applying them in a methodic way and fitting them to your needs is the real burden.

    It's the same for architecture / database design and everything else...
  • 0
    They can do that because we are just high paid slaves that can be easily replaced if we say no and then they fire us. Life and work is not fair.
  • 1
    @Fast-Nop I love it when you said the words: agile, architecture rot, tech debt.

    Happening to me now
Add Comment