Discussion about this post

User's avatar
Raviraj Achar's avatar

I loved the article! I love listening & telling "how I messed up" stories. They always have the fun & learning part.

"I felt physically ill, and helpless." I know the feeling :) The feeling of receding blood flow from your limbs and it gushing to your head. That scary moment after you mess up something big and before you know you have to fix it.

"For those of you not working in startups - please don’t judge 😅"

I won't! Meta had something similar back in the day. I remember a new hire from MSFT being in awe when I hot-fixed an issue and ran it from my dev server.

Expand full comment
Marijn's avatar

Extra point: Configure DBeaver correctly for your use case and share these settings within your company. For me it is very useful to have whitespaces as delimiters for queries, to manually run parts of bigger queries without running the above 'CREATE TABLE' line as well (seperated by whitespace). You can even create profiles for different connections like a more restricted production profile.

For your usecase of production use, DBeaver can be set to always to the next semicolon, and it can run in 'manual commit' mode handling the BEGIN and COMMIT for you.

Expand full comment
15 more comments...

No posts