• 0 Posts
  • 43 Comments
Joined 2 months ago
cake
Cake day: June 12th, 2024

help-circle

  • Are the petabytes of training data included in the repo? No? Then how could it ever be called open source?

    At best, some of the current AI can be called freeware.

    If you’re just including the trained AI itself, it’s more like including a binary, rather than source.

    You can’t really modify Llama in a significant way, can you? You can’t fork it and continue improving that fork.





  • I just beat this level yesterday!

    It becomes easy… Once you know what the tricks are supposed to be, which the game doesn’t tell you at all.

    For me, these were the tips I needed:

    1. There’s a dedicated button for burnout, which makes it super easy to do the 360
    2. the slalom only counts if you do the pillars on one side of the garage BOTH WAYS
    3. To do a backwards 180, drive backwards, then push one direction, then halfway through push the other direction.

    Supposedly the PSX version also has a video in the options menu which shows you a dev completing the course, with button prompts on screen.

    Oh, and there’s a cheat code in-game to skip this level entirely.


  • I think that would depend on the skill of the developers and the resources they are given.

    A lot of us are only ever taught to be code monkeys and those would probably not naturally gravitate towards true agile practices (which most, I would argue, have never actually seen in a real project).

    Another problem is a lack of access to domain experts, which is also crucial.

    However, my current project doesn’t have any managers, or even business analysts, there’s only the developers and the Product Owner. We have access to some domain experts and we work with them to build the right thing.

    It’s going great and the only problems we are facing are a lack of access to the right domain experts sometimes, as well as some mismanagement in the company around things we can’t do ourselves (like the company Sonarqube not working and us not being allowed to host our own due to budget constraints).

    In conclusion, I think part of the problem is educating software developers - what true agile is and what the industry best practices are (some mentioned in my previous comment). Then you give them full access to domain experts. Then you let them self-organize. Basically, make sure you have great devs, then follow the 12 Principles of the Agile Manifesto to the letter and you’ve got a recipe for success.

    Otherwise, results may vary a bit, as I think many would tend to continue doing the Fake Agile they were taught and continue producing the poor quality, untested code they were taught to produce.




  • A part of it is horrible practices and a work culture which incentivizes them.

    Who can be happy when the code doesn’t work half the time, deployments are manual and happen after work hours, and devs are forced to be “on-call”?

    Introduce Test-Driven Development, Domain-Driven Design, Continuous Deployment with Feature Flags, Mutation Testing and actual agile practices (as described in the Agile Manifesto, not the pathetic attempt to rebrand waterfall we have in most companies) to the project and see how happiness rises, along with the project’s reliability and maintainability.

    Oh, and throw in a 4 day work week, because no one can be mentally productive for that long.

    IMO the biggest problem in the industry is that most developers have never seen a project actually following best practices and middle management is invested in making sure it never happens.






  • I don’t think source-available licenses have any chance of outcompeting open source, or at least I hope developers won’t let them.

    Open source thrives on contributions. The moment you restrict what I can do with the software I’m supposed to contribute to is the moment I ask myself: “am I being asked to work for free, solely for the benefit of someone else?”.

    The incentive to contribute completely disappears (at least to me) when I’m asked to do it for a project which “belongs to someone in particular”.