And for anyone interested in a template:

  • ChickenLadyLovesLife@lemmy.worldEnglish
    8·
    10 months ago

    I briefly wrote Blackberry apps circa 2010 (yes, I knew RIM was dying a quick death). The development process was insane: any module from the framework that you incorporated into your app had to be digitally signed by RIM servers every time you tried to compile your app and deploy it to a device, even if you had only made a one-line change to the code. On good days, this would make the compilation take 5-10 minutes; on bad days it would be upwards of an hour or never happen at all. Some wags had even set up a special website that would tell you whether the RIM servers were down or not (long gone now, of course). I got in the habit of making a large number of code changes before attempting to run and test stuff, which is obviously not the ideal way to do things but it certainly teaches you to be careful. It also make me think long and hard before including a new module into my code. As one example, for my GUI I needed to use trigonometry functions which were naturally (lol) part of one of the cryptography modules which took an especially long time to get signed. I ended up writing my own sin() function in Java just to avoid the hit of including that module.

    The great part of this was that I always had a ready-made excuse whenever I felt like taking a long lunch or going shopping or going home early. “Sorry boss, the signing server is down” and I made damn sure they never knew about isthesigningserverdown.com. It also helped that it was Blackberry circa 2010 and it didn’t make a shit bit of difference whether I got the app done or not.

  • JargonWagon@lemmy.world
    6·
    10 months ago

    Cleaned up the template a little and also removed the job role specifying “programmer” to make it even more of a flexible template:

  • sik0fewl@piefed.caEnglish
    1·
    10 months ago

    What we need is some sort of distributed version control system.

    I’m not quite sure how it will work yet, but it would have the entire codebase and its history mirrored onto every developer’s computer. Instead of requiring a central repository, developers could share their changes directly with each other.

      • Eager Eagle@lemmy.worldEnglish
        1·
        10 months ago

        git itself is really not far from a blockhain. Blockchain is fine, it only has a bad rep because of ponzi schemes that use it to create crypto, but the technology and trustless consensus mechanisms are interesting.

        • mogranja@lemmy.eco.br
          0·
          10 months ago

          I think blockchain also has a bad rep because every chance is mirrored to every copy of the blockchain? Thus wasting a lot of power and bandwidth for most use cases. Unlike git, where you only push what you want, and everyone only pulls what they want.

          • Eager Eagle@lemmy.worldEnglish
            1·
            10 months ago

            The waste of power is often associated to the proof of work consensus, but that’s not a requirement of blockchain. There are other ways to create consensus.

            The bandwidth requirements really depend on what’s being stored, but it’s usually very manageable for a server. And clients not running validation don’t need to store or transfer that much data.

    • Eager Eagle@lemmy.worldEnglish
      1·
      10 months ago

      but seriously, we need project management features that are decentralized: issue tracking, kanban, code reviews w/ comments, and ways to extend functionality without relying on a git forge.