Watching someone/working in Production Databases. There's so many easy ways to accidentally bring the system down in a fiery mess. Especially when watching someone that doesn't give off a strong sense that they know what they're doing.
Senior Software Engineer started programming over 20 years ago.
C C++ python
flask QT django
AWS GCP Airflow
k8s terraform
JS CloudDB's
rust vue TS
API backend dev
#Intp #mathematics #nerd
30+ years of tech, retired from an identity intelligence company, now part-time with an insurance broker.
Dev community mod - mostly light gardening & weeding out spam :)
Just as anxious-inducing for me is copying a production database to your local development box. If there's private customer data, ugh. (One consulting gig insisted I copy the production database over for local development or connect to it directly and it was a small business so the owners and employees and contractors can lose their livelihoods with one messed up SQL query or ORM command).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Watching someone/working in Production Databases. There's so many easy ways to accidentally bring the system down in a fiery mess. Especially when watching someone that doesn't give off a strong sense that they know what they're doing.
Same with me. Well that is a scary situation playing with the production database.
Heh, that's referred to around my way as 'playing Operation in prod', aka live heart surgery...
Just as anxious-inducing for me is copying a production database to your local development box. If there's private customer data, ugh. (One consulting gig insisted I copy the production database over for local development or connect to it directly and it was a small business so the owners and employees and contractors can lose their livelihoods with one messed up SQL query or ORM command).