So some backstory here: I’m pretty much anti-AI, but I try to stay on top of things so I can make informed recommendations to leadership. Recently , they’ve come to me interested in using Replit “because it’s so easy” and they almost have a site built out how they want.

Besides the fact that it’s managed to blow up and nuke production, what are some pros/cons about it? I’m worried about things like BCDR, vulnerability scanning, separation of duties, etc. You know all the base things you should have in place too.

  • kambusha@sh.itjust.works
    link
    fedilink
    arrow-up
    10
    ·
    1 day ago

    Forget replit specifically, what problem are they trying to solve? Leadership shouldn’t dictate the solution but define a problem that needs solving.

    • ramble81@lemmy.zipOP
      link
      fedilink
      arrow-up
      5
      ·
      1 day ago

      Valid question, but leadership is technical enough to cause trouble and this is a smaller company that values fast right now.

      I’m working within constraints for now before pushing cultural fixes.

      • kambusha@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        1 day ago

        I would still say that the solution depends on what they’re trying to achieve, and what their priorities are. Maybe Replit is a good solution if they want something to create a quick proof of concept. Rather than commit to just one platform/solution, maybe it’s worth doing a 1-3month trial on Replit to help uncover what some of the pros/cons are.

    • lime!@feddit.nu
      link
      fedilink
      arrow-up
      2
      ·
      1 day ago

      we once lost a contract to build a service from scratch because the team didn’t have enough experience with aws lambda.

      there was no stack, no legacy code. the pitch was basically “onlyfans but sfw”, with no further details. as a team we had about 80 years of experience. all seniors. but no, they wanted experience with lambdas.