• 0 Posts
  • 226 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Yes, silly engineers that don’t like being held to unrealistic estimates and deadlines; typically the ones that arise at the start of a project where there are still who-knows-how-many unknowns to find.

    Waterfall is the most effective tool for software engineering in a world where the whole world stops once you’ve planned and only starts again once the project has finished—i.e. a fictional world that doesn’t exist. Literally every waterfall project I worked on back in the old days was derailed because something happened that wasn’t planned for—because planning for everything up front is impossible and planning for anything more than a handful of eventualities is impractical.

    Agile and subsequent methodology comes from realising that requirements will change and that you are better off accepting that fact at the time than having to face it once you’re at the end of the current road.

    Agile does not mean engineers talking continuously to the users, engineers are hired to do what they’re good at: engineering. Understanding user requirements and turning that into a plan has always been product’s job regardless of methodology, in agile and similar it’s just spread out over the duration of the project, not front loaded. Agile isn’t “make the engineers do every proficiency”.


  • A software engineer was not involved in this if waterfall is painted positively.

    I think the last time I heard an engineer unironically advocating for a waterfall IRL was about a decade ago and they were the one of the crab-in-a-bucket, I-refuse-to-learn-anything-new types—with that being the very obvious motivation for their push-back.



  • Firstly it’s a fraction of a percent of the pool of people working as entertainers that get paid anything close to a comfortable salary—many don’t even last a few years and make basically nothing before they change careers.

    The successful ones get paid a load basically because the people that invest in funding TV shows & films know that you can generally multiply your investment by attaching a household name to the project. Now this is for several reasons, firstly a household name will generally actually be a good actor. Secondly, people recognising a member of your cast means they’re generally more likely to watch it. Finally, there’s the effect on the rest of the casting—some studios might take the opportunity to push the compensation of the “no-name” actors down because they have an opportunity to work with a star, others might go the other way and use the first star in negotiations to get additional starts signed on to the project.

    So essentially, the big projects make a lot of money, and executives attribute a significant part of that generated value to having the big star involved, and so they portion the funding to ensure that happens.

    There’s also the negotiation factor on long running shows, main characters end up in good negotiation positions for more money if a show is successful and their character isn’t easy to kill off. This is also why Netflix tries to cancel stuff before the 3rd season—that’s about the point who holds the power in negotiations shifts away from the studio.

    An in-demand actor is a finite resource, they can only really work on one or two projects at any given time, so this also pushes their fees up as projects may end up in bidding wars. Conversely most entertainment costs very little to sell beyond the initial production costs, so after that’s broken even it’s free profit they can use for these fees.

    Tl;dr capitalism










  • The statement “this [guy] thinks the government uses SQL” demonstrates a complete and total lack of knowledge as to what SQL even is. Every government on the planet makes extensive and well documented use of it.

    The initial statement I believe is down to a combination of the above and also the lack of domain knowledge around social security. The primary key on the social security table would be a composite key of both the SSN and a date of birth—duplicates are expected of just parts of the key.

    If he knew the domain, he would know this isn’t an issue. If he knew the technology he would be able to see the constraint and following investigation, reach the conclusion that it’s not an issue.

    The man continues to be a malignant moron