• 2 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle
  • Ah, the usual propaganda from the fucking content mafia and the lobbyists they bought:

    “The takedown of Fmovies is a testament to the power of collaboration in protecting the intellectual property rights of creators around the world,” Knapp says.

    “Strengthening intellectual property rights is an important element of the U.S.-Vietnam Comprehensive Partnership,” Knapper said

    I’ll happily repeat again and again and again:

    • If pirate sites offer a better user experience than your paid offerings, you don’t deserve payments at all
    • The money goes mostly to some rich fucks, fucking shareholders, lawyers and bought politicians and and not to the artists/creators of the movies (with some exceptions for the really big names)
    • I will very happily pay a service which is not shitty, not region locked, doesn’t annoy me with advertisement and is reasonably priced. The illegal sites are demonstrating that it is possible to sustain such an offer on advertisement alone. Don’t give me fucking bullshit that it is not possible for companies like Netflix while most of the subscription fees are going to shareholders and higher management instead into creating new content

    Seriously, fuck all the politicians and governments which act against the benefit of most of their population to conspire with the content mafia.





  • Good points, and I mostly agree with you, especially with feedback loops!

    Still, I never argued for waterfall. This is a false dichotomy which - again - comes from the agile BS crowd. The waterfall UML diagram upfront, model driven and other attempts of the 90s/early 20s were and are BS, which was obvious for most of us developers, even back then.

    Very obviously requirements can change because of various reasons, things sometimes have to be tried out etc. I keep my point, that there has to exist requirements and a plan first, so one can actually find meaningful feedback loops, incorporate feedback meaningfully and understand what needs to be adapted/changed and what ripple effects some changes will have.

    Call it an iterative process with a focus on understanding/learning. I refuse to call this in any way agile. :-P


  • … I cannot count the number of times at my different workplaces where we had an agile process, dailies and everything else of the agile BS for projects which where either trivial or not solvable. No worries, the managers, product owners and agile coaches made money and felt good, we developers went for greener pastures…

    Agile is a scam, nothing they do is based on any facts and when you challenge agile coaches / other people which profit it is always ‘I believe’ or ‘proven by anecdote’.

    Combine this with the low quality of people in the average software projects and you have a receipt for failure.

    Writing the requirements first at least forces people to think trough a project (even if only superficial), so I am not surprised the success rates for this projects goes up.