emma

It works in dev. Why doesn't it work in prod?

Last updated 22 Dec 2022, 21:50:53 GMT

I enjoy a solid code πŸ“„review, but I am not always working with other πŸ«‚people when I code. Either way, I 😣dislike the feeling of accidentally introducing πŸ›bugs with my code. I've done it before, and I am the type of person to wake up in a 🧊cold sweat in the middle of the πŸŒ”night wondering why that page just doesn't quite scroll to the top in the right way.

It is even more πŸ‘»soul crushing when that issue doesn't even happen until the code has gone through a πŸ”continuous integration workflow and ended up in some data center somewhere; oh, and also, all of the source maps are gone. This isn't even considering that you might be working on something highly πŸ‘visible that you wouldn't really want to be working on in production while there are people actively interacting with it.

Why doesn't it work?

Maybe, it is a bad βš™config, or maybe, the thing you designed is fundamentally incompatible with the thing you are hosting it on, or maybe, it is just a bad βš™config. It is really hard to tellπŸ€”. Is it even πŸš€deploying? Hold on, let me read the logs.

Oh, I think I fixed it!

Oh, wait, no. It was just cached from before it broke.

Is this just a part of being human?

Am I doomed to fail? Is acceptance of my humanity the only thing that will relieve me from my 😣suffering? I don't know. I can't say for sure, but I do know that, as a πŸ‘©human, I am bound to make ❌mistakes. I am getting better at not ruminating on the past, but my progress isn't a straight πŸ“ˆline. Growth is all about making mistakes. You can't learn how to do something unless you try. You can't know if something works in production unless you put it in production.

So, go ahead! Press that πŸš€deploy button!

Unless, that is a bad idea for you; idk your lifeπŸ€·β€β™€οΈ