The real deal y0

  • 1 Post
  • 64 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle








  • Im currently trying to steer a product team to have this kind of process. They are working with an ancient piece of software that is slowly being replaced. However, we need to replace piece by piece while the main app is still being maintained because of law and workflow changes. This is why i want them to set the requirements and designs up front a bit so we can make a good analysis of it before development starts so no technical difficulties or questions arise mid development! However, nothing is set in stone and after each small piece ( aka after each sprint ) we have our review and product owners and stakeholders see what we have made and can chime in, causing us sometimes to pivot what we were making.
    Best of both worlds!


  • Agile has its uses, but like everything you need a bit of both. You need a bit of both waterfall and agile.
    Example : you need to have your requirements before development, yes. But how far do you go in your requirements? If i were to make all the requirements for my current project ill still be busy in 3 years and will have to redo bits due to law and workflows changing. however , we need requirements to start development. We need to know what we need to make and what general direction it will be heading to a make correct software/code design.

    Agile also teaches you about feedback loops, which even with waterfall, you need to have to know that what youre developing is still up to spec with what the product owner is expecting. So even with waterfall, deliver features in parts or sit together at least once every x weeks to see if youre still good with the code/look/design.

    Pure agile is bullshit, but so is pure waterfall. Anything that isnt a mix is bullshit and in the end, it all depends on the project, the team and the time/money constraints.






  • Thanks for the response. Ive heard of rust’s compiler being very smart and checking a ton of stuff. Its good thing it does, but i feel like there are things that can cause this issues rust cant catch. Cant put my finger on it.
    What would rust do if you have a class A create something on the heap, and it passes this variable ( by ref ? ) to class B, which saves the value into a private variable in class B. Class A gets out of scope, and would be cleaned up. What it put on the heap would be cleaned up, but class B still has a reference(?) to the value on the heap, no? How would rust handle such a case?





  • Ye, the sm64 was just a jit emulation, you are correct there. Not gonna deny that either. The sms and smg emulations are interesting and impressive though. They basically use a combination of jit compilation and aot compilation to basically take in the rom and adjust code as they go, but its technically running +/- natively, if i read the switchbrew wiki page correctly, thanks to the aot compilation. I find that impressive, from a technical standpoint.
    Could they have added more and do more changes? Yes, ofcourse. Im not saying the fan made stuff isnt impressive, it is and i love it!
    But for nintendo, who strives to create new experiences and things, not rehashing older stuff, is why they kept it basic. For them adding that stuff doesnt make sense as the game doesnt add new enough experiences. They dont care if a bug is fixed or graphics are improved. Those dont get you new experiences or gameplay mechanics. Thats what nintendo strives for.

    Again, if that is a good stance to have as a company i leave up to others to make opinions on, thats not up to me to decide or voice my opinion on ^^

    Fyi, since you seem to know what youre talking about, nintendo’s r&d have used open source projects before internally and we assume it is done to look at older games and see how they worked or if they could be used to make projects like sm3d ( without doing what the license doesnt permit )


  • Has nothing to do with their closed eco system. They basically did similar stuff with some of the stuff in the sm3d collection thingy.
    Nintendo is a company that only wants make new stuff, innovations.
    For example, they ( mostly miyomoto ) has been quoted to not understand that people want another f-zero, as the game’s principals and ideas have been fully flushed out and no new ideas could make it feel like something new.
    They also usually dont do remakes/remasters unless its so new/different it can be considered a new game ( see metroid 2 on 3ds ).

    If that is a smart business position to have, i will leave for you to decide, but do get your facts a bit straight :)

    EDIT: also, nintendo has used open source projects for internal projects before, so idk how “closed ecosystem” is part of their stuff :)