Three months of broken builds before I got the hint

I kept wondering why my code worked on my machine but broke on the server every single time. Finally a guy on Stack Overflow asked if I was committing my node_modules folder. I was... for three straight months. I felt like a complete idiot when I realized git was pushing all that junk. Has anyone else had a deployment facepalm moment like that?

2 comments

2 Comments

johnson.ryan13d ago

That line "the kind of mistake you only make once" really hits home. I think that's the thing about these deployment facepalms - they stick with you because the lesson is so specific and painful. Like once you understand that gitignore file actually matters, you start checking it on every single project before the first commit. It changes how you approach your whole workflow because now you're paranoid about what else might be hiding in your repo.

ryan_carr5914d ago

Man that is brutal, I can totally feel the pain of those three months. So many of us have done something similar with config files or build tools where you just assume you know what you're doing until something smacks you in the face. Props for sticking with it and figuring it out though, that's the kind of mistake you only make once.