Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@alexbrooklyn I'm responsible for the project but I get help from another (older) dev.
-
@netikras haha lol.
-
Don't worry :) you've ported their whole infra to the cloud. A few missed spots - that's nothing. These things happen all the time! Lapsus here, lapsus there - oh well, fix them as they are found.
I say you have nothing to worry about :) it's completely normal. Hopefully the client understands that as well :) -
@lecethimon :P
-
@netikras Thanks haha. Yeah, the client didn't even notice a thing so lucky me I guess
-
@Jifuna they were probably too excited about working in the cloud to wonder where the emails were. Free day off for them?
-
@aspenscythe Hahaha, I think you're right. I don't really understand how they didn't notice it because it was like 10 days or something :P.
-
This shit right here is why I always tell people "write it somewhere, no one is even going to remember it 2 hours from now, and definitely not any of the new guys that might work on it"
Seriously, this happens so often, that something gets deployed, fixed, a plugin gets configured, a package gets inatalled... And theres **one** person who did it and no one else knows how, including him month later when its time to deploy to production!!
This shit needs some place to live or the company is destined to keep wasting time and resources on the same issues.
Related Rants
Welcome to the future guys.
Then they say
So today was the worst day of my whole (just started) career.
We have a huge client like 700k users. Two weeks ago we migrated all their services to our aws infrastructure. I basically did most of the work because I'm the most skilled in it (not sure anymore).
Today I discovered:
- Mail cron was configured the wrong way so 3000 emails where waiting to be sent.
- The elastic search service wasn't yet whitelisted so didn't work for two weeks.
- The cron which syncs data between production db en testing db only partly worked.
Just fucking end me. Makes me wonder what other things are broken. I still have a lot to learn... And I might have fucked their trust in me for a bit.
rant
aws
worst day ever