Programming

26102 readers

930 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Thoughts on Replit? (lemmy.zip)

submitted 1 day ago by ramble81@lemmy.zip to c/programming@programming.dev

10 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] kambusha@sh.itjust.works 10 points 1 day ago (2 children)

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.zip 5 points 1 day ago (1 children)

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 2 points 21 hours 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 2 points 1 day ago (1 children)

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.

[–] Bibip@programming.dev 4 points 1 day ago

a little bit of knowledge is a dangerous thing