Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
vringar17214yMistakes happen. To everyone. Trust me I fucked up a lot of shit.
But that is why blindly trusting doesn't work. You always need someone else to look over it. Even the most seasoned veterans do.
Try to get yourself that someone so it isn't as bad next time.
Also keep your head up. You are still very young and learning.
Mislead12824yI once set a server on fire.
No no, litteraly.
I put my laptop on the server rack and the additional heat generated made blue smoke appear.
Fire alarm goes off.
The whole building had to be evacuated.
Customer eyeballed my quite a bit when talking to the firemarshal and he explained where the smoke came from.
No firetrucks had to come to correct your mistake huh?
Just another one of those hard learned lessons in life.
Like not putting a laptop on a server rack.
Cheer up! It's not as bad as you think!
itch9625004yWow, just 19, working VOLUNTEERILY, and you feel so bad..... You are kind hearted and young. Mistakes happen and it's fine to feel bad too. Just make sure that you don't repeat your mistakes. Time will heal you my friend. Go on and don't take too much stress and responsibility, its bad for your health. (Hell i cannot change a person). Just do your best. If you dont face failure, you will never be able to taste success.
Wack66514yI was 19 or 20 back then and I was tasked with coding a slideshow to work on mobile with swipe control (the old one only had clickable arrows)
Guess who forgot to put the google analytics (plus wemf that's what the advertisers relly on in Switzerland) code there. Yep me. We found out about half a year later.
Not all was lost as ads still got delivered and the adserver counted the traffic, but the traffic didn't show up in the normal traffic report.
Bottomline: every body makes mistakes. There is a solution, the company won't go out of busines and you (hopefully) learned something.
P.S. suggest your boss to get a "staging" system, one that behaves like the system at the clients, maybe even replicates their db as a slave or restor it from db dumps, to test the whole update proces.
dreik14634yDon't be that hard on yourself. From what you have said, your boss's reaction seems to be on the positive side. So, there's that.
And you know how life is, test comes first, and the lesson follows. And those who doesn't fail, doesn't learn to be better.
So, don't blame yourself, help in any way to make things right and help the company setup a good review process to stop things like this from happening.
GC979774y@pascalwacker We have such a staging system and we also tested it this way - but we used our version which is newer than the client ones. This is the reason why WE didnt get any errors :/
mhudson13384yPain is the most effective teacher.
It is small comfort right now, but I suspect that this incident will sharpen your attention to detail by orders of magnitude.
I don't know your boss, so I do not know how this will effect your job, but it will not end your career.
Keep your chin up. 👍
gberginc4724yDon't be so hard on yourself. You are young, use this to your advantage and try to improve internal processes, at least code review, proper staging and deployment.
For code reviews, do not skip them, never! Especially when this goes to your production. Mistakes can be made, always, regardless of the person doing the changes. As you've learned even a single line can cause problems.
Then, improve your staging, make sure that you are testing for all versions your clinets have installed (and are still officially supported).
As far as the deployment goes: do not rush it and be prepared for severity one reports. If possible, rollout in batches, with your most keen clients to ensure smooth transition.
gberginc4724yAlso, for the Monday meeting, I suggest not to go too deep. You ackowledge your mistake. Based on your rant, you really won't have to say much - your colleagues, and your boss above all, will see it in your eyes! Try to focus on making improvements, preventing such things could happen in the future.
Finally, again, based on your rant, you are the kind of person I would love to have on my team! So don't worry about it too much!
elfico20114yAWS went down because of a typo.
Gitlab was down because of backup failures.
If all softwares were perfect, there would be no need for patches which are released from time to time.
Just keep that on mind. Learn from it and move on. From what you said about your boss, I think he would understand.
Dude relax man! You're still in growing age all this stress is going to be very negative for you. Take a deep breath accept the mistake learn from it and move on. No one in this whole community is free from mistakes. We all make them. Hell I actually once lost all my code from seven days of coding
Everyone makes mistakes bro. Don't worry and Keep on grinding. Maybe a little break could help you to get refreshed.
I know that most people don't care about the 99 good things you do but focus on a single mistake. but as you explained your boss sounds like a really good person so I think he still trusts you. I hope everything will be fine soon. ♥
jshrt1444yDude, cut out the 19 years old bullshit, I was working around that age too, being young is a very advantegious situation.
For the mistakes, that is all alright.
This frustruation is going to make you write better tests.
What's gonna happen anyway? Lose the job? You will get another one. Ruin your reputation? Fuck that, you will fix it by starting your own shit and excelling at it.
I am just saying you know? Take every fuck up as a challenge between you and yourself that you will get better and actually do the sacrifices necessary.
Good luck bro.
PS: Explain your mistakes to your boss as you were explaining them to a colleague developer as far as importance is concerned, if it is something that was out of your reach, let them know so, so that they understand that there is certain hiccups to using technology including installing dependencies etc...
One of my colleagues accidently deleted the one of our customers databases. With like 100000 documents in it.
It took him one day to recover the data with the backups.