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 wormhole through a path of communities !webdev@programming.dev
Since I've never talked an idiot out of doing something stupid, I focus on selling them my help "deploying" it.
My amazing skills can help their stupid shit make it past security and legal, at the low low cost of sometimes a quiet complete re-write.
It usually works because idiots are also bad at mathb (or just magic thinking, carefully ignoring that their stupid added more cost than it saved.)
managed to blow up and nuke production
test in AI production
Pros: leadership wants to do your job. Chill out, let them do it, then laugh at them when it fails. You'll at least have a relaxing job up until they either fire you in their idiotic confidence or beg you for help.
Cons:
it's managed to blow up and nuke production
You know, I remember reading a similar story about AWS recently...
There are no pros since they wrecked a database. You should instantly find anything else.
Give them enough rope to hang themselves. They'll learn the hard way.
Forget replit specifically, what problem are they trying to solve? Leadership shouldn't dictate the solution but define a problem that needs solving.
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.
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.
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.
a little bit of knowledge is a dangerous thing