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
Search - "gutted"
-
I think I've shown in my past rants and comments that I'm pretty experienced. Looking back though, I was really fucking stupid. Since I haven't posted a rant yet on the weekly topics, I figure I would share this humbling little gem.
Way back in the ancient era known as 2009, I was working my first desk job as a "web designer". Apparently the owner of this company didn't know the difference between "designer", which I'm not, and "developer", which I am, nor the responsibilities of each role.
It was a shitty job paying $12/hour. It was such a nightmare to work at. I guess the silver lining is that this company now no longer exists as it was because of my mistake, but it was definitely a learning experience I hold in high regard even today. Okay, enough filler...
I was told to wipe the Dev server in order to start fresh and set up an entirely new distro of Linux. I was to swap out the drives with whatever was available from the non-production machines, set up the RAID 5 array and route it through the router and firewall, as we needed to bring this Dev server online to allow clients to monitor the work. I had no idea what any of this meant, but I was expected to learn it that day because the next day I would be commencing with the task.
Astonishingly, I managed to set up the server and everything worked great! I got a pat on the back and the boss offered me a 4 day weekend with pay to get some R&R. I decided to take the time to go camping. I let him know I would be out of town and possibly unreachable because of cell service, to which he said no problem.
Tuesday afternoon I walked into work and noticed two of the field techs messing with the Dev server I built. One was holding a drive while the other was holding a clipboard. I was immediately called into the boss's office.
He told me the drives on the production server failed during the weekend, resulting in the loss of the data. He then asked me where I got the drives from for the Dev server upgrade. I told him that they came from one of the inactive systems on the shelf. What he told me next through the deafening screams rendered me speechless.
I had gutted the drives from our backup server that was just set up the week prior. Every Friday at midnight, it would turn on through a remote power switch on a schedule, then the system would boot and proceed to copy over the production server's files into an archive for that night and shutdown when it completed. Well, that last Friday night/Saturday morning, the machine kicked on, but guess what didn't happen? The files weren't copied. Not only were they not copied, but the existing files that got backed up previously we're gone. Why? Because I wiped those drives when I put them into the Dev server.
I would up quitting because the conversation was very hostile and I couldn't deal with it. The next week, I was served with a suit for damages to this company. Long story short, the employer was found in the wrong from emails I saved of him giving me the task and not once stating that machine was excluded in the inactive machines I could salvage drives from. The company sued me because they were being sued by a client, whose entire company presence was hosted by us and we lost the data. In total just shy of 1TB of data was lost, all because of my mistake. The company filed for bankruptcy as a result of the lawsuit against them and someone bought the company name and location, putting my boss and its employees out of a job.
If there's one lesson I have learned that I take with the utmost respect to even this day, it's this: Know your infrastructure front to back before you change it, especially when it comes to data.8 -
So a few days ago I shared about the conflict with my colleague on learning React. Today I was let go. Obviously I asked why they would do that and they said they feel the problem isn't even my React knowledge but the fact I don't grasp the fundamentals of OO programming.
Thing is in these 3 months there has not been a single code review. They are either going of what my lying colleague told them (they claimed he was excluded from giving feedback), or the consultants who were hired to help us. And yes, I got feedback I should improve but at the same time the assurance so long as I show improvement it'd be fine. And I was told they could see improvement. So I'm not sure what changed but suddenly there is no budget to keep me on. In any case it feels like shitty corporate bullshit.
But I can't say they are wrong. I struggle to explain simple concepts I know in words. I've worked a series of bad jobs where nobody cared how you did stuff as long as it got done. I feel I'm so behind now and so affected by bad knowledge it's even harder to fix than to learn the first time. So I'm wondering how to fix this.
I'm really gutted too because I loved this company. I was finally getting a fair wage instead of being underpaid. The people were excellent. I felt I could finally relax and feel safe at work. And now I feel betrayed. Which for someone with self esteem issues is very hard. Can't trust in myself and can't trust in others.
I'm gonna try and pick myself up in the morning, but today I feel totally shit. This wasn't how I'd expected things to go. I thought my manager had intended to talk conflicts over but instead I get the boot. And the advice to stop overselling myself. Real useful that. Like it is on me that they hired me despite my subpar interview because my CV looked good. It's a shitty excuse. In any case they're now stuck with a dev that walks out of work, throws false accusations about colleagues, and another person warned me about to not engage because nothing good ever came from it. He's gonna keep over engineering everything and make up for all the time he wastes outside of work creating a dysfunctional environment for everyone. But yeah, easier to fire the new person who does her best despite the odds. And who cautioned against over engineering because we kept missing deadlines. And who believes in refactoring when it is needed because that's how agile works. Yeah better keep someone who has no sense of work life balance and makes others miserable then claiming he's being driven out by your ignorance. And of course the consultants who throw your own people under the bus. Can't get rid of those now.7 -
Another failed interview after I poured my heart and soul into an employers interview project. I Pulled all nighters. I worked so hard and really pushed myself this time. The interview went really well and I had a lot of positive feedback but I didn't get the job because they hired someone with more experience.Im am so passionate about becoming an Android Developer but it saddens me that I will never be able to get a job doing it because there are always people more experienced than me. I'm absolutely gutted. IV worked so hard to get this far. I'm about to give up. What's the fucking point.... Devistated.16
-
This gutted feeling when you got so overly excited over an idea that you poured blood, sweat, and tears into it only to figure out what the others were doing isn't actually bad. Their's doesn't have issues. There's nothing for me to do. My whole idea, scrapped
I feel tired 😔5 -
Have you ever gotten a task where you have to modify some existing code, and to get it to work the way it needs to you have to write some ugly ass code?
And I'm talking FUGLY ass code. The kind where every brain cell you have screams to refactor it all so that your code won't be so ugly and you can live with yourself. But you only wrote it that way because some numbnuts who was fired a year ago designed it that way, and left zero commentary or documentation on his reasoning ("sELf-dOcUmeNtiNg cOde, bRuH!").
It doesn't pose any sort of risk with regards to security or resource management or efficiency, or really even faulty logic. It just looks fucking awful, my brain can instantly see better ways to design it and I don't want history to tie my name to it.
But also the system is being gutted and retired within a matter of months, so maintenance won't even be a concern; and you know that you have a lot of other large tasks that need your attention too, and to refactor will ultimately prove to be a time sink.
I mean ultimately, I know what I need to do, but I guess it's a pride thing. Just makes me feel icky. -
Oh you want that ticket closed from a week ago? Okay how about every time i finish it, you quit reopening it and adding more tasks and features to shit ive already redesigned/gutted/debugged about 20 fucking times.1
-
My top lesson was realizing that I am a stubborn person, and that I was wrong to keep trying to implement unimplemented features past a deadline and that I need to understand when to give up. I also learned that I can't trust others to finish their part of something I start. There is nothing like seeing the entire backend you wrote be gutted by someone else because they "needed to learn how route handlers work by creating it themselves" and then seeing them not complete said route handlers.
-
So I got accepted into a Master’s programme for CS - which is kinda cool but hardly unexpected. Guess I should feel elated about it, but honestly, I don’t know how I feel about it. Really it only adds additional complexity into the next few years of my life: I feel a little gutted that I have to switch over to my plan B regarding the sporting side of my life (there’s no way I can work full-time, study AND train for IM simultaneously - there’s just not enough hours in a day…), but that’s okay. At least I had a plan B knowing I might get accepted to these studies now.
What it really complicates is decisionmaking regarding this: https://devrant.com/rants/5571843/...
At my current workplace, I have officially 2hrs each week + an additional full work day a month to use for studying during work hours (in reality I tend to use more than that because I can, whenever there are no pressing matters need doing), and my gut is saying that’s unlikely to be possible in a consultancy position in a startup. Maybe it is, I don’t know. Need to ask.
In life, very few things are ever straightforward, aren’t they? But hey, at least I get to do my Master’s and I get to do it in a quality university! -
Trying to understand why the last guy who worked on my current project gutted out the framework specific data layer and replaced it with component-level ajax calls4
-
So I joined this amazing team at a pretty good company. They're solving some interesting problems and improving the company's product. I'd been very motivated working with them from the start.
A few weeks ago the company announced they'd be allocating more resources for sales related teams and turns out my team is one that's gonna be gutted from 7 to 3 devs.
I've been extremely demotivated since I just left a fintech cause I found the space extremely boring. Haven't been able to work, finish tasks etc knowing I'm gonna go back to something I know I don't enjoy.
Not sure if I should leave, just slack off or what since the pay is really good and I've only been here half a year. There was also a small singing bonus I'd have to return.
Any tips?5