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
-
This was at my previous and last internship. At previous ones i never got serious tasks so i was pretty used to that but one day my guider (lead backend programmer) called me over to help him out with a server issue (in all seriousness he said that i was probably the best Linux guy at that company at that moment). So i fixed it quickly and just out of curiousity i asked what kinda server it was and how many visitors it got monthly!
"it's a prod server and about one million at least i think"
I was just standing there for a minute and then asked why the hell he let me, an intern, work on that to which he replied: because you know what the fuck you're doing. I think I succeeded in hiding the tears of happiness that came up at that moment :) i fucking miss that place.12 -
I was working in a small startup with very cool people as a GameDev. One day I turned towards my colleague to tell him about a joke I just read and I saw flames coming out of his CPU. He was so focused on his work that he didn't notice.
I yelled "OH, SHIT' and quickly reached to the main switch and turned it off. Everyone turned towards me to yell at me, but then they saw the flames and everyone ran outside.
After few minutes the flames died. My colleague was in shock to lose his work as the HDD was completely burned.11 -
One day a client sent me gifts and a sweet letter just because they loved their new website so much. I just about cried. I work in an industry where acknowledgment and thankfulness by clients are extremely rare. 😱😭8
-
Call comes down from the CEO and through his "Yes Man" that some investors are coming by to visit and he want to show off the data center and test servers. There are four full racks of storage servers filled with HDDs and each server has 4 to 16 HDDs a piece.
I got told to "make all of the lights blink", which can be epic seeing it in action but my test cycles rarely aligned that way.
All morning I was striping RAID arrays and building short mixed I/O tests to maximize "LED blinking" for the boss's henchman.
Investors apparently live/die by blinking light progress and it was all on me to get everything working.21 -
Said my code is self explanatory and doesn't need comments.
After few minutes "wtf is this shit?".5 -
Python. Changed a function to return a tuple instead of one value in some database code. Tests pass, gets deployed, everything works. End of the month comes. Suddenly, we get a report that we're draining people's bank accounts and credit cards.
It turns out there was an untested bit of code inside the billing process that used this function. It used the function that was changed. To make matters worse, when the exception was thrown, the billing had already completed successfully, and due to another unrelated bug it would retry despite this.
So, needless to say, type safety and good unit tests are things I prioritize nowadays.7 -
Today.
Last night someone detonated an improvised nail bomb at a concert venue in downtown Manchester. 22 dead and 59 injured (many life threatening).
I'm working from home as my home is listed as a safe haven.
I'm not sure how much, if any, work I'll get done.
If you're in Manchester and need anything let me know.
It's all very much process:
Check everyone I know is ok
List house as safe space
Buy food
Keep passing information around to those who need it
No real time to think about it, just stay in the "response" mode.12 -
In my previous company, I used to work for a client company which had a terrible website. It was about financial data and people would have to wait too long before the page loaded because there was a freaking 1.2 megs of minified, compressed JS file that needed to load before you could do anything.
Everyone knew that was a pain in the ass and nobody wanted to touch spaghetti code and mess up something they didn't know.
I wanted to however take a shot at it. So an architect from client side and I discussed how we were gonna go about it and how we were gonna find the stuff that needed to load on page load and stuff that could be loaded later.
So we plan for it. We broke everything down from a globals polluting JS, found out the variables and functions that needed to run during first load by literally putting a console statement for each function and finally came up with two bundles.
The primary bundle was 120kb and would during first load and then every module would call it's own secondary bundle when the user interacted with it.
In the process, we removed half a meg of JS and the site became blazing fast.
I did it with a team of two members who, my manager thought were useless, learned a ton of stuff, setup proper process for the transition.
When the client didn't appreciate the amount of brain and effort we had put into it, these two members came forward to tell the client to acknowledge my effort and attributed the success of it to me.
I was totally moved. There was so much respect that I didnt care what anybody else thought. I was just so happy to work with those two humans.
When i left the company, i gifted them stuff they always talked about or wanted. :) Feels good.2 -
The day i found out how GitHub and Git actually work and how easy it is to manage versions rather than having a zip archive in Dropbox. I grew up so fast...T_T1
-
Resigning tomorrow, and I can't sleep. Thrilled to finally end the slavery at a company that pays me half of the market price. Exciting day coming up..5
-
The most emotional moment was after seeing that "Hello, world!" printed out on the screen for the first time. That was the point where I felt like "yup, this is gonna be my life from now on"
-
Day before easter holidays, a few years ago. It was evening and almost everyone had gone home. I finished a task, and immediately set off to do the next one, stressed as fuck, as usual. One colleague was left at the office, who asked me to at least eat something before I continued. I said I didn't have time, but after some negotiations sat down at the table, and realized I couldn't physically move the fork to my mouth.
I was having a panic attack. My colleague helped me with breathing excercises, gave me some pills and when I started to calm down a little, I said I'd better go back to work.
"No", she responsed, "we're going to the emergency"
I refused, since I had work to do, but she told me that I needed a person in a white lab coat to tell me that I shouldn't work for a while.
We went. The doctor gave me 3 weeks of sick leave, where I learnt a new word: No.
I thank the universe for not letting me get burnt out. I'm thankful for that amazing colleague.
I now work without stress, doing one thing at a time and saying no when my body says no.11 -
Me yesterday. I dont have my laptop now...
When you are chewing mentos and because you are thirsty, you drink coke.
SPRINKLE ALL OVER MY DESK!4 -
Sometime in mid 2013 or 2014 as a junior dev I woke up to a call from my company's CEO. He informed me that the legacy system they use for order processing is down nationwide that nobody can add new orders until it's fixed and that I needed to fix it. I had been working there 6 months and was hired along with a senior dev to begin developing a web app to replace this legacy system. The senior dev had left the company two weeks earlier for a better offer so it was put on me to figure it out. I was very frank with the CEO and told him I didn't know if I could fix it and suggested he try to call the company they hired to create it. I didn't even know where the source code was let alone what the design paradigm was or whether or not there was any documentation. He said he would try figuring out who created it and give them a call and asked "As a developer you shouldn't you be able to fix this?" I just told him it wasn't that simple and left it at that.
I get to work and the CEO has discovered that the company who created the software no longer exists and I tell him he may need to find a company to consult on this if I can find the source code and if I can't find the code he might be screwed.
I found the source code in a random IT shared folder there is no source control, no documentation, no unit tests, no test environment, and it looks like nobody had touched it since 2005 or about 8 years.
Despite being completely unfamiliar with the code and the design paradigm I was able to figure out that they were validating customer addresses against an old Google geocoding API that was shutdown the day before and the lack of response was killing the application. I fixed the issue and warned the CEO before deployment that I wasn't able to test but he said to go ahead and thankfully all went well.9 -
When I didn't compile the code for 500+ lines and when i finally did, there was only one syntax err... it was a typo... and then it worked...11
-
When I managed to minimize the processing time of the project I'm currently handling. It went down from 30min-1hr to 7min-15mins. The project owner was so happy, said it made his life easier. I was told I did a good job by my manager.
I feel like a real dev then and there. So whenever I'm having a bad day, feeling insecure, I try to remember that day when I was able to do something right. :) -
Once it really hit me hard. The father of my brothers wife once told me that I'm not fit for IT in general. He thinks that I have pseudo knowledge of IT and Programming.
He just works parttime at home as "computer scientist" and sells routers, pc and such stuff to some private customers. Before he used Filemaker and sayd that he already coded his own CRM with it.
When he said that it really made me sad. But after we talked I looked back what I already achieved:
1. I build for me and friends custom PC's with Case mods and Hard Tube watercooling
2. I can programm in HTML5, CSS3 and PHP
3. I raised a Community with over 60 people in it. We got 2 dedicated Linux Roots (I7-6700K, 64GB RAM, SSD)
4. I manage the Linux Servers on my own with VoIP, Mail-, Web-, MySQL- and Gameservers
5. I built up a complete Community Solution with Game Groups, Forum, Tournament System and a lot of custom scripts.
6. Now Im almost finished learning the C++ Basics to code and manage to learn the beginning of GUI/UX programming.
7. Next thing Im gonna learn is Javascript (Browser) and Java, so I can complete my Web Skills and also can code Java Desktop Apps and Java game plugins (don't rant, Javascript is not the same as Java, I know 😉)
So I thought to myself "maybe in the eyes of others Im not a computer scientist, but then Im on the way to be one at least"
But please dont be a douche (the father) and prejudice me, before you don't know what I already can and achieved.
Just because you're are selling computer parts and installing them doesn't mean, that you are a computer scientist and telling me that I'm not 😉
In IT you're the smith of your own merit!7 -
Life can't be too bad when most of your spam calls are from recruiters. It made me emotional to remember 4 years ago when I was the one calling to them.6
-
That would be the time when i got fired from my last job. Hosting company, it had lots of good stuff and bonusses, coworkers were great, i was doing really important stuff when suddenly, i got fired and replaced... 'You have a too strong personality, sometimes you're just too outspoken'... At hearing those words, i felt very sad. Took a few bottles of champagne from the fridge at work (they had those apparently a year already, nobody touched them)... I left the building, together with two coworkers who became friends, drank the two bottles of champagne... i was crying... Because i got smacked in the face due to my personality. Admitted i am an extravert, and i do dare to talk back when it's needed, always polite, but ensuring i was not agreeing. Still i did my job pretty well. I was practically the only one that was multi-lingual!
After that i became a freelancer. It was a good start, a lesser good intermission, but next month i am starting at a goverment department for long term, so future is looking good.4 -
The day I discovered Schrödinger's lesser known paradox of simultaneously being fired and not fired.
This isn't really much of a dev story, but I figured I'd share it anyway.
About two minutes into signing into all my stuff, I suddenly was kicked out of everything. I tried logging in a few more times, and then suddenly started getting the error, "Your account has been disabled for security reasons." I couldn't sign into chat, and co-workers confirmed that I was missing from the company directory. My manager didn't come in for another two hours, and we couldn't get anyone else to answer what the hell was going on. So I was kinda panicking.
Eventually, we found out from one of our coordinators that someone else with the same name as me was leaving the company, and they had deactivated the wrong person.
It ended up getting a lot better. They told me that it could take up to 48 hours to restore my access (it took longer), so I found stuff to do so I could maintain my paycheck. One of those things was assisting someone with data collection and processing, where I eventually said, "Dude, I could totally automate this," and now that's what I'm getting paid to do.1 -
My most intense day as a dev was when we had a product announcement day (with 70 engineers from dozens of companies invited) and the night before the app still didn't run all of the way through.
My team and I worked all night and had our first successful run-through at 10am when the announcement presentation and demo was at 1pm. All I can say is that I didn't breath when that demo was running live... But it worked flawlessly.
After that experience I realized that I had enough of non-tech management setting unrealistic deadlines, quit that job, and am now helping to build a startup. It has been so much more fulfilling and now I set the deadlines. 😎7 -
Hopefully seeing the app that I've been working on for months officially released and on both the App store and google play store.
I say this because I've been waiting months and months for my boss and some other people at this company to be done with the privacy policy + terms of use for the app (which is needed due to how the app works) and I want to resign soon due to minimum wage + 2 hour commute twice daily + want a proper development culture (get treated as the IT guy at work) -
First payment i received for doing someone else's homework. I was staying at a dorm and said to roommates "pizzas! Im buying"
-
The first time I caused a massive error on production.
The good news was the site didn't go completely down. The bad news, however, was that it went down for 60% of our users, and because it's only partial, it got detected only after about two hours.
Everyone halted what they were doing to help investigate the issue. When it turned out that my latest commit caused the error, I was told to fix it... with the CTO and senior software architects watching.
It all happened because I deleted one too many line, an if statement, making the accompanying else statement a complete nonsense. It was a corner case code unforeseen by the QA guy.
The attached meme perfectly describes my feeling for the rest of the month following that accident.
2 -
When I was a kid I programmed a musical tune in QBasic (1994). It was magic. That "beep blips woin blop tuuuuu blups" coming out of the 386 builtin speaker just sounded like: "World, you are the next".
-
When I made an app for a hack someone else discovered for Android's Spotify app that increased the quality without paying for premium :P (Root only) Was based on a bug with enum in the app.
-
Today,
My "big boss" call me because I take too much time to develop a website. She thinks all I need to do is drag n drop. Why the f*ck do you need to hire me if it's only drag n drop you "super smart ass licker"? Man, this old people need some update about technology.
Btw, the "drag n drop" idea came from Dreamweaver YouTube tutorial.2 -
Once while making a automation program for a friends errr academic betterment. I realized I had taken three of the sacred caffeine pills and chewed them unlike normal. Needless to say this increased the surface area tremendously. I thought I was gonna have a heart attack right there at the age of 20. And all I could think was, "fuck my screen has a lot of dead pixels."
-
When I was a graduate I often had to do proof of concepts and one had to be done by the weekend, I'd only been given it on the Wednesday. After a few sleepless nights I had it working or so I thought. On the Friday afternoon the CTO had a look at it and spotted a bug, he told me about it and I stayed in the office until about 10 when I finally managed to get some kind of fix in place. I emailed him told him I thought but was working and shouldn't happen again.
A few hours later no response I get a phone call from him screaming, shouting and swearing calling me useless and a waste of space etc. Etc. To the point I logged in desperately trying to fix the issue in a very hastily written integration and ended up having quite a major panic attack woke up on the floor and immediately went back to work. On the Saturday morning one of the senior Devs logged in and managed to fix it in the database and everything went fine in the end.
I went into work on Monday fully expecting to be fired from the way the CTO was speaking to me, I went to my line manager at the time and he just said don't worry. I left it in his
hands and things went back to normal. That call put a pretty serious dent in my confidence for years, but I learned a few valuable lessons which I stick to today.
Never work on serious shit after 6, use a second mobile for work which is turned off at 5 o'clock, properly test all fixes and always ALWAYS have someone in between graduates and senior management because honestly they can't handle the shit that's flung from above.1 -
When I cost the company half a million.
We recently got incubated and signed up for an accelerator programme, it was a life changing moment for me especially after having worked with my startup unpaid for almost a year. So naturally, it meant a lot to me.
But my friends / colleagues had to leave for a trip leaving me to work along side this other startup in the same batch. They needed a front end guy for their web stuff so we naturally offered our services except they needed me to work on Angular and I didn't know jack shit about it but pretended I did.
I couldn't reach out to my friends for help because I felt bad and wanted to prove my worth, and I pressured myself to the point where I called the client our batch mate brought on board making him leave.
I lost credibility as a professional, trust as a friend and my place at the office because it's gotten extremely awkward to go back there.
I fucked up my one way ticket out of my current certain household circumstances and realized I'm just a shitty developer who's all talk and no show.9 -
I once saved lives sending cpr teams to heart attack victims through an sms gateway platform.
This was amazing considering it was back in 2008 ;)11 -
The day I discovered I have a limit to the amount of crap and abuse I can take. The following day I handed in my notice at a place I had worked for 7 years. That was 3.5 years ago, have been happily freelancing ever since.1
-
Had to program an entire ecommerce site for both a city soccer league and baseball league. Around 50 teams each. No planning or anything beforehand. They gave me around 4 days to complete the project. Once everything was squared away, of course they complained and said that half of the teams were wrong. So I had to stay until around 11 pm in the office fixing everything that Friday night. Of course everyone said it was my fault. I blame it on the lack of planning.4
-
After 1 week working on a screen (design, logic, testing) my boss comes to me saying that what I've been work won't be necessary any longer and I should discard it.
1 month later asks for that same stuff and I tell him (jus like he said I should do) that I discarded the code.
Starts calling me names and how useless I am (this was normal).
So I pick up my stuff and just get out while saying: "please, if you are so damn good, you can do that shit yourself, I quit!"
Was there for 1 miserable year and that was my best choice I made till today.
Right now the company closed cause all the devs ended up leaving him6 -
When code is already working and reversed engineer to compare how efficient the current vs previous code. Now, blames self when prev code is an unorthodox code. ^_^1
-
Spent about 3 hours arguing back and forth with a QA engineer on what a particular API call was *supposed* to do. It actually got a little heated and probably bothered me way more than it should have, but in the end he comes back with "well why don't we just ask the dev that wrote the code in the first place". Guess who that was?2
-
The day I got hired because my (now) boss saw me showing off my super powers as a dev to some fellow students. He liked that I was so energetic.
Now I make quite a lot of money (for my age) and learn so fucking much. By the way, I'm only 17, so it's quite nice.6 -
About to enter the snake pit of lawyers for a client call about a late project. Putting on my super suit.
2 -
Trying to program at all when your soulmate that you've been together with for over 14 years moves to her mother because of relationship problems. And suddenly you feel like a truck is crushing you constantly. Ah fuckit11
-
A company you loved working for announcing mass lay offs due to a lack of funding.
We were like a family which made it all the worse.3 -
Layoffs happen all the time. But when you survive it and come back the next day and see the empty cubicles occupied by very senior devs who were really close to you and mentored you.
Had to go through this twice, 2014 and 2016. Thankfully we still meet up at Hooters every Friday and rant, and that's our version of a 'weekly' -
There are so many. One that gave a lot of warm fuzzies, was when I was teaching pointers in a C++ class, and as I was describing them, watching the faces as the light bulbs came on one by one. You have to understand, these weren't school students, these were professional Devs adding another language to their coding toolbox. It was so cool!
-
Hard drive head crashed and corrupted my entire android app source code which took my 5 months to build. I was depressed for 2 days and then started working for it again and updated the app on the store in 3 months. It was a terrifying yet amazing experience. Definitely don't want to go through that again.
Now I keep backups on the cloud. Lesson learnt.7 -
Last day of internship:
"You will not become a developer, at best you will be a code writter".
That struck hard at the time.5 -
When I was made redundant (business I was working for collapsed) 5 days before Xmas and 2 weeks before birth of my first child, with no pay, no redundancy package or anything.
Good times.3 -
My most intense day was in the company at the day we had to publish a website containing lots of jQuery & CSS animated stuff.
We planned to go live at 3pm but due to the fact that before lunch time there began to appear more and more styling and animation problems, we went live at around 9pm. I was sweating and nervous as hell the whole time.
At least my boss and I went to drink a few beers right after that. ;) -
My daily scrum, the team I'm in doesn't care and just blows our 10min daily into a 1hour "talk about anything" meeting2
-
The day I was only one ++ away from getting the stress ball.
Decided not to claim it in the end, though.7 -
First software refactoring in the company I worked for. No test environnement because "who needs it?", no unit testing, no comments, had to make sql updates and shit, was scared all day long that something would fuck up.
"Fuck fuck fuck, forgot a part of the where !" Had to fix everything quickly so no one would notice, no coffee/smoke pauses. On top of that, got a ton of retarded requests from the PM and other technicians working with me like "hey boi, could you add an icon to every button we made? There's like a thousand, we need it for tonight, our client will come visit us and I want to show him a better interface blablabla"
And since I was an intern, I couldn't refuse, had to work like a prostitute in virgin-land, and for what?
"Oi, you did good, now do other stuff"1 -
When our org got sold to another company, and we weren't informed about anything that was going on. There were whispers of emails that went out, that we first thought meant we were keeping our jobs, but it turned out emails = severance packages. Friends that I have worked with for years were dropping like flies and all we could do was wait.....it was awful, and extremely emotional 😢1
-
When there were some coding questions to solve that I thought I can do but can't do more than 50% of them! It hurts to heart and I felt so gloomy.
-
Going around the building of a large mega corp telling all my internal customers their projects are going from "green" to "red" because I had a layoff meeting later that morning.
Ever see adults cry because their "favorite developer" was getting sacked and they would not see their project in time, or at worse, canceled?1 -
The day, today, when i go to a different world. School camp!
Say bye to dev world!
Time for nature.
Wait... I forgot to turn off my laptop!
Nooooooo1 -
Most emotional day?
My friend/colleague getting fired out of the blue!
I was so pissed I immediately tried to resign, but they convinced me to calmly reconsider in few weeks. That would be right about now...2 -
Most intense day for me was at the very start of my career. Internship... went with product manager to client's office while PM installed new test version of our product for on-site integration testing. Shortly after deploy, client manager came over to ask why production had gone down...
Turns out that manually typing DB name as part of deployment script is not, erm, risk free. PM entered production DB name and took out a very busy call centre for a few hours. Agents in tears, customers raging on phones, etc! After we restored and got everything back up and running, he reached me the keyboard and said "You're doing it this time."
My attempt was problem free, thankfully. Earned many brownie points that day.1 -
For the first time, wholeheartedly prepared for an interview for a major IT firm, only to be rejected coz i didnt know what methods are present in a library i had never used!! Wanted to throw the guy out of the window!! 😑3
-
Dealing with stubborn devs who don't understand why non prod apps shouldn't talk to production apps.2
-
Got my first live 0.68$ application fee from stripe from my bootstrapped startup beta webapp I've coded myself2
-
My first day of my internship. I was confident in my abilities to develop, but wow. I was totally put in place after the first day. I realized that I didn't know as much as I thought. Almost wanted to change career paths. I'm thankful for that day because it really made me push on and become a better person and programmer!
-
My most emotional moment was when I wrote my first android app (it was a calculator but it looked cool) and started it on my phone. I was 15 at the time (this was 6 years ago) but those were my first steps in programming1
-
Finishing the whole front end for a pretty big site in 2 hours with 2 people and only 1 knows HTML and CSS2
-
Many years ago, I wrote an app for a company to provision users in AD and Exchange. It disabled 10k users and no one could work. Good times.2
-
From the moment I realised I was a TABs guy, and she a SPACEs person, it was all over. Love became terribly bad "indented" from that very moment.
2 -
In the third month at my first job, a batch processing script I wrote DDOS'ed my company's API servers on a saturday and caused hours of client-facing issues2
-
The day we had to have an app ready for an upcoming demo. Management said everything needed to be done by the end of the day. My change was done, but was dependant on another change being merged first. I had been in the office since 8am. It didnt get merged until 5pm. I was in the office until 8pm trying to fix the insane merge conflicts. In the end i gave up and went home. The next day we discovered that the "deadline" was made up anyway so we still had time. I wanted to flip every single table in that office.1
-
There is a Codingame Level wich took me a whole fucking day. I was soo happy when all those test cases passed!
-
When my boss told me this:
Boss: I have some bad news that I didn't want to tell you on the phone.
Me: So I'm fired?
Boss: No, the roof of the server room collapsed and most of the computers are really damaged.
Me: Then tell the technicians to start fixing, why are you telling me?
Boss: Now it is your job ...6 -
I had a client who wanted me to install a php project from github on a live server. I agreed to do it for $10. I set it up and it showed the setup page. so I left it there and thought this is probably how far the client wants me to go.
But then he asked me to go through the setup and completely install it. I was like ehh..ok I will do it.
But then came the shit storm of bugs in that project's installation module. Had to run through a gazzillion issues on github. Eventually I gave up.
Then I tried installing it on my localhost and surprisingly it installed fine. So I just made a zip and uploaded it to the server.
2 other devs had failed to get the job done before me. I t felt really good to get the job done.
The client tipped me an extra $5 too.
=)2 -
Here is mine.
So I have been working on a project for 2 months now at my company. Briefly, I describe it as the WordPress of the surveys (create, edit, share, tons of features). Last day, I had to implement one last feature in order to make everything working and as similar as possible with the final product. I had 10 minutes to do it (had to go home) and I was like "Tomorrow bro". Believe it or not, 10 minutes was what it took me to end this fckin' project, and go home on time like "Good job Man, relax it's friday now" :)
Thanks for reading ! -
Some of the rants this week have been really touching and amazing. This small community holds within itself so many amazing stories.
The most intense day for me was my last day at my first job. It was sad to see some of the best developers I had personally known for the last time. I learnt a lot there and had some really fabulous moments. -
Accidently created a folder called "assets" next to my "Assets" folder, deleted it from MonoDevelop and instead it deleted both of the folders... irrecoverably...
Maybe spent about a year on that project and I lost 6 months progress...
Like how did it even manage to delete my folder irrecoverably?!?!1 -
At the end of an internship we talked to the lead developer of the company to hand over the project and he was thanking us, he was happily surprised with what we delivered etc etc etc.... After that he asked if we were ready to graduate next year, but we were just 2nd year students. After that he was silent for a moment and said ' take what i just said and do that times a few'.
That was an amazing feeling we got from that.
After that he probably ran to the boss asking why he would ever trust 2nd year students with such an important project but that is a rant for another time 😂 -
I went to meet a client with our CTO. In the meeting we discuss the implementation of SAML SSO. Their SSO guys asked whether they need to build 2 trusts for our application because we have 2 modules that use SSO. Both the CTO and I were not sure because we did not have any prior experience of integrating SAML SSO. To act professional, we couldn't say we were not sure. So the CTO said we needed two trusts. I immediately added "We may only need one. Let us do a bit of investigation and confirm."
After the meeting I did the investigation and found out we really only needed one. So I sent out an email to tell the client, cc the CTO. 1 minute later I got the email from the CTO "why tell them one when I said two?". When it's an immediate response with only 1 line, I know I'm in trouble. So I called him and was ready to explain to him. I couldn't. Later I found out the time I was calling him, he was talking about this with the CEO.
I thought maybe I can explain to him when he's available. The next morning as I came to work, the CEO asked me to come to his office. He closed the door, and told me the first line the CTO told him the day before was "I want him (me) fired." I was so shocked. Having been working with the CTO for quite a while, I was surprised he said that without even communicating with me. Did I do something that wrong that you don't even bother to tell me what's wrong? I was not fired because the CEO at least asked what happened. He also understood I was actually making a better technical decision. But well, guess I shouldn't be making a decision when I had no power to. And even I believed the client heard my "let me investigate first" comment, the CTO didn't. I still got an unofficial warning. For that whole day because of the stress, I don't remember getting anything done.
Fuck that acting like profession and smart when you are not. I'd go down the path of becoming professional and smart instead. And fuck metting with clients. I'm a dev don't fucking dare to talk to me and get me fired. If you wanna talk, talk to the big guys who don't make us look bad like I did.
If you ask me today I still believe I haven't done anything wrong there. So fuck everything.2 -
What a coincidence. This will be that day. Not as dev, but as a student. I know this place called DEVrant, but I'm really nervous right now, because of the tests today. I didn't learn and I'm gonna fail all.
But not the tests the only thing I worry about. I hate this world becouse everybody needs to work hard and there is no break. Rarely you can get some air, but one second later you're in the deep again... I don't know what to say or what to do. This will go in my entire life? This is horrible.
I know. I'm just a student. "It will be harder." you say. But I've had enough of this.3 -
New android dev joiners... Never Ever... I am saying.. never ever update the test devices in the office...!!! 😣😣
-
Today. I had to argue against using unencoded characters in URLs. The manager did not take me seriously.
Fuck everything about this. The contract jobs I've had lately are the worst jobs I've had in the past 10 years. This latest company hires junior developers because they "need senior level experts".1 -
When everything kind of just clicked.
I was struggling with learning how to program for quite some time when I first started, but one day I'm not sure what happened but everything clicked. It all started making sense and I felt like I could do anything with code. It was on that day that I knew I was going to be a dev for life. -
Production goes down because there's a memory leak due to scale.
When you say it in one sentence, it sounds too easy. Being developers we know how it all goes. It starts with an alert ping, then one server instance goes down, then the next. First you start debugging from your code, then the application servers, then the web servers and by that time, you're already on the tips of your toes. Then you realize that the application and application servers have been gradually losing memory over a period of time. If the application is one that don't get re-deployed ever so often, the complexity grows faster. No anomaly / change detection monitor can detect a gradual decrease of memory over a period of months.2 -
Layoffs, hard to see good working people leaving the building.
You can feel the mood of the company the next days/weeks is a killer of productivity. -
I've been reticent to chime in on this weeks group rant, feels too personal...but it is what is is.
Most emotional was losing a dev to cancer, and an analyst to an allergy, and an engineer to an accident...ugh.
Most intense was probably losing servers and hard drives without recovery, not being able to get databases back online because they went down so bad, websites being down, not meeting some quarterly goal, shit not building, email campaigns that go sideways...fuck...anything involving reactionary leadership...unrealistic expectations.
But all that shit, while seemingly important or "stressful", pales in comparison to someone you fought with in the trenches not being there anymore.
restore -if friends -
I once managed to replicate data from a scientific paper by writing a C++ program, at the first try. I still can't believe it to this day.2
-
The particular day
it was in April.
A news to convey
of a new job to cradle.
The first one it was
and well it paid.
One problem existed because
too late I was laid.
And still in school
for two years to come
I'll sit on a stool,
my keyboard to drum.
Good it was on paper
but too young for me,
using C shaper
being on a coding spree.
In two years time
I'll hope for the best,
tired of making the rhyme
I'll let you imagine the rest.1 -
I'm organizing my leaving handover etc,
Just spent the better part of 2 hours making sure a graduate, who due to come on the project has the environment all set up, which is cool dont wana see them stuck,
But when u ask a mid/senior level dev how his set up is goin and he replys with his user name and password for a VM and says, "Work away at it yourself" ,
thats when im trying to hold back my inner Hulk and not lose the Fucking plot! Lazy Cunt!
-
My first dev job was for a .net shop. Until then, I had only worked in Java and PHP. This place didn't have the normal team structure, and I soon found that I was going to be working solo on the projects I was responsible for. I'm my first week there, I was tasked with making make revisions to an application in a new language, with a new toolkit, solo. A few weeks later was the most intense day I've had as a dev, as I put in the change control to release my update to production.2
-
When your project is actually implemented in real world solving real problem with the solution you created
-
My first internship.
The webdev department for a engineering company is in the basement. I was given a cubicle near the middle by the wall. The ceiling light was broken so I had to work in the dark... It was a 7-4 with no pay nor do they cover any expenses. I did manage to use the experience and got a job offer at a 'proper' software company in the end. -
Lately? Today. About to get on a call with some angry lawyers about their unhappiness with a product they haven't paid any attention to until they began feeling like I screwed it up.
-
Wrote a new feature for our flagship product in C. Worked perfectly, no issues. I was told to wait before submitting to SVN.
Because my company is a little cheap in engineering, they took my Green Hills license for another dev to use. I wasn't using it, and now can't compile.
Then, a month later, I was asked to submit my feature to the repo, they needed it in done version, do I did. Still not able to recompile to see if other changes broke anything...
As you probably guessed, no one's code complied after pulling from the repo! Big embarrassment. Weeks later I was told that it wasn't my fault in the end... I don't remember how my code impacted it, but man, it was a bad day for this dev.
Never again!1 -
Everytime I applied long leave, my client and PM will plan for important feature, but they say start the sprint and for other new people i have to give KT, and they will take care. I know how that will screw up the system. So at the time it's nightmare late night at office, in office time KT, no weekends, stand-up for 1hr(every time QA will ask, what we get after this sprint). Stupid clients changing the requirements after stand-up.
Everytime code base screwed and need to refactoring. So as much as possible core functionality I'll complete and only bug fixing for newbie. I hate those days. -
I had network problems.. and you know.. no shit.. the problem solve thing which might actually be just a for loop solved it.2
-
I guess days lile today, where hard work and solid effort is rewarded with a promotion and a sizeable increase in salary.
Feels good man -
Trying to remote in your home PC to setup git but because you have 2fa you need to signup about 6 time than creating a repo to push the home project to and setting up an exact copy of the tools on your laptop to continue on that said home project.
-
In my first few months of my first dev job, I written this fragile piece of code in, trigger warning, PHP that sent out email reports to my clients. It was a two men team, and we have no clue about TDD or how to do unit testing for such code. We would just run that piece of code manually do send out dummy emails to ensure things were working.
One day the code broke. I was told by my boss to fix it. Spent the entire day trying to fix but couldn't get anything done. Finally at around 7pm my boss came by and asked why is it I couldn't get it fixed. He helped me troubleshoot and fixed it. And subsequently told me "c'mon man you're better than this."
It turns out that he changed a part of a code that was supposed return an array of strings to an array of objects, adding a second attribute that wasn't even in use.
So what that meant is that he changed a piece of working code, to include a property he didn't need, committed and push to production without even manually testing it. AND TALKED SHIT TO ME.
That was the day I learned git blame and began my journey on TDD. -
When my e-commerce system built for a school didn't calculate totals properly at launch and I had to take it down, re-charge people, and re-launch the next day.
-
That day (today) when I posted at devrant that a program that i wrote was shown in a movie and the only reaction was the comment that this must be a joke.
Then I deleted the rant.
Thank you for the intense day!10 -
Teammate used some excel sheet concoction/gimmick to execute hundreds of thousands insert statements on production tables. A few days later (when I'm on call), I find out he didn't adjust the cell formatting on the aforementioned excel "tool", so all the network addresses from the insert statements were put in scientific notation, on prod...thus breaking a lot of the things. FML
-
Though I started late and I'm not very self confident on my skills:
All those moments I was able to see issues or solutions where no one else did...1 -
University projects. I used to always delay them till the last day/days(somehow I knew when to finally start working to be just in time to complete it). There i would be not sleeping for 2/3 days and submitting like 5/10 minutes before deadline time.
P.s. I've only been working for about a year so not much to quote from there -
Actually, it was probably my whole first two weeks in my first dev job. I got hired while still attending community college for my associates, and was woefully under-qualified (I didn't embellish, they hired me anyway), and my boss went on a three week vacation three days after I started. I had no idea what to do, didn't get much help from others on the team either. First couple of weeks were rough.
-
Once I was waiting on a client to ok some minor spelling corrections in an app. I don't know what I was thinking but I pushed it to the store without thinking.
I told my manager, and I was so annoyed at myself. I was trying so hard to get into a senior role and I was feeling super terrible. I actually requested a letter of warning, but my manager just laughed and refused. PHEW! -
Most emotionaly intense?
Every day! - when i have to merge in changes in production to git and figure out what the idiots changed in mangled minified javascript, i'm really happy i didn't kill anyone yet. -
Every first of a month is our most intense day because we have the most data throughput then due to lazy people we get data from. And boy will it be even more intense when something broke because we were forced to deploy a new feature the day before...
-
I needed to migrate one DB to another with one sql suite but instead I fucked up and suddenly disconnected both DBs, without being able to reconnect them again
I waisted a whole day for debugging, but found nothing
And guess which magic fixed all issues? On and Off a service of an app
On and Off!!!
The fun thing is that restarting the server didn't help, but the only service helped1 -
I always have doubt on myself that i will never to create a system,right now almost 20% eventho it was just 20% but it mean a lot to me 😢 #student #internshipproject
-
When I was working on the bug list and our testers kept repeatedly assigning me new bugs and "do-overs" I don't think I've ever been so angry
Top Tags
Weekly Rant
View