• Admin @ lemm.ee, a general-purpose Lemmy instance
  • Professional software engineer
  • Lemmy contributor

ko-fi

  • 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle
  • I think there are two separate things I want to address here:

    First, agile isn’t a project management methodology, it’s just a set of 4 abstract priorities and 12 abstract principles. It’s very short, you can check it out here:

    https://agilemanifesto.org/

    Nothing here says that you’re not allowed to write documentation, write down requirements, etc. In fact, the principles encourage you yourself as a software team to create the exact processes and documentation that you need in order to meet your goals.

    “Working software over comprehensive documentation” does not mean you aren’t allowed to have documentation, it just means that you should only write documentation if it helps you build working software, rather than writing documentation for the sake of bureaucracy.

    “Individuals and interactions over processes and tools” does not mean that you should have no processes, it just means that the individuals in your team should be empowered to collaboratively create whatever processes you need to deliver good software.

    Secondly, in terms of practical advice:

    1. Talk about this problem with your team. Is it hard for others to figure out where requirements came from? Maybe they already have a good method and can share it with you. If it’s hard for everybody, then propose improvements to your process, for example, propose some type of design document process as part of building any new features
    2. There are no perfect answers to the question of “how do I safely make non-trivial changes to systems”, but the general approach is to ensure that:

    a. You have metrics about how your system is used.

    b. You have automated tests covering any requirements, so that you can feel confident when making changes to one part of the system that it isn’t violating any unrelated requirements.

    c. You actually document any confusing parts in the code itself using comments. The most important thing to cover in comments is “why is this logic necessary?” - whenever something is confusing, you need to answer this question with a comment. Otherwise, the system becomes very annoying to change later on.

    If you are missing any of the above, then propose to your team that you start doing it ASAP

    1. At the end of the day, somebody is responsible for making product decisions. Is it your team? Or maybe some separate product owner? Sometimes, you just need to communicate with whoever is responsible to figure out if any requirements are still relevant, or if they are now safe to change.






  • This approach makes so much sense from a business perspective.

    How many here have this experience: out of my entire friend group that I grew up playing video games with, I can’t think of a single person who kept pirating games after acquiring disposable income, even though we all exclusively played pirated games as teenagers. Without piracy, none of us would have had access to any games, and very likely none of us would still be into gaming today, spending probably thousands of euros every year on games, consoles, PC components, etc.


  • That user has actually not been in contact with any of our admins, I’m not sure why they are claiming otherwise.

    In any case, I shared my position on piracy on lemm.ee a few months ago, and it has not changed. TL;DR discussions about piracy are fine, but explicitly facilitating piracy on lemm.ee is not allowed, and if any such content is reported on lemm.ee then I will most likely err on the side of removing it. Having said that, I am not planning to defederate lemmy.dbzer0.com at this point, as they have not been causing any issues for lemm.ee (but, of course, I do reserve the right to re-evaluate federation with any instance if at any point they start causing problems for lemm.ee).

    Quoting my original comment about piracy on lemm.ee, just for full context:

    There’s nothing inherently illegal about VPNs, P2P, seedboxes, torrents, software for torrents, etc - as a software engineer, I have no trouble understanding that these things all have legal purposes. There can be no realistic case made against someone just because they use (or discuss the use of) any of these things. You can post and comment about stuff like this all day long.

    Also: discussing piracy topics in general (like commenting on the legality of it, just saying you do it, whatever) without actually using lemm.ee servers to host anything sketchy is fine as well.

    On the other hand, telling people “go to coolpiracywebsite.com to download the latest avengers movie” is very sketchy - you’re not directly distributing anything, but I think a case can be made that this comment is directly facilitating piracy, and if someone sends me a legal letter to remove such a comment, then TBH I will most likely just comply rather than deal with the hassle of trying to figure out how legal it is. Just being frank here - I don’t want to create false expectations of lemm.ee servers being a safe haven for content with sketchy legal status.