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
-
So my coworker just got this error on production server, and well, the stack trace stood out to us all...
5 -
That feeling when the feature you've been working on everyday for the past 2 months is pushed into production.
My baby's all grown up now 😭8 -
Had to wake four people up at 2 am to fix a crashing service.
10/10 would deploy to production on Friday night again.
24 -
Useless notification..
Working on a Job Portal Application, i made notification functionality.
At least i caught this one before production
5 -
Confession of the day:
1. I work in release mode
2. I work on the main branch only
3. I test on production13 -
You think a junior dev pushing his code onto a production server is bad? Wait till you have that admin who is illegally mining Bitcoin on your production server. 😂
I went for a Cyber Security conference today with one of managers and this was one of the life experiences some of the speakers shared.18 -
My computer science teacher won't stop developing on the production server 😭 he switches the branch on the production machine to dev all the time and merges broken code into master. Kill me4
-
Interviews for developers should say: This is an error on production. You have 10 min to find the solution on google.
This is more efficient than making developers write algorithms.7 -
We had issues with lack of disk space on our production SQL server. Another developer decided to delete the databases he thought weren't in use to clear some space.
Ever think about checking first?!
Production chaos!7 -
One of my colleagues at work has cooked up this amazing amazing method.. and guys brace yourself.. This code is on production..
17 -
Product Owner: "Our definition of done is putting it on production. So you are only done if it's on production. Otherwise our sprint goal is failed."
So we put it on production.
After deploy, some content manager appears: "Why is the system doing things? I was told this should not happen today."
"Erm, we have put the feature on production as we are only done if it's on production."
"Well, yes. But it should not be live yet!"
Oh well. Communication, or the lack thereof, does never fail to amaze me ¯\_(ツ)_/¯5 -
Never, ever, ever, release on a Friday. But.....
if you do.
Add this step as part of your production push process.
2 -
"Read-only Friday" rule: On Fridays, you don't deploy new versions, don't merge code into production, don't update databases, and a lot of others "DON'Ts"4
-
PM (on slack): "we’re about to deploy to production".
Me: "ok"
… I keep on working on a task / remain available for any post deployment issues …
PM (5 minutes later on slack): "deployment broke production! We need to handle this NOW!"
My dev colleague has already called it a day, but I’m still online
Me: "ok I don’t have access to prod, can you describe what’s going on? I can’t reproduce on any other environment"
PM: …
10 minutes go by
Me: "anybody there?"
PM: …
45 minutes later, I realize PM is offline
The following day:
PM: "ok we got prod running again" (turns out it was client’s fault for not updating a config we as devs can’t access)
PM: "but we’re REALLY UPSET! You guys need to be available to intervene for any issues following deployment to production! At least one of you should be available!"
Me: "but, but…" 🫠14 -
Refactoring and writing tests for code that was code written by intern and is on production about one year
-
Friend: I just love the adrenaline rush caused by bungee jumping
Me: I just love the adrenaline rush caused by deploying untested code to production server on a Friday night5 -
A few days after deploying a big important Website into production, I wanted to copy the whole thing including DB back onto our test server for future testing/bug fixing if something comes up. (Last changes were done on production server before going live)
So I opened SSH, removed everything on the test sever aaaaand then I realized I was connected to production...
Took about an hour to get everything up and running again. We didn't tell the client and hoped it would not be noticed.2 -
I left some spaghetti code on production at the company i left, i really hope my replacement isn’t a psycho who’ll try to find me3
-
I released my first legitimate Android app to production a week or two ago, and it already has over 50 downloads on the Play Store! 😄😄😄
12 -
Running a huge migration on our production db.
Takes 45+15 minutes (migration+tests) on my lappy. So. I'm going to be bored and slightly worried for the next hour.
Hopefully the production servers will be faster.7 -
“In order to release on production you merge on production”
Makes sense.
“In order to release on staging you merge on release”
Wait, what?
“The CI for the staging release is called release to production”
What? No, stop!
“You also need to create a tag called pre-production-deployment, so that staging can work”
STOP FFS
“It’s very easy, you just need to read the documentation!”
How do people do not realise they are spitting out bs?3 -
Accidently deleted user table on production database and some backups where broken. Had to deploy a 4 days old backup...6
-
It was a normal school day. I was at the computer and I needed to print some stuff out. Now this computer is special, it's hooked up onto a different network for students that signed up to use them. How you get to use these computers is by signing up using their forms online.
Unfortunately, for me on that day I needed to print something out and the computer I was working on was not letting me sign in. I called IT real quick and they said I needed to renew my membership. They send me the form, and I quickly fill it out. I hit the submit button and I'm greeted by a single line error written in php.
Someone had forgotten to turn off the debug mode to the server.
Upon examination of the error message, it was a syntax error at line 29 in directory such and such. This directory, i thought to myself, I know where this is. I quickly started my ftp client and was able to find the actual file in the directory that the error mentioned. What I didn't know, was that I'd find a mountain of passwords inside their php files, because they were automating all of the authentications.
Curious as I was, I followed the link database that was in the php file. UfFortunately, someone in IT hadn't thought far enough to make the actual link unseeable. I was greeted by the full database. There was nothing of real value from what I could see. Mostly forms that had been filled out by students.
Not only this, but I was displeased with the bad passwords. These passwords were maybe of 5 characters long, super simple words and a couple number tacked onto the end.
That day, I sent in a ticket to IT and told them about the issue. They quickly remedied it by turning off debug mode on the servers. However, they never did shut down access to the database and the php files...2 -
Rant, but also want to know, how the fuck do you accidentally drop a database link. In production. On the most important database. Housing our biggest applications.8
-
The One thing every Dev should know about:
Never Push to production on Friday.
Coworker pushed to production yesterday.
Customer saw it and likes the new features.
Customer also saw a shitpile of Bugs.
Customer is angry and my weekend is runined -
We have a pretty simple rule in our team:
Do not deploy to production on Friday.
Well thanks to the client being very slow to reply to me, they only signed off on launching the app at 15:30 on Friday, for a big campaign the app was built to facilitate starting Saturday.
Guess who had to bite the bullet and launch a new app into production at 15:30 on Friday.
Guess who got a text from his boss at 19:30 that there was a critical change required tonight.
Guess who was making code changes and deploying to production at 21:15 on Friday night while drinking Gin and tonic...
Nb This was a project only i was assigned to and came in as a rush job at the last minute.9 -
As a developer, always expect the unexpected! Except when deploing to production on friday afternoons, then you know exactly what to expect.1
-
So I can't VPN into my production servers because our fucking government decided to block them
How on earth can I work you ignorant basterds12 -
Turns out that dropping all tables on the production database wasn’t such a good idea. 😅
Thank god we had a backup from 10 minutes before it happend.6 -
Type T ( something something... )
...
Type * TP = T;
TP.do()
> Be me
> Production code
> Update Type structure
> SEGV
> Wtf why was this even working
> Ask senior
> senior y u do dis
> bc
> Why were no errors
...
> mfw
> He says
"I added -fpermissive and forgot..."
On production since May
...
...
...
... 20072 -
Patching a bug in production is like trying to collect marbles on a train track... with a train coming toward you....3
-
Never ever have a tab open on production server database. Changed all users passwords by mistake. Thought was my test database.2
-
My worst dev sin was leaving out the 'WHERE' in a SQL update statement on a production database
Set every booking to be owned by the same sales consultant 👀2 -
Today is Friday. People are generally happy on Friday because it's the weekend.
I have a production upgrade tonight, which potentially can go through the weekend.
This is my second production upgrade support in a week. I'm sleep deprived and getting disinterested and seemingly in the want for a holiday.15 -
Somebody at Samsung is testing something in production 🤭
It's "Find my mobile" which is preinstalled by default on Samsung devices
8 -
Today users weren't able to sign up on our website in production.
The guilty code :
int ttl = 5256005760;
The first who find why will have a candy.10 -
Nothing screams panic like accidentally deploying an older, broken staging build, that also run outdated database migrations on start, straight to production3
-
Does anyone else get that awful hot feeling and rapid heartbeat when breaking a site on production? I have nightmares about it 😬2
-
Just pushed my first ever ticket to production! AAAND on top of that, did not take down our entire system. 😅7
-
I hate it when I ask the customer where did they test it or where the error is.. On test or on production? And the answer is yes. O.o2
-
Adding a feature to webapp...
Webapp relies on database in production server...
*adds feature to production webapp directly*
Every page: ERROR 500
Manager: what did you do???!!!! You MESSED UP the production, FIX IT NOW
*Use ctrl-z because manager doesn't like Version Control*5 -
- "Hi A, we had a bug in production due to a changed category ID which we were not informed of."
- "Oh but my API just proxies the content from team B."
_____
- "Hi B, we had a bug in production due to a changed category ID."
- "Ah, I have nothing to do with category IDs, you should talk to my colleague C."
_____
- "Hi C, we had a bug in production due to a changed category ID."
- "I wish I knew anything about that, you should contact person D!"
_____
- "Hi D, we had a bug in production due to a changed category ID."
- *changes status to "Absent" on IM*
ERROR_TOO_MANY_REDIRECTS1 -
Having one of those days where the code works on the development VM but not on the production box.... FML
-
The awkward moment when the website is faster on my shitty computer than on its pre-production server...4
-
If I recognize someone by their username or remember their name.. it's usually a bad thing because they're on my mental blacklist for fucking up Production....
Ahh life in IT Ops...3 -
Dev1: "How did you wrote this code? It causes bug on production."
Me: *checks on gitlens*
"Dev1... 3 months ago"1 -
Don't you just love it when something works in your development environment, your staging environment and then randomly breaks on production? :^)6
-
Copy-Pasting code from the StackOverflow into production code is like chewing gum found on the street. 🙄1
-
Quick reminder: don't deploy to production on you last working day before holidays :)
Wish you all happy new year)
GG!5 -
So this just happened...don't test on production kids (....sometimes you have no choice BUT DON'T F**KING DO IT OK!?)
6 -
When you get a mail from a client at 11am on Sunday and he tells you he wants a change for the Monday production...7
-
docker
Having exactly the same shit running on my own machine as in production makes life so much easier.2 -
Does anyone know to get rid of a programming CURSE?
"You will have unique ERRORS, only in production, which would not be found on Stack Overflow"
:|
1 -
Didn't reviewed the migration file and ran the script on production which altered the column from LONGTEXT to TINYTEXT and truncated all the data. 😞2
-
I work on a warehouse dev team. One day this past year, I was trying to deploy a new build to a QA server. Earlier that day I had been looking at the logs on the production server and had left the ssh session open. I had been working for less than a year out of college at this point and shouldn't have had access to deploy to the production server.
Long story short I deployed my QA build to the production server and saw there were problems connection to our production database. Then my heart dropped in my chest as I realized I had just brought down our production server.
I managed to get the server back up by rolling back in about 5 minutes and no one ever knew except some people on my team.
I felt horrible for the longest time. Later in the year another guy that joined my team that has about 20 years of experience under his belt did the exact same thing, but needed help rolling it back. Needless to say, that made me feel a lot better. 😂
Definitely the worst moment of my year.3 -
Overheard a conversation...
Dev: We should focus on getting it working in production, then we can copy it over to dev so we have a working version.
Me: da fuq?4 -
small victories... leaving little fuck you notes all over the code..
along with all the test cunts that still get incremented on the production..
-
"This needs to go into production NOW"
Five hours later...
"That fix is on production now"
"Thanks, did you fix that other bug on production? We need it fixed now" -
Difficult tasks, dog is sick, S.O. suffering from depression, sleep deprived, and now I accidentally type "rm -r / ./" instead of "rm -r ./" on the production server. Whyyyyy12
-
Got informed that there is a bug in production that needs to be addressed on top priority.
Me opens Android studio to check.
Android studio: chill bro2 -
DONT do production stuff on friday afternoon. This friday evening we had an issue on production and just wanted to do a quick fix. The fix resulted in a ddos attack that we accidentally started on our servers in an IoT project. We contacted all customers' devices and asked them for response at the same time. Funny thing is that the devices are programmed to retry if a request fails until it is successful. We ended up with 4 hours downtime on production, servers were running again at 11pm.4
-
That awkward moment when you're only dev working on almost dead project and you start making changes in production and then move it to development servers 😬4
-
During my rookie days I used to glorify the fact that I wrote production grade code using vim.
Lol, explains why I would delay on delivery6 -
If you don't know, there are 2 types of bug fixes:
Hot Fix - Patch files directly on the production
Quick Fix - Deploy fix on production and then test it4 -
Hi guys! Im jr dev and i had a great week! My girlfriend letf my house :'( but my project it's working very well on production. It's not a prank!
#TrueStory7 -
Don't test complex functionality before production.. neither unit, nor system tests involved for my android app. Releaseing solely based on hope!2
-
It's 1 AM and I've just finished deployment on production. I should go to sleep but what I do, yes scroll through devRant.6
-
“We are on a hurry, let’s fix in production, then you can write the fix in the repo.” (Multiple times)
Guess why we are always on a hurry…3 -
When coworkers have a var dump on a page in production.-_-
I aint saying shit because everytime I mention something they do wrong I get assigned with fixing it. -_- -
My brain: you have 30 min until you gotta catch the bus, that’s enough for that css fix you wanted to implement on the website!
My development environment: Hey that looks a lot better and works perfectly fine!
My website in production: Fuck you. Fuck your changes. Fuck your bus.
What do we learn? Precompile assets before pushing to production and don’t push to production if there’s a bus to catch 🙃 -
Who can come up with the best DevOps Power Ballad? I'll start off:
Phil Collins - Something happened on the way to production.
GO!12 -
Lets fix this bug in production on a Friday afternoon. (did that three times on the same project). Never went wrong :)3
-
Nothing like Facebook devs saying:
"If there's an error, just pop it up in an alert on production!"
3 -
Switching to R on the last moment from Python for a production build - I wouldn't lie, that was one of the worst choices I ever made.
-
I ran elasticsearch reindexing on production.
My manager asked why there's no item shown on the search page, and I slowly told him, I ran reindex on production.
💣💣💣1 -
I used a test user account to make live payment transaction with test wallet money on production, accounting department just called... I think I'm in hot waters!1
-
Supporting a production upgrade on a Friday night without extra allowances because I screwed up the one on Tuesday night! Yay!6
-
Me: "Oh right I still had to fix that"
Me: *fixes thing*
Me: *checks on staging to make sure it all works*
Thing: *works absolutely fine*
Me: "Cool, let's promote it"
Me: *updates production stack*
Me: *checks on production to make sure it works*
Thing: *still broken*
dsfhjh dsaghdsaupot nvhudfot vnhgue6 -
When you are told the app you worked on is scheduled to go into production on Friday.....
My reaction was "Aise kaise?"
(Translation -How even?)1 -
When you decide it's not worth of your time to go through lengthy code documentation and just run that stackoverflow snippet straight on production.. 🤠
-
Forgetting to write that WHERE statement, on a production database, during a serious case of Schroedinger's backup system, that failed.
....
oops2 -
Head of IT: kindly check what the issue with the following transaction
Me: Is this on production or on staging?
Head of IT: YES
Me: 🖕🏾 🖕🏾1 -
When destiny hits you very very hard.
Man Accidentally Destroyed Production Database on First Day of His Job.
https://hackread.com/man-accidental...2 -
When some seniors backup any file with .<n> on production system. Like if 15y of dozens of different blah.exe.1 to blah.exe.27 are of any value but bloated directories...5
-
Manager tweaks with some data on the production server and accidentally deletes some rows.
*flip table* *rage*2 -
Shoutout to all the devops people currently on their parent's WiFi trying to fix a database issue in production
-
Our IT team keeping our PET Production server alive by resizing partitions on the fly.
#living-on-the-edge
#caveman-practices
-
Here: this is BDD, a Linter, and Git. CI your shit to staging before you CI to production. Never deploy on a Friday.
-
That feeling when you have already fixed the problem on production server on Thursday and got the approval from the client but the same issue appears again on Friday evening.
#WeekendSpoiled
5 -
My worst mistake was to have localhost phpmyadmin up, and beside the production one. I ran DROP on production instead of localhost. That was not a nice feeling when I realised 😐1
-
My mate just pen-testing on running production server using admin credential.
Guess what happen!
And no backup!
What a day!2 -
I quite often run untested scripts on production systems or hot fix JavaScript files on live using Emacs...2
-
Never! Deploy! To production! On Thursday! *banging my head against the wall*
Now I need to revert some things manually on production ON MY DAY OFF 🤦♂️🤦♂️8 -
!rant
Today I finally found a randomly appearing bug that prevented our nightly backup on our production servers! Finally!
Now I can go to sleep in peace. -
What do you guys do on low work days? both in terms of
a) Low energy = low work production
b) Low work required of you/slow work day10 -
One of those mysterious bugs that only happens on production. Want to solve it on your laptop, it's not reproducible. Staging server? Nope. Production?
HOW DARE YOU TOUCH THE LIVE SYSTEM?!?1 -
"Just try it on production"
- a coworker DBA shortly before he desperately had to figure out how to restore to the latest backup. -
A coworker needed to check the number of users for brand. So he selected all rows from users table and then used php's count function. He released this piece onto production.
Later that day he asked me if there's a problem with the production env because his code is working on local.2 -
Fuck I forgot to make a database export before I executed delete statements on a production database...
All went fine though. Nothing broke.5 -
On this Saturday my first full project is going to production and I am unable to resolve one fucking critical bug without db hit. Well still trying..3
-
delete random, unused column from production database
entire app blows up
re-release last change on code pipeline
everything works beautifully
¯\_(ツ)_/¯2 -
When you are working on a mobile app since 2 years and it is not in production yet !.......Fed up with it... -_-;4
-
So I'm currently "assigned" a task in which I need to fix a slow query problem, which isn't a big deal. The biggest problem is that the original team of this project haven't got any means to develop things on your local machine. Looking at their docs and scripts, it seems like everything is deployed to a dev server. But whilst looking for details for this server, I found out that the network team have decommissioned the server!
So my dilemma right now is that I can't test any of my fixes on anywhere besides staging, or possibly production! Inheriting projects is the bloody worst!5 -
Did you ever had to integrate a fucking "API" that is done via mail bodies?
Fuck this shit! Who need responses about success or failure?! Guess this will take a long time to test this fucking piece of garbage... We don't get a test system, we need to test this with the production system of the other company. I hope their retarded application crashes when receiving malicious mails.
Not speaking about security, I bet everyone can send a mail to their stupid mail address and modify their data 🙈
And inside of this crap mail you also have to send the name, street and email of their company. Why do you fucking need this information?!1 -
Deployed to production on Sat evening while drunk, surprisingly everything went smoothly. I think this was the first and last time I'll be releasing like this, lol.
Similar stupid experiences anyone?3 -
TIL don't rely too much on in memory databases if your client runs development and production environment on the same machine.
Just don't7 -
I'm live debugging on the production machine on an 1x year old system in the middle of the night ....3
-
Do people just see reviews (if any kind of work) as an admin task? Just a box to tick on the way to production?
Seems like it is here. -
You know what's hard...
Fixing a bug which occurred in production without having any logs because you log that useful info at debug level. 😧
Now take pen and paper, do calculation on your own and speculate what would have happened in production.3 -
A developer couldn't get a application performance monitoring (APM) tool to trace his application. They claimed that their libraries and their configurations were alright and that the APM tool was non-performant.
The developer then argues with sysadmin that the APM tool can't trace the application and that there's nothing wrong with the application or the configurations. When sysadmin questions whether the developer got the tool to work anywhere, they say, "No" and head off to make it work at least in one place. They come back saying that it works on their development environment (which is their local machine). Sysadmin claims that the system configurations on the server instances cannot be matched by the development environment and there could be a lot more factors to be considered for the problem. The sysadmin asks to prove it on a server instance on one of the test environments and then they'd agree that it is a problem with the tool. They also argue that this is not the only application that uses the APM tool and the tool happily traces other applications with no issues.
The developer tries the same configuration on a staging instance and fails. In order to make it work, they silently uninstall the existing version of the APM tool and then compiles an unstable branch of the tool. It finally works with this version.
They go back to the sysadmin and show that it works on the staging environment, but does not on production. After banging their head on the wall for a while, the sysadmin figure that the tool had been swapped out for the unstable branch that was manually compiled. When questioned, the developer responds, "It works with this version on staging, so deploy the same version on production"
WTF? You don't deploy an unstable branch to production. Just because you can't make it work on the stable branch doesn't mean that it is the problem with the tool itself. There's a big difference between a stable branch and a non-stable branch. How would you feel if the sysadmin retorted by asking you to deploy the staging branch of your application to production? -
How do you guys push changes to you server. ?
I am currently pushing changes to my git repo then pulling those changes on server where I am running the application in production.
I am planning to set up a simple server, to which I will push the changes and it push the changes to the server's running in production.
Or better would be to write a script and run on production servers that will check github for changes3 -
Switching from Linux to Windows on my personal production server... because sometimes logging into RDP is so much easier than SSH.3
-
When i had finished my work and was about to leave i saw commit in master labeled "Testing on production"... tomorrow will be an interesting day1
-
Hotswapping/replacing classes on the production server
We call it "russian deployment" .. No offense -
> checking it once
> checking it twice
> on production it still fails in front of our eyes
> programmers are coming back to the office -
The first error on my first react native app happened on production. It was just once in a Android 4.4 from 2010... how do I even simulate that ? 😶4
-
Who the hell hardcodes their localhost ports in a web.config without updating the release config to the correct production URLs? And why doesn't our ops team pick up on this shit before clicking their fancy deploy button? And why in holy heaven do we even have a pre-production server if it isn't an exact mirror of production?
God help me, I need a drink. -
Holy shit the programming memes you are seeing are actually being used in production. What the fuck is going on3
-
We should teach people early on how to collaborate with others in a team atmosphere. It’s hard to get code into production on your own, and once it’s in production it’s not your code anymore, it’s everyone’s. Everyone should have a say.3
-
What's your workspace setup?
Curious because it took awhile and a lot of experimenting/thinking to get mine setup the way it is, but now I can't even think properly unless I have things setup that way after booting up in the morning.
Here goes:
Workspace 1: General stuff, personal email. social media, random research for non work related things, etc
Workspace 2: My main project local development, includes terminals, database, browser research for bugs, debugging software, error logs, etc.
Workspace 3: My main project, production workspace, consoles, browser, etc related to production server, you get the idea
Workspace 4: local dev on my side project
I found it crucial to setup workspace 2 and 3, it has helped me avoid countless stupid errors, like, for example, accidentally working on production terminal and wanting to rip my hair out wondering why the fuck _____ isn't working, then realizing, oh shit, i'm on production, not local. Huge brainspace bandwidth saver when I setup like this.
How about you?2 -
Why do people go on lunch break while we are in the middle of hotfixing on a production site?....13
-
Some idiot fixing bugs in production and overwriting files without updating his git repo when I pushed another bugfix live.
Boss to me: "it's your job to get the fix live!"
I FUCKING HATE MONDAYS!
screw performance i'm gonna run gulp.watch in production and just git reset it to last release when someone fiddles with files on the server :( -
When a major bug fixad recently by you reappears on production environment 'cause someone else (not you of course...) merged old branch content to live branch...
-
Any devs out there worked building Golang microservices for a production environment?
I don’t have a specific question really. Just wondering who is out there on a similar path!
I’m building using Golang, Google Cloud, Docker, Kunernetes, and Terraform currently on a personal product bound for production!1 -
My boss that push the code on production without versioning it.
I deleted all the changes, and the fault was mine, of course.1 -
!rant
If your manager does not add undue stress on you even if there is a bug in production, then probably you are working for the right company.3 -
I dont know which one is more frightening!
Having a bug on the first run or not having one until production...3 -
why does preg_split work on my local copy but not on production? WHY DOES IT RETURN LITERALLY NOTHING? IS PHP JUST HELL? AAAAAAAAA9
-
3 weeks ago
Client: when can we go in production, we want x and y
Boss: 13/12
Absolute Silence
Today 8/12
Boss: how long will it take for bringing this in production on 13/12?
Me: I'll do my best to get it ready on time
Boss: Why will it take 2 workdays?
Me: because client asks x and y
Boss: so?
Me: x and y is not ready
Boss: x and y can' t take two days, it must be ready now
Me: You said 13/12?
Boss: client wants to test before production
Me: ... 😡
Where did things go wrong here?7 -
It's been a month since I commented the password check for the login page on production... no one has complained...
-
It’s always fun when you are asked to push to production on a friday afternoon...Because the project managers and owners won’t have be the ones who have to fix something on a friday night or weekend 🤷♂️
-
Friday: Run your security test on production after hours.
Saturday: Wait, do development instead.
Today: Ya know, development is a critical environment too. Just don't test anything at all.
🙄 -
I had a fun one for one of myself but then I heard a "technical architect" at my company used the same login and password for a project's production and development databases.
I then had to deal with the crisis of a new dev on that project blowing the entire production database to smithereens because of said decision. -
When a designer walks into your office and asks you to turn on a feature that is not ready for production...1
-
Not sure how this made it to production..
Looks like Time Warner Cable updated their site to use rems with a replace all on 'px'.
https://registration.timewarnercable.com/... . -
Huh, I finally secured 15 years warranty on my life from god. He agreed on replacement for production defects only. It doesn't cover physical damages caused by me though.
-
docker is shit. It fills up the disk on its own whim and then crashes the server, and they claim it to be production ready. Stupid piece of software!4
-
Disconnected a production servers Ethernet adaptor ten minutes early. While people were working on it, and its failover was not quick...like five minutes not quick. Why isn't there a confirmation box on that Microsoft...2
-
When I tried to install Android x86 on a partition on my production machine, and by mistake installed it using GPT on my MBR machine.
I pulled 2 all nighters to fix that.
That was when I learned about GPT and MBR.
Fml.2 -
TFW you get to work and your colleague is like : "Hey boyo you got bugS to fix on that code we pushed into production"
As I was just having a better outlook on my life -
It’s a tie between every Ruby-On-Rails project I have ever seen that has been in production for more than a year...
So much goddamn magic -
Quick update on our partner's API that doesn't work (see previous rant).
They gave the wrong URL! Wow!! Well we have the new URL but
the production credentials don't work!!!2 -
Goverment just confirmed 2nd January as National holiday (work free day)...scheduled Nationwide production on 1st January, 2nd January for bug fixes (no holiday for me)
FML! -
Today is release day!
Got a whole set of new features to deploy on production!
Also, internet at the office has been dead since 6am.
I'll take a coffee break. -
Expanding a batch system on production
Set reservation to block the new nodes
Apply changes and restarted scheduler
(Reservation quietly lost, as it should persist)
Client called because jobs start to fail on new nodes…
Gahhhhhhh!!!!!! -
Reproduce production defect on local.... Apache ProxyPass for the redirection... Apache Crashes.... Fiddler to the rescue... fingers crossed.
-
Spent a couple of weeks on writing a cronjob which updates a certain value in the application config, and spend the last few months on testing it in different environments to make sure it does not fail in production. Ran the deployment script, and the damn cronjob fails because of ssl certificate on production. fuck me
-
My beautifull roomie asked me make a simple php page for her company . I did not sleep 3 days. The day it was released on production, it fucking didn't work. The reason: "the production Administrator didn't install the php server. I get no paid, my roomie is kinda mad at me.13
-
Hit into NullPointerException on production then I saw this in the source code,
entity.getKey().getValue().contains("a string"):2 -
That feeling when a new feature works on a local build, works on the development server, and works on the QA/UAT server, and then still breaks production when deployed.2
-
Currently debugging a project that was written over 4 years ago...
At first all was well in the world, besides the ever present issue off our goddamn legacy framework. This framework was written 7 years ago on top of an existing open source one, because the existing one was 'lacking some features' & 'did not feel right'.
Now those might be perfectly fine reasons to write a layer on top of a framework, but please, for all future devs sanities, write fucking documentation and maintain it if you're going to use said framework in all major projects!!
Anyhow back to the situation at hand, I'm getting familiar with the project, sighing at the use of our stupid legacy framework, attempting to recreate the reported bugs...
Turns out I can't, well I get other bugs & errors, but not the reported ones. I go to the production server, where I suddenly do can reproduce them...
Already thinking, fuck my life, and scared for the results... I try a 'git status' on the production server....
And yep, there it is, lo and behold, fucking changes on production, that are not in git, fuck you previous dev who worked on this and your stupid lazy ass modifcations on production!
Bleh, already feeling royally pissed, there's only 1 thing I can do, push changes back to git in a seperate branch, and pray I can merge them back in master on my dev environment without to much issues...
Only I first have to get our sysadmi. to allow pushing from a production server back to our git server...
Sigh, going to put on my headphones, retreat to my me space and try to sort out this shitpile now... -
What's better in general:
#1 master merge -> production
#2 master merge -> button -> production
And why?
At work we currently use #2 because sometimes we need to make manual changes or update images on prod before we can fully update the code
Edit: This should have been a 'question' not a joke/meme, sorry about that -
I was just going hit send on a slack message:
"Issue for this fix is deployed on production"
Just a few moments before I realised my goof up in the text😂1 -
What are you using for local environment? I'm stuck on xampp for 10 years. I realized that I'm having terrible pipeline from developing to production.6
-
Gahhhh.... This side project I have been working on for the past 3 months is basically finished. However, the production build of the project seems to be breaking a key read abstracion I built. God damm it.
Can't blame anyone but me, because I should have tested this on production months ago!! -
Just built tested and pushed to production a website based on an injoke. On a Friday. Why am I like this.
-
In the beginning I created a CLI script to manage some production tests of our embedded product. Then they wanted a GUI with a single textbox and button. Then they wanted a shortcut on the desktop to that GUI.
Now one guy I know in 'production' insists that I keep adding to the documentation for things outside the scope of the software and more towards what will be sent to other production workers. Some of which includes 'ensure the cables are plugged in'. He says that he and other production workers are dumb and need a bulletproof guide. Fair enough, I say...maybe get a brain also?1 -
It's extremely frustrating when a project is set up so that development, staging, and production reside on one branch.2
-
how many people in production support trying to learn programming on here? feels like having two jobs at once.
-
When you get paged by your company to help investigate and fix critical issue in production and don't get time to work on the hackathon.
-
actually it wasn't mine. But it affected me. So we had a project website on wordpress and wanted to rewrite the theme. everything went well to the Point of production. Site is fine locally, at testing and on stage. On production we still see old, a bit broken old version, but only on homepage. Wtf. Nothing helped. After couple of hours later we found out, that the admin was updating php version and he left html shot at production, which was taking over.
-
I once executed a rm -rf * on a production server. What was your most fckd up or fireable instance at job?2
-
Just heard someone saying it's bad security practise to have composer and git on production server for deployments.... did I miss the memo?1
-
Doing production release on Wednesday is kind of pointless. Someone is going to override the world a day after due to Last Thrusdayism - https://letmegooglethat.com//...1
-
If your code is giving HTTP 500 error on a production server, go kill yourself, until you are having a development environment on the production server. In that case, kill your manager! 💢
-
When one thing append ( girlfriend bios brick ).. all the shit append at the same time ( HDD badsector, production fuk up, migration that work on local not work on production, etc ) this week is shit jezzz4
-
I am wondering how phone operator company can make such thing go on production for live users? Seems like dev has used three times for loop when balance is checked 😐
-
Does anyone use file comparison software (Ex. Beyond Compare) on production server to deploy code?7
-
Who's on the serverless / AWS lambda train? Can you actually do something useful and production quality yet?5
-
Finally finished my 21h shift...Deploy on production is tomorrow...Back to the chair in a few hours.4
-
Deploys to Production.
Runtime error.
Open Development server and run in Production setting.
Still runtime error.
Fixes Error.
Error fixed on development.
while (hoursWasted < 3) {
Deploy.
Not working on Prod.
Try other fix.
Still not working, but works perfectly in dev machine.
What the fuck
}
Rage
Go take a walk
Realized I might have deployed to the wrong server
Glanced at deployment path
Realized it's at the wrong server
Reconfigure and Deploy
It works.
Fuck.1 -
How do I deal with this;
Edge case hiccup on production, no errors in the available logs(very shallow logging), no access to the production server, issue unreproducable on staging and a manager that want me to fix it AFTER I already said that im kind of sailing blind and can't do much without logs or access, and already looked at it with another dev who also has no idea what is going on3 -
I need to work on a mysql project for university but i know nothing about it,
Can you tell where is it deployed for production purpose, like mongo DB stuff can be deployed on heroku11 -
When you test on production server
"Your system folder path does not appear to be set correctly. Please open the following file and correct this: index.php"1 -
When you get the proper specs only after the current changes on the provided 'vague' spec sheet, that the stakeholders created, goes to production and it's not what they want...
-
I wish there is an open source alternative to forge or serverpilot. Not to use on production servers but for local development environment.
Yes, I'm not a command line person.4 -
this afternoon, we got email from our pentester. He said that he got some security vulnerability in our project. He found .git/ folder in project directory in production server. He considered it as security vulnerability because user can see all git branch on remote repo. He recommend us to remove that folder but the problem is, we using CI/CD so we need that .git/ folder. My question is it bad practice to use git on production server?10
-
some time ago on production I fund string join implementation using substring. No idea why it was implemented at all since this is in language standard library
Top Tags
Weekly Rant
View