Hi there, it’s me again.
Today, I want to share a great (and painful) experience I had while deploying a product to production.
My team and I were working on a very simple product. Its only responsibility was to register users — nothing complex, no heavy business logic. Simple, right?
Well… not exactly.
The DevOps team never explained how the infrastructure worked, so we built the product assuming things would “just work.”
Spoiler: they didn’t.
The first real deployment session lasted 6 hours.
Six fantastic hours staring at a simple “Hello World”, just to verify that the backend and frontend were running.
At that point, my patience and aura were gone.
I have 4+ years of experience in this industry, and honestly, it was the first time I had seen something like this.
The Production Conversation
There’s a moment I’ll never forget — right in the middle of deploying the backend to production:
- DevOps team: The backend can’t start because it can’t read the database. Please create a script to create the database.
- Me: What do you mean? Are you saying we need to create a script to create the database if it doesn’t exist?
- DevOps team: Yes.
- Me: … OK.
Why did I say “OK”?
Because I remembered some advice I once received:
- “To fight, you need two people.”
- “We didn’t research enough how the infrastructure works.”
- “Senior, look at me. Don’t stress. I’m 30 years old, and I already look like I’m 50.”
Conclusion
This experience taught me something very important:
- Never assume — always ask how the infrastructure works.
- To fight, you need two — and sometimes it’s better not to fight at all.
- I’m only 26 years old, and I don’t want to become a meme of a stressed senior developer.
Sometimes, the best solution is patience, communication, and learning the hard way.
Thanks for reading my powerful story 😉
Top comments (0)