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 - "uat"
-
Anyone else used Stack Overflow for many years without ever asking or answering a single question?21
-
My sister in law got me this guy for Christmas after I told her about devrant!
She found it in a rubber duck shop in Amsterdam.
Best sister in law!11 -
I've had my share of incompetent coworkers. In order of appearance:
1. A full stack dev. This one guy never, and I mean NEVER uses relationships in their tables. No indexing, no keys, nada. Couple of months later he was baffled why his page took ten seconds to load.
2. The same dev as (1). Requirement was to create some sort of "theme" feature for a web app. Hacked it by putting !important all over the place.
3. The same dev again. He creates several functions that if the data exists returns a view, and if it doesn't, "echo '0'". No, not return 0 or return false or anything, but fucking echo. This was PHP. If posted a rant about this a few months ago.
4. Same dev, has no idea what clean code is. No, not just reusable functions, he doesn't even get indenting right. Some functions have 4 spaces, some 2 tabs, some 6 tabs! And this is inside the same function. God wait until he tries Python...
5. Same dev now suggests that he become the PM. GM approves (very small company). Assigns me to travel to a client since they needed "technical assistance about the API". Was actually there to lead a UAT session.
Intermezzo, that guy went from fullstack dev to PM to sales (yes, one who calls clients to offer products) to business development, to product analyst in the span of two years.
After a year and a half there, I quit.
6. New company, a "QA engineer" who also assumes the role as the product owner. Does absolutely no tests other than "functional tests" in which he NEVER produces any form of documentation. Not even a set of test cases. He goes by "intuition".
7. Same guy as (6), hands me requirements for a feature. By "hands me" I mean he did that verbally. No spec documents, no slack chat, no Trello card. I ended up writing it as a card in Trello. Fast forward to the due date, he flips out because that wasn't what he wanted. Showed him the card. He walked away, without thinking of a solution how this mess should be handled.
Despite all this, I really don't want him (6&7) to leave the company. The devs get really stressed out at this job and he does make a really good person to laugh with/at. -
TLDR: Fuck you, Client A
1. Want to change the business flow during UAT and decide the deadline to be less than 4 weeks, even though that's how the business flow stated on the docs
2. He threatening us not to pay if it isn't done, even though he's not the one paying us
3. He said time isn't a problem because he can provide a table and chair that is put in front of his table
Fuck you, Client A12 -
A common scenario strikes again today:
- Blocked on a problem at the end of the day
- Tell my wife I'm headed home
- Inspiration strikes
- time flies by coding in the zone
- realize I'm super late
- run out the door like a crazy person1 -
Holy shit balls it works (so far)
-
So I’ve been working on a project... well feature for the past year (yes 12 whole fucking months - anti agile I know)
And today I got to merge that bitch of a pull request into the current working branch and deploy it to UAT - no conflicts 😵I think I need to put the lottery on tonight!
And some how, by some stupid lucky roll of the dice it just works.
I have never felt so afraid and delighted in my life!6 -
Night before flying internationally includes the following checklist:
- check VPN works, can access frontend sites and hit the backend
- git push4 -
This morning I kept falling back asleep after the alarm went off, drifting in and out of a dream about programming.
My wife finally said "no more sleeping".
Still mostly sleep, I replied very confidently "you can't sleep in a sandbox!".
I was dreaming I was in a code sandbox. Obviously sleeping is not allowed.
Jeez, my head has been really full of programming since this conference. (One of the talks was on codesandbox). -
Let me tell you a story.
Our company has a homegrown monitoring solution. Keeps track of our deployments and alerts us when something is broken. Really nice for the most part, except a little issue where we get up to 25 alerts PER DAY that our PRODUCTION ENVIRONMENT IS DOWN. Including weekends.
With this many false positives, we quickly learn to ignore the alerts and miss real incidents.
So we approached this team, remember its our own tool, and told them about the problem. Turns out it is a known issue. And here's the kicker: they aren't planning on fixing it!
It gets better. Rather than fix this glaring issue, their solution is to make ANOTHER ALERT that lets us know the monitoring is misbehaving.
To recap, we can now expect to get up to 25 false positive alerts per day that our production is down, followed immediately by more alerts that the monitor is broken, which means we can ignore the previous alert.
As our PM said when he heard this: fuck that noise. We are escalating the shit out of this!7 -
Every time I hear my boss say "surely it can't be that hard" or "that's what, like a 5 minute job?"
*shudder*3 -
I'm such an idiot.
Spilled water on my MacBook today. Not that much water, but the cup landed right in the middle of my keyboard.
Worst part is I was gaming with my sister and didn't want to stop. So I wiped it off and shook it out a bit and kept playing. A bit later the screen started flickering and eventually went black.
Finally my brain turned on and I switched it off, shook out some more water, and set it up to dry. Just hoping it's not too late.
At least the drying setup recommended by the internet is pretty hilarious looking.
Now we play the waiting game. They say 72 hours before turning it on again. Seems a bit extreme. Will there still be moisture evaporating 3 days later? Not sure I can wait that long to see if it's toast.
Such an idiot.14 -
*A group of college friends, discussing what is success*
Guy1: selection in national hockey team!
Guy2: having Audi, iPhone7, trip to UK every quarter and ...
Guy3: Running an own business!
*INNER ME: Reproducing a #BUG * 😌😎1 -
*spends a long time crafting a huge eBay post (we're moving)
* tries to drag and drop first picture
* page navigates to the picture without warning
* loses everything
WHYYYYYYYYYYYYYYY
WHEN DRAGGING A PICTURE INTO A WEB PAGE I NEVER WANT TO NAVIGATE TO A PAGE WITH JUST THAT IMAGE. WHY NO WARNING BEFORE LEAVING THE PAGE. WHY DON'T YOU SAVE TEXT LOCALLY. WHY DOES THE WEB SUCK SO HARD. AAAGGGHHHH.
* feels better
* starts over7 -
Netflix, why is your loading spinner so horrible!
Do you know what a percentage is??? 99% means you are ALMOST done. Just a tiny fraction to go. I should not see 99% for seconds or even minutes on end. Much less after the first 98% took only a couple seconds!!
Stop the lies!!!5 -
My new fitbit reminds me take 250 steps each hour. When I do stop and take a walk, I find it helps my productivity, and I feel better. However, I'm not good at keeping to it.
It's always the same story.
"Quiet you, I'll get up and walk once I finish this one thing".
...
Another hour goes by.
If only I could keep to my own convictions.4 -
I spent more than an hour trying trying to debug why two functions were always returning undefined. I even put in conditional breakpoints and executed the statements to confirm the logic was correct.
I forgot return.4 -
In a UAT meeting with representatives of our project partners,
The account executive, who set up the project, said to my PM in front of everyone just before the test started: "I hope your system won't fail, because everyone here will be watching"
My PM: "No it won't. But in that case, I believe it's your fault for setting an unrealistic deadline without consulting us, the development team, first"
All the representatives, being also developers from multiple companies, proceeded to stare at her with disgust.2 -
PM, on kickoff meeting: good code speaks for itself, need no documentation
PM, on UAT day: how does this features work, where is the documentation for it?
Dev: Just do me a favor and go fuck yourself.1 -
I think my productivity at work seriously went up when I discovered this site with custom noise generators. Blocks out my coworkers, and I can pretend it's raining all the time. Perfect for coding!
http://mynoise.net/NoiseMachines/...2 -
Coding has given me the ability to turn my favorite hobby into a career. This in turn gave me the chance to take jobs in three countries so far (US, Germany, UK). So, I can explore the world with lovely wife while doing something I'm really passionate about and constantly learning. It also allows me to relate more to my dad, a software engineer of about 30 years who got me started when I was a kid.
In short, coding changed everything for me.
PS: I met my wife in intro to CS, though she's not a developer. -
When your company buys a third party solution and you spend all your time emailing them about bugs in their system.
Seriously, I even sent you the exact line of the bug in your JavaScript with a suggested solution, and deployed a new stack with your latest (broken) fix so you can test out that solution. Then you email back saying it is fixed but it is clearly still broken. If I email you a fixed version of your file will you deploy it? OMG!1 -
Working in a bank, using MIcrosoft platform:
To open my email, I need to enter my password and sms OTP.
To open my email using phone, I need to enter my password and sms OTP.
To open Teams, I need to enter my password and sms OTP.
To open Teams using phone, I need to enter my password and sms OTP.
To access Microsoft Azure, I need to enter my password and sms OTP.
To git pull/push, I need to enter my sms OTP.
To check UAT logs, I need to enter my sms OTP.
To get access to UAT DB, I need to connect to VPN, which then asks for OTP.
Did I also mention that I need to do these OTPs every single fucking day?
#OTPDrivenDevelopment5 -
After being live multiple years supporting only Safari, Firefox, and Chrome, one customer wanted IE support. After taking a close look at the usage numbers, and discussing with us front-end devs, our product guy shot it down. Pop the champagne!2
-
Client: Each invoice should be it's entity. It should only report it's own open amount. Any other open amounts remain on the other invoices.
Me: No problem. ::Sets invoices to only report own open amount::
PM: Hey, the invoices in UAT are not displaying the sum of all open bills.
Me: I know. The client wants each invoice to only report the open amount on that specific invoice.
PM: That can't be right, change it back before we give the client access to the UAT environment.
Me: No problem. ::reverts invoice changes::
Client: We are failing the invoices. The invoices should not be giving total open amounts for the account. Each invoice should only report the open amount for that invoice. We told the development about this...
PM: I see. I'll make sure he understands your request.
Me: ... ::reverts the revert::
PM: Hey, the invoices in UAT aren't giving a total of the open-
Me: OMFG. I just want this task closed!
Client: After the invoice work is done, we need to talk about past due amounts and how they are reported to customers.
PM: Sure thing. It is logical to give a total of a past due amount to the customer...
Me: ::Starts updating resume:: -
Me: Im testing a new feature that is not on production yet for 30m and can not make it work. (I asked the developer for any idea why is not working)
Dev: i just tested, works fine.
Me: i just tested again with no luck. I’m i missing anything?
Dev: (Developer comes to my desk). Lets see what you doing wrong here. (After 5seconds). You're not on UAT. You have been redirected to the production and you've been testing there all this time.
Me: 😩 -
That moment your reading devRant while waiting for a UAT environment to build for the 3rd time in one afternoon.
-
Gotta love product owners that don't seem to understand agile.
We delivered the set number of items in the sprint we committed to plus a little extra polish. During the last day of the sprint we're spending the time to push all our work to UAT do he can actually perform acceptance testing...
He decides he should chase all of us up on stuff that we never commited to or even mentioned we'd touch.
Had to explain it to him at least 5 times during the day.3 -
These days are the best days of my life, up till now.
My best friend said yes to my proposal, I got a job at my dream company with higher payment, and no issue at all after my uat like last month.
I hope my codes doesn't ruined my day 😂😂😂2 -
Major state insurance provider, all past and current members data stored unencrypted (including SSN, date of birth, home address, etc.). All developers and contract developers had read access to it. Reported it, nothing was done. Reported it again in my exit interview. Was basically told they had intrusion detection systems in place so it was not an issue.4
-
When our company (past employer) got acquired by another company and everyone got to have a meeting where you got a black or blue envelope. One indicated you were being let go, the other indicated you were being offered an "opportunity" if you would relocate to NJ. What was an awesome company -- they destroyed the soul of it in one day.
Oh well their CEO got let go after a US Congressional investigation earlier this year. Karma, bitch! -
When you make a mistake and try to fix it, but you can't remember how to spell amend...
git commit --ammend
error: unknown command `amend'
git commit -ammend
[branch-name] mend
Huh?
git log
commit #
mend
Created a new commit with message 'mend'. Now to clean this all up and go get some sleep!2 -
i asked my senior "why we need a develop branch" and his reply was "-_-" , literally an emoji.
Ok ,well this might be a stupid question, but i have been in this organisation for 6 months and all this time these guys have not been able to make a proper release. either they miss commits while cherry picking, or they end up reverting stuff, or they are delaying the releases due to QA disapprovals, backend issues or management issues.
i proposed a simpler vcs :
1. `uat` is the source of truth
2. for every release we create a temporary branch `release-x.y.z` from `uat`
3. then we develop every feature in a branch cut from `uat` as `feat-abc`, code in it , and merge it back to `release-x.y.z`
4. finally we merge `release-x.y.z` into `uat`
where is develop branch supposed to be cut?
which branch is supposed to be cut from develop?
which branch is supposed to merge into develop?
where is develop supposed to be merged?
no one has answers to these fucking questions. but still they wanna confuse the whole team of 15+ android and ios devs about how to use which procedure
fml :/10 -
Code is sat in UAT for a month and no one looks at it. Two days before the (completely arbitrary) go live date and testing commences, finding one bug which is immediately fixed. And now I'm the one allegedly delaying roll-out. Err OK...1
-
You know how my 'about' here says I create features from bugs?!? Well if you didn't before, now you do.. :P
Anyhow, today the most bizzare thing happened.. Customer played 'reverse uno card' on me..
Meaning?!
They reported a feature missing on uat env, when in fact I fixed a bug they have on prod..
Not sure how I should feel about this, but it sure made my day! (: I just hope they will not open a bug report for this missing bug..4 -
!rant
Super awesome day today.
1. Got up early to do a risky production deploy and it worked!
2. Three PRs approved before lunch.
3. Got some time to continue learning scala.
4. Coffee and cupcakes with some refugees and discussed work as a software engineer.
5. Tried virtual reality for the first time. Really fun.
6. Helped prepare our goals for this quarter and present them to the department.
7. Department meeting had free local craft beer and pretzels.
8. Went bouldering after work and flashed a 6c.
9. Curled up with my wife watching Netflix.
I really love my life sometimes.5 -
Years ago, one of my friends in college was taking an intro to CS class. He asked me for help on one of his assignments. It was a simple Python program, but it wasn't running as expected. I go in figuring it will be easy to fix. But everything looks exactly right. An hour later I'm tearing my hair out! It isn't even entering the function although it's clearly called. I'm beginning to feel very self conscious, as a CS major who can't even debug a 15 line program for a friend.
Then it hit me. This is Python. I used an editor macro to convert all indentation to tabs, lined them up, and it ran on the first try. Turns out, he had somehow ended up with a mixture of tabs and spaces.
I'm not sure what the takeaway is, but I think he got a surprisingly honest introduction to the life of a developer...2 -
PSA: negate your tests and make sure they fail!
I have what I thought was a weird and slightly paranoid habit. When I write tests sometimes just as a sanity check negate the assertion to make sure the test fails and isn't a false positive. Almost always fails as expected.
But not today! Turns out I had forgotten to wrap my equality check in an assertion so it would always pass. It freaks me out to imagine pushing a test that always passes not just because it doesn't do its job, but could also obscure a bug and trick me into thinking it works differently than it does. Broken tests are the worst!
But it pays to be paranoid. -
Me: *adds a shiny new graph to our foos web app showing player ratings*
Fred: Can I please have a button to see just my scores?
Me: *adds "JUST FRED" button*
Fred: perfect, thanks4 -
Problem:
some folks left the angular codebase full of ridicolous console.logs, client was upset as he noticed it during UAT
Solution:
1. add extra script in main template page
window.console.log = function(){};
2. translate it into JSFuck
3. if they ask, pretend it's a super-secret encryption algorithm to improve security6 -
So we just had our GitLab moment... Some dev ran a script that is nuking our db as I speak...
At least it was uat but... fck all that data has to be restored from somewhere..... By someone....4 -
The marketing dept comes to me and ask for an important project to be done ASAP. Builds pressure on my PM to get it done fast. After I complete it, I ask them to complete UAT to make sure it is what they wanted so we can go live. They seem to not have enough time to test it. After one month the whole dept gets divested! Is this common or I am unlucky? They never used that very important app ever!!😢😠2
-
I'm genuinely shocked at the number of people I see on here bashing automated testing as a waste of time, simply because my entire career has taught me the opposite (and it's usually only non-technical managers I see who don't want to see "time wasted" writing tests.)
I'm also just as genuinely curious - what do you guys do instead? Just don't test and deal with production issues as they occur? Pass it off to a separate UAT / human-based testing department and let them sign it off? Assume that because you're using Haskell / some other discipline it'll work if it compiles?14 -
It works locally, it works in Dev, it works in Test, but fails to deploy in UAT. Is it a data issue? I don't know, I don't have permissions to see the UAT database. Literally all I know is that this API is returning 500 instead of what it's supposed to return, but only sometimes.
Guess I'll sit here all day and try to solve the problem telepathically as there is literally no way of troubleshooting other than scrolling through the code and hoping that a cartoon lightbulb appears above my head.2 -
I get home today and my wife says:
"Just finished some chores and really want to play stardew valley, but the computer has been updating for an hour!"
Windows 10 anniversary update strikes again.3 -
When you offer to help out a fellow coworker on the top priority feature he is developing and he just sends you the branch and stops working on it.undefined one way to avoid merge conflicts paired programming would be more efficient welp guess it's mine now happy to help2
-
Wouldn't say our teamwork failed we just sucked that day.
I had a ticket to fix a SQL sp and then correct some data afterwards. As this was the typical "urgent fix need now" we went through a different process for fixing it.
Me: Just sent you some scripts can you check them over before we apply it to uat?
Boss: let's go through it together.
5 mins later
Boss: looks fine I'll apply the scripts.
2 minutes later
Me: did you apply the scripts to uat?
Boss: No I applied them to live.
Me: oh ... oh no.
At this point I realized I was missing a critical where clause so yup my update was applied against all of the data.
Boss: oh
Yup he just spotted my error.
Helpdesk phones start ringing
Boss: you pick it up it's your code
Me: hey you applied its your problem now.
One db restore and several incident meetings later we fixed it. Twas a fun day.1 -
somewhere in this world this happened..
Company lands huge enterprise project
manager: we have a year to get this done.
poor devs : excited and thinks about so much learning with this project it would be.
manager: Lets get work started with (spits planless jargons)...meanwhile another team is working on SRS.
poor devs: So we are doing R&D right..(excited)
manager: No we have a demo scheduled after 15days.
poor devs: What??
manager: Get on it..we need something to show on demo.
poor devs: no words spoken
...after one year of unplanned demos...
manager: we have to stablize project..UAT is nearing.
one of brave poor devs: No no..lets focus on demo...why do you need a stable product.
manager: instant rage1 -
So it's officially a month into my new job...
I have to say, sometimes life can surprise you, I never expected things to go down so smoothly especially after getting fired from my previous one.
My manager is just an amazing super friendly guy, great colleagues with positive attitudes, positive work environment, better benefits, the list goes on...
Honestly I would say the biggest con is I now work 45hrs/week instead of 35, which might be a dealbreaker for some but I also work in the cloud industry which is honestly miles ahead than the UAT testing crap I used to do, plus the company pays for your certifications after you pass, so it's a small price to pay imo.
If any of you are struggling with a shitty job/work environment don't give up, out of all the places I worked at I never felt appreciated until I came here, keep on grinding.9 -
Wow or wtf to these banks API. was integrating an API for a service which accept JSON input.
Okay fair enough, that would be fine
Spent an hour writing code(purescript) most of time spent was on writing Types based on the API doc. after that okay let me test the API it failed.
I was what happened? So tested the API from postman with the payload from the doc, it worked. What how?
used a JSON diff to compare the payload from postman and the log. Looked same to me after spending few hours checking what is wrong with it .trying changing value to pasting the body of the log request in postman and trying everything failed.
Later went to the original working payload provided by them and changing the order. It started throwing error. I was like wait what?
It must be only on there UAT. created a payload with production creds and hoping to our production server (they have IP whitelist) ran the curl with proper payload as expected it worked. Later for same payload changed the order or one key and tried it failed.
Just why????
I don't want to create a JSON with keys on specific order. Also it's not even sorted order.4 -
So we called out our project manager and tech leader, who sent out an email last Friday to our bosses and stakeholders a project schedule - which we never knew about until we saw it in our inboxes - that showed we had already completed development and would go on to UAT testing by next week.
Except if you look at our agile board we have 3 weeks of dev tasks left and a couple more for testing and QA. Then our dev environment is shit because the deployment steps in TeamCity were not properly done by Dev Ops. And we still don't have a UAT environment created, much less tested out. And the project manager is about to go on a one-month vacation. Great!
So we replied back with all the aforementioned information (less the swearing and name-calling) and sent it out to the same recipients, including our bosses and stakeholders.
That was such a fun Friday afternoon. -
A little background on project fubar:
Project fubar was started a couple of years ago, by an entirely different set of devs, against an entirely different set of requirements which were never made transparent to this day, on a new platform and framework.
That means it had APIs either outdated or deprecated, front-end logic that did things it wasn't supposed to be doing and lots of scope creep and technical debt.
I had to support and fix fubar for the last few months to prime it for UAT. It was the equivalent of plugging leaks which created more leaks.
Finally, I couldn't take it and asked for a week off. I timed it so it would be right after what would have been the final UAT deployment and I'd be back after they completed their test rounds, so I could fix any new or returning defects.
Today I just found out that fubar got put on hold, that UAT was a failure and all fubar-related work had to stop. I have some mixed feelings on this: I worked hard to get fubar working as business wanted, and I was proud of that. But I also didn't like that fubar was constantly changing in scope and function.
I wonder if anyone else has ever felt the same thing?2 -
We've been using private GitHub repos as a distribution method for our personal npm packages at work for years.
I finally got sick of it and did the work to publish them to artifactory yesterday. Today, I worked out the remaining kinks, fixed the CI builds, and wrote a wiki page explaining the change with step by step migration instructions and sent it around to the rest of the devs. And it's working great!
I feel simultaneously like a hero for finally getting this fixed and an idiot for putting up with it for so long.
Also thankful for my devops friend who helped a bunch.1 -
When your coworker is having issues with an old ColdFusion app, and says "Nevermind, I am just going to rewrite this in ASP". Yes, he is writing a "new" app in Classic ASP. 😒2
-
I work for an investment wank. Worked for a few. The classic setup - it's like something out of a museum, and they HATE engineers. You are only of value if work on the trade floor close to the money.
They treat software engineering like it's data entry. For the local roles they demand x number of years experience, but almost all roles are outsourced, and they take literally ANYONE the agency offers. Most of them can't even write a for loop. They don't know what recursion is.
If you put in a tech test, the agency cries to a PMO, who calls you a bully, and hires the clueless intern. An intern or two is great, if they have passion, but you don't want a whole department staffed by interns, especially ones who make clear they only took this job for the money. Literally takes 100 people to change a lightbulb. More meetings and bullshit than development.
The Head of Engineering worked with Cobol, can't write code, has no idea what anyone does, hates Agile, hates JIRA. Clueless, bitter, insecure dinosaur. In no position to know who to hire or what developers should be doing. Randomly deletes tickets and epics from JIRA in spite, then screams about deadlines.
Testing is the same in all 3 environments - Dev, SIT, and UAT. They have literally deployment instructions they run in all 3 - that is their "testing". The Head of Engineering doesn't believe test automation is possible.
They literally don't have architects. Literally no form of technical leadership whatsoever. Just screaming PMOs and lots of intern devs.
PMO full of lots of BAs refuses to use JIRA. Doesn't think it is its job to talk to the clients. Does nothing really except demands 2 hour phone calls every day which ALL developers and testers must attend to get shouted at. No screenshare. Just pure chaos. No system. Not Agile. Not Waterfall. Just spam the shit out of you, literally 2,000 emails a day, then scream if one task was missed.
Developers, PMO, everyone spends ALL day in Zoom. Zoom call after call. Almost no code is ever written. Whatever code is written is so bad. No design patterns. Hardcoded to death. Then when a new feature comes in that should take the day, it takes these unskilled devs 6 months, with PMO screaming like a banshee, demanding literally 12 hours days and weekends.
Everything on spreadsheets. Every JIRA ticket is copy pasted to Excel and emailed around, though Excel can do this.
The DevOps team doesn't know how to use Jenkins or GitHub.
You are not allowed to use NoSQL database because it is high risk.2 -
A conversation that i had with my co-worker today. I was having trouble getting into UAT to troubleshoot.
me
i lost access to UAT again
co-worker
F. So secure we can't even get in
me:
lol
co-worker:
I'll email whoever we did last
me:
i can get through the first phase(where you enter pin+rsa)
it denies me access after that
says bad username or password
co-worker:
Oh ok. Prolly just need to reset your pwd then. I'll find the email for helpdesk and fwd.
At least ur RSA works.
me:
yeah what a joy
co-worker:
If it's locked you may need to try from a Windows box. Horizon is bugged on Mac where the submit button stays disabled even when you type a pwd.
me:
i couldnt contain my happiness that my RSA worked
😃
co-worker:
Yeah it's exhilarating
Whenever I pick up my rsa token my life re-finds it's purpose and I feel like I'm meddling through a field of sunflowers.
I once tried to get my RSA token tattooed but it switched too quick.
me:
lol its faster that Usain Bolt
co worker:
Russia got kicked out because of their RSA tokens -
I want to buy a beer for everyone who developed the mobile pass app. Just breezed through immigration and customs without waiting in the 1 hour+ line. Technology wins. Cheers!1
-
Live deployment next week Monday but Product Owner really need this new fix in.
Can you code, push to test, test it, push to acceptance test, UAT it before Friday...
It's Wednesday today 😐
Project manager says ok 😱1 -
Originally wanted to get a head start on work since gonna be out Monday... And don't want to be distracted while working on it... But UAT db was down.
So spent all morning working on side projects like a password manager because we're not allowed to use keepass...2 -
We take over development of a live customer facing system and PM agrees date for our first code deployment with client CIO
Me: The dev and staging environments don't have any test data currently as the old agency screwed it up
PM: Well you better load some
Me: There isn't any... It'll take 10 days to copy prod db due to hosting provider SLAs, leaving 1 week for SIT, UAT and performance testing (assuming they don't screw up)
PM: Well the date is set, 1 week will be enough for testing2 -
Dev: *completes tasks, pushes to UAT and assigns to PM in Jira for testing*
PM: *receives notifications and immediately bulk change on all taks and assigns to client without testing*
So what is it you do here...?5 -
I had an interesting mystery the other day. I work in the UK, but I'm working remotely from the US for a while. First day, I made some changes, ran the tests and they failed. Weird part was the failing test was for a component I hadn't touched. I took a closer look, and realized it was a date off by several hours. The test was checking that a passed in date appears in the output. But it was creating the date by parsing a string. The library I was using defaults to local time, but the component uses UTC. So, I had inadvertently created a unit test that only passes when run from UTC. But I had never noticed before because my work is in that timezone. Yikes!
-
Users have use cases, test cases, user manual etc documented material with them at the time of UAT.
But in the end users do only those things which they don't suppose to do..!! 😑😥1 -
It kills me when people performing UAT do not know how to test a particular functionality but still mark it as a defect when something uneven happens! We use IMF to build the input using tags. Sometimes they won't even care to know the right tag to fit in the params, but would still mark it as a bug whatsoever!
-
Just happened today!
So since this morning we've been trying to get our website ready for UAT deployment Monday next week, even though we only were told of it yesterday. Since we had some critical merge conflicts to unscrew on our dev branch for promoting to UAT, we sent a warning to everyone on our hipchat group
Dev team: @all please don't commit anything to the repo for an hour or so while we get the branch good for dev and uat build
Tech lead: ok
That should be enough warning, right? Surely our tech lead, who has been piling up our scope creep trying to please our stakeholders, understands well enough not to do a single goddamn thing on our repo until we sort it out, right?
Nope.
10 minutes later our tech lead pushes several changes that not only break our builds but also remove all our configuration transformations. I just stormed out of the office to avoid sending her on a one-way ticket to slapsville and fuckyoutown. Geez goddamn louise. -
Coworker has been working as a web developer at our company for 10 years... Yesterday I see him watching this video intently: https://youtu.be/PLA2FaOXkkg ?4
-
Just moved countries and started a new job at an awesome company, which is so great I have nothing yet to rant about.
Oh here goes: almost three weeks with no internet at home and no end in sight.2 -
Things you should not say on your last day of work:
If I broke it, I think it would be pretty obvious. -
Asked if I'll meet a July 15 deployment date for a payroll app that has been out in UAT since Jun 27th with no comments (6 working days and 2weekends)
Me "Well I smoke tested it and it worked but if I get a 20 item correction(/enhancement) list on the 12th from the customer rep again, then I won't"
m
Team Lead: "I'll try to play with (test) it some today"
Me :)2 -
Just attended my first conference and it was awesome! So many new ideas, but also tired and overloaded. Can't decide if I should code tonight, go to bed early, or just do something mindless.1
-
Two steps from UAT being done:
Product owner: "Oh yeah, one more thing."
My brain: "You gotta be shitting me!" -
Manager: calls me on Wednesday and asks that have you moved your changes to UAT on Monday?, the client wanted to test it.
Me: Started looking for a new job immediately. -
Why is so Fitbit so bad at multiple time zones??
Guess what, people get on planes and travel.
Every time, my Fitbit gets so screwed up, including things like changing previous step counts, or duplicating an entire day of steps.
I understand MTZ is a tough problem, but this is just unacceptable. I'm not obsessed with my steps, but when your product is all about counting something, seems like you should be more careful to avoid double counting or not counting at all. Seriously, how much R&D have they invested in their hardware and apps, but it completely fails when you travel. Get it together!1 -
Got a new devops "manger" today we had an argument for 20 mins about why Staging/UAT was needed and why we could not just by pass it and get to prod quicker .. WHAT?! I am dumbfounded I do not have words to express the emotions I am having right now.2
-
[Conference Call on Project Launch]
🤡: we just came up with an extra list of features to add to the system
🙊: but we just finished the system and it is ready on UAT server to sign off
🤡: we want these features, they are essential for a better backend admin experience
🤡: and we have been working on this project for almost a year!! we need these features and launch now!
🙊: (well, it took you guys six months to sign off on the initial graphics designs...) can we first launch what we have on UAT site first as they have been sitting here waiting for your approval
🤡: ok. i will test them and provide feedback. if it’s all good, then you can launch it.
🙊: ok. we will do another set of UAT after launch for your new features.
🤡: ok. i will let you know when we can launch the current UAT.
[Two weeks later]
🤡: #%^#*+!! why are the new features not on the UAT site yet!! why are there no changes after two week!! we cannot accept more delays! really need to launch asap!
🙈: 🖕🏽2 -
Other dev in group chat: we need to stop syncing so much data from prod to uat because it's crashing the uat db...
Me thinking: no really... U just realized it's not a good idea to dump most of the prod db into uat every week?
¯\_(ツ)_/¯4 -
When someone cooks bacon in the break room early in the morning and doesn't bring enough for everyone. #hungrydeveloper1
-
So I started a new job back in April with a the developer on a government project being developed by a reputable international organization, lets call them R. Once the project reaches a an acceptable release stage, maintenance, changes and integration into the eco system falls to me. This project started about 3 years ago and the original team from R was "changed" because they claimed the product was ready for go live when it wasn't.
My job since then has mostly been analyst and QA work identifying issues with conversations like this:
Me to Client: I don't think this feature is working as it should be.
Client: You're right.
R.dev: This feature is working according to signed off SRS and assumptions register.
Client: Yes but the SRS and assumptions are wrong.
Me: Facepalms. Oh this other feature isn't working correctly either, this should generate A according to SRS but I'm getting G.
R.dev: Yes but that would take a major change to the system.
Me: [Blank stare]
R.dev: Ok, we can give you E.
Client: OK we corrected the errors in the SRS and the assumptions register we've signed off on this, please use these going forward.
R.dev: OK we reviewed and made changes.
Client: Um, these are wrong the calculations are off.
R.dev: We did it according to your SRS and assumptions register.
Client: Oh, wait, these formulas are wrong.
Me & R.dev: [Blank stares furiously]
Client: The sponsor won't pay the next stage until you reach an acceptable release. Fix these critical issues and we can worry about the rest in support.
R.dev: ... OK, we will deliver by X date.
[7 Days to delivery of changes]
R.dev: We postponed development till (deliveryDate + 8) when we meet with the sponsor.
Me: But that's when we should start the next UAT for go live for the New Year...
I left a management job for this so I could code more. 180 issues later I still haven't seen the source code... fml
Silver Lining: Still gettin' paid though -
I was always interested in computers. My dad was a big computer geek and a programmer to boot. Usually had a couple old PCs in the basement to play with.
In middle school, I took tech ed and we made simple web sites with html and css. I remember the struggle of nested tables.
In high school, I couldn't fit any CS into my schedule. But someone gave me a learning to code book in ruby. I loved it, and have been hooked ever since. -
Best tip for getting unstuck? If it's after your usual leaving time, GO HOME.
So many times I solved the problem right away the next morning. Only wish I followed my own advice more often... -
So yesterday at a client location, our support guy called me and said this thing is trimming the characters whenever I save it. It was a ckeditor in our application, so basic troubleshooting was to check the system configuration for that page and the ckeditor configuration.
Checked the system configuration, ckeditor configuration, found nothing.
Out of curiosity, checked the schema for the table in which the data is stored, so one of the idiots took the backup of original table and appended it with the date time on which it was backed up. And created a new table with field data type of varchar with a 255 limit.
This was in UAT server as well as Production server. Changed the field type to text again in UAT. Asked to team to get the same thing done on Production server as well. -
It drives me crazy when there are unclosed parens or quotes anywhere.
Is it too much to ask for people to run their Facebook posts through a compiler first? -
When everyone thinks FE is easier, quicker, and less important than BE. Just because our fantastic UX people made you a high fidelity mockup in a day does not mean we can build the whole FE in a week.
This is why I'm returning to full stack. -
Computer does a BSOD right at the end of a tiebreaker competitive overwatch match where the enemy is about to cap the point and win. I'm one of the tanks. Hard reboot and back in the game within 45s. Just barely hold them off in overtime and win the match. Epic!
Thank God for SSDs!4 -
So my multithreading optimization is now in UAT.... it looks like it's working and not crashing....
It seems it's also 50%... aka saves 1hr...
I'm having a rare moment when I actually feel good about and actually did something at my job... -
Current Mac and Windows user here looking to get back into Linux. Any distro suggestions?
Looking for something not too high maintenance.7 -
It is so frustrating working in a pure waterfall environment. My current work is constantly interrupted by QA and UAT defects. Many of which have nothing to do with my code. But they still require me to stop what I'm doing and research what happened. It's 2:43 and after meetings and research I haven't written a line of code on my current project. Ugh!
-
Started working for a new company as a data lead, created a couple of basic lambda functions for a pipeline... 5 approvals and three weeks later the functions haven't even been pushed to UAT (which I'm not allowed access to).. Have I been lucky before or is this dysfunctional..?
-
Any recommendations for moving a blog?
My wife and I just cancelled our account with siteground hosting a WordPress blog. Looking for a cheaper alternative. Willing to get my hands dirty as a web dev, but would like a nice CMS experience for my wife. Also want to keep our existing content. If we can keep our custom domain somehow that would be a win.
Thanks!7 -
In our company, "UAT".
We using staging environment and most of the data is either missing or corrupt. They don't refresh the data, saying it can impose some security issue.
How the hell are we supposed to complete UAT when there's no data that's in production!!!! -
Just joined a new company and can only describe the merge process as madness.....is it or am I the one that is mad?!
They have the following branches:
UAT#_Development branch
UAT#_Branch (this kicks of a build to a machine named UAT#)
Each developer has a branch with the # being a number 1 to 6 except 5 which has been reserved for UAT_Testing branch.
They are working on a massive monolith (73 projects), it has direct references to projects with no nuget packages. To build the solution requires building other solutions in a particular order, in short a total fucking mess.
Developer workflow:
Branch from master with a feature or hotfix branch
Make commits to said branch and test manually as there are no automated tests
Push the commits to their UAT#_Development branch, this branch isn't recreated each time and may have differences to all the other UAT#_Development branches.
Once happy create a pull request to merge from UAT#_Development to UAT#_Branch you can approve your own pull request, this kicks off a build and pushes it to a server that is named UAT#.
Developer reviews changes on the UAT# server.
QA team create a UAT/year/month/day branch. Then tell developers to merge their UAT#_branch branches in to the previously created branch, this has to be done in order and that is done through a flurry of emails.
Once all merges are in it then gets pushed to a UAT_Testing branch which kicks off a build, again not a single automated test, and is manually tested by the QA team. If happy they create a release branch named Release/year/month/day and push the changes into it.
A pull request from the release branch is then made to pre-live environment where upon merge a build is kicked off. If that passes testing then a pull request to live is created and the code goes out into production.
Ahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh it's a total mess. I knew when I took on this job it would be a challenge but nothing has prepped me for the scale of the challenge!! My last place it was trunk based development, commit straight to master, build kicks off with automated testing and that just gets pushed through each of the environments, so easy, so simple!
They tell me this all came about because they previously used EntityFramework EDMX models for the database and it caused merge hell.9 -
evaluating whether i should make it more agile and flexible or just get it slapped into production. always waging war in between proper developer testing vs my own uat testing (of which we as devlopers also need to do)
-
this whole conversation is 4 hours before a UAT deploy.
PM: Do we have the new keys?
me: did they devs give you the new keys?
PM: no. what about the new URLs?
me: what are the new URLs.
she walks away. -
The only thing worse than client QA is client vendor QA.
I do QA for a company that does custom implementations of a major e-commerce platform. On one of my current projects, the customer has elected to outsource their UAT, and isn't willing to wait for the site (or even individual features) to be complete before starting testing, so I've been triaging a lot of silly tickets. But today took the cake.
This system allows users to save their credit card info. The vendor QA guy filed a ticket "reporting" that if he saved a cc with a given number, then created a new cc record with the same number but a different expiration date, the original record was overwritten, rather than a new record being created.
I just stared at the thing for like five minutes, gathering the mental strength to reply with something other than "you're an idiot."3 -
I have 3 jobs but one salary... I look after some financial enterprise system as one of my jobs ... In short am an integration support specialist, earlier today system was down ussd gateway... Some client pinged me on fucking skype asking for integration support on uat i ignored cause i was busy fixing production issues , the nigga escalated me to the CTio, sneakey bastard.. Some clients are shitty. Hope they make money
-
The end of today was hell...
Another company make changes to UAT for one part of the application and refuse to use VCS. This means we have to manually merge there changes in regularly. The developer in charge of this project left a few weeks ago and when someone new to the setup decided to pickup a task to re merge they accidentally did the scp command the wrong way around...
I probably don't need to say much more but we received MANY angry email and calls.1 -
Trying to add money to a prepaid SIM card today. Their website is a mess. Plus and minus buttons were not functioning, so my only option was to add 15 euro. Checked the console, no errors. Tried triggering the buttons jQuery, no luck. Found a data value attached to the submit button set to 15. Changed to 10, clicked submit, and BOOM, it worked! You just got engineered!
After I paid, I was curious, went back and set it to -15, and tried it again. Unfortunately, they know about backend validation. -
Just spent the better part of my day making our QA environment work and look like our CAT/UAT environment for a website and supporting web services that was built to look like 1998 puked on it. Wrong way people. Other Devs skipped QA due to external reasons (admittedly I was one) and never kept it updated... Everything from database comparisons to IIS configurations needed to be redone.
-
Vague requirement for feature A received from client
Business consultant refines
Example mapping done
Acceptance criteria defined
Scheduled in sprint
Development done
Unit tests passed
Pull request reviewed
Code merged and deployed to system test
Functional testing successful
Deployed to UAT
Client asked to sign off
Client: "Actually I don't want that feature." -
Just happened 5 mins ago:
Customer: "Can we run through one round on our side first before UAT?"
Somebody forget what UAT means..1 -
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
-
Hello, my first time here. I got to know this website/app from my PM because I need to vent it somewhere other than him according to my PM.
So, here goes my first rant. The date is today (Monday). The rant subject is our new tester. Some context on the guy. He started in our office 8 weeks ago and his title is senior tester with some years in testing. Me and my team with the exception of our PM are new hires and for me, this is my first job after graduation.
After a grueling month of pushing for new modules and bug fixes from our monthly UAT from the client (yes, this will be a future rant one day), about 2/3 of the team is on vacation paired with a long weekend. So, a very few ppl in the team including me and my PM came for today.
I usually came quite early, around 8 am as I commute with public transportation. As soon as I have my breakfast and just getting ready to open my dev laptop, he came to me with a bug. This is like under an hour I came to office. I'm ok with anything related to the project as today was deployment day to test server for our monthly UAT. So, I check the bug and it wasn't my module but the PIC is not there and I familiar with the code thus I fixing the module.
Then, not even 15 mins later, while fixing this module, he came to me with another bug. I'm still the only one who in office that can fix it thus have to do it too. Finished the both bugs, pushed and je retested it. Fortunately, my PM and another colleague came. But, for some reason, he only comes to me for the bug fixes.
The annoying thing for me is that he comes to me every time he found an obstacle, bug or glitch. At this rate, by hourly. Thus, this cycle of impromptu going around fixing-on-the-go for the project begins, for me. Then, my PM asks him abt our past issue log given by the client UAT. Another annoying part is he never checks the clients feedback to see if the result can be produced again. The time he checks it is when ppl ask abt it and test it 1 by 1. Then he came to me again with why x person marked it as done. Like hell I know why they marked it done, you the one who need to check with them. Thus, I called/messaged the PIC for x modules abt the issue and then they explain it. I have to explain it again to him abt it and then he makes the summary report for the feedback. This goes until lunch.
I thought the bug fixes is over and I can deploy it after lunch. I thought wrong and I kinda regret coming back early from lunch which I thought I can rest for a while with the debacle over morning. Nope, straight he comes to me after I sit down for 10 mins and until almost work hour is done, he came to me with small bugs and issues like previously, hourly. By then I think I crushed like ~10 bugs/issues and I'm knackered. I complained to the PM many times and the PM also said to him many times but he still does it again and again. Even the PM also ranted to me abt his behavior. The attitude of not compiling an issue log for the day and not testing the system to verify what the client feedbacks are valid or not is grinding my gears more and more. Not hating the guy even though his personality is quite unique but this is totally grinding ppl's gears atm. As of now, it's midnight and I finally deployed the system to the testing server. This totally drains my mental health and it's just Monday. May god have mercy on me.
Owh, the other colleague that come today? He was doing pretty much the same thing but he was resolving a major issue which is why the tester came to me.2 -
I walk by our devops dashboard several times per day. It keeps track of key metrics for all our live services. I noticed an interesting trend the last few weeks.
3 weeks ago: all metrics green
2 weeks ago: 1 metric red
1 week ago: 1 metric still red
this week: 1 metric still red but covered with a post it note -
so management implements SDLC. finally. but here is the snag... none of the environments are setup for any developer , integration or uat testing. now all the while business keeps pushing changes knto us and making us try work miracles. anyone else have this hell of communication from the high holy management above not listening to developers concerns ?
-
I work in a small team. As the senior dev I tens to focus on important tasks that shape the core of the product but some times I can’t divide my self when there are multiple tasks at hand, so I pass some tasks to the an other mid level dev.
So the task was to create an automation in order to CD (continuously deliver) an order from WHMCS of the (git versioned) product to customers UAT, PROD envs.
To get a background this is an old guy with “constricted” experience in PHP/jQuery/Joomla/Wordpress.
So when we were breaking up the tasks he told me he would like to implement this so i gave him the task as i was busy with core features.
I was like what could go wrong? I know he doesn’t know much about CI/CD but he can read right? He will google right? He will search for CI/CD solutions that do this out of the box right? He will design on paper or what ever and do small POCs right? He will design the flow first before starting the implementation right? RIGHT?
So fast forward to today I had a call with him this morning about some DB staff. And he wanted to show me his progress…
His solution is:
(parentheses is my brain)
1. Customer completes WHMCS order (perfect)
2. Web Hook 🪝 action (YES)
3. cpanel gets source and “automatic!” Init, all using pure PHP code ignoring the usage of the current framework (ok… something is missing)
4. cpanel web hooks(?) WHMCS to send email to customer with the envs initial setup page(?)
5. Customer opens link and adds setup info (ok fuck, fuck, fuck)
(Ok stay cool composed, lets ask some questions maybe he thought it all in a cool way I can’t get my mind around)
Me: So how are you gonna get the correct version from the repo to the env and init the correct schema?
Dev: I haven’t thought about it yet.
Me: Are we gonna save each version to a file system then your code is going to fetch them?
Dev: I haven’t really thought about it we will see. But look on customer init user setup I implemented a password strength validation and it also checks if the password is the same.
So after this Pokémon encounter I politely closed teams. Stood up drank some (a lot) coffee ☕️. Put out the washed laundry while reflecting on life’s good things, while listening to classical music 🎼 .
Then I sat on my office chair drank some more coffee, put some linking park starting with in that order:
“Numb” then “What I’ve Done” and ended with “In the end, it does really fucking matter” -
the place my friends and I were previously interning at offered to pay us for some freelance work once we started school, "it'll only take one month, the backend is ready!", they said.
We finished on time, and delivered fixes throughout UAT. 9 months and counting only paid half the promised amount.... -
!= rant
Does AngularJS still have momentum. I toyed with it for a while on a side project. Since then .Net Core launched and most of my work (both day to day and side projects has been in MVC 5 or .Net Core)
I wanted to go back to tinkering with that one side project but it seems that some of the hype surrounding AngularJS has died off.6 -
When you are tearing you hair out trying to figure out why the PR you're reviewing isn't working. Then you realize you forgot to pull the latest changes!
-
When the users say UAT went brilliant yet mysteriously all goes BOOM when feature goes live. #aDayInTheLifeOfAdev
-
Is there a unit test for dance moves? I really gotta see some green lights before I move this one into production. Side note: anyone have a UAT environment for this? Thx3
-
You know it's Friday afternoon when your interface is broken because you tried to set the type to the string 'string' instead of the keyword string.
Interface IEnvironment {
name: 'string',
...
} -
Received 'Thank you' e-mail after Test Deployment and UAT !!
Usually i receive that e-mail after production and some issue findings! -
Last employer -- a major health care insurance carrier -- had over a million current and former subscribers data in SQL database with no encryption on SSN or other personally identifiable information. I reported this as an issue, and was told that since they had intrusion detection, etc. they don't need to encrypt the data. Guess they have never heard of zero day vulnerabilities or disgruntled employees?
-
On pager duty. Getting alerts about New Relic synthetic monitors failing in prod. Freak out. Go to check them out...all of them are pointed at the uat sandbox, not prod.
I don't know how to feel about this. -
When we take user stories in sprints but dependencies are not resolved. I have to wait till n-1 the day for the upstream team to go to UAT and then push half my tasks to next sprint for testing \ prod . Fuck the planners - _-|-_-¦
-
I just thought of an elegant solution to a problem in prod. Basically need to run 2 different versions of a app.
Just deploy it to uat and point it to prod db for the data.
I guess if we were following microservices architecture though we could deploy both versions to prod but we don't....3 -
!==rant
Are there any good cloud-based IDEs that:
1.) Supports C# (ASP.Net Core / MVC)
2.) Would work on a Chromebook2 -
Resolve overlaps in repos downstream from current project. 1 overlap... Get in today, 7 overlaps downstream; including original. This means we can't deploy the code that a developer decided needed to be fixed; it didn't; and we have 1 week before go live and still need UAT validation, oh and QA needs to retest all the components due to the "required fix". What in the actual fuck?!