Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

147

Some of the choice ones i have noticed, a continuation of prior post i wrote.

  • Someone did testing on some code, ironically not QA but another developer, of the curry descent. They decided to test malformed json by passing a string with a value of "null", not to be confused with a null value to the request. Confusing arose because i was expected to know which was which. Why not use garbled text or something instead of using a value which is historically known to have a certain expectation?

  • All environments are open to developers, from DEV all the way to pre prod. To get around the approval issue, everyone has access to self approve their own deployments. This has lead to many, many issues as there is no mechanism to stop bad builds from being promoted, since the dev can promote through an override.

  • Per my manager, all the coding was done in a week and thrown into a production environment, and the idea was to go back and fix it later. I added a very small change to some endpoints, which is what eventually caused complete system failure when the experimental functional testing started running its test cases. See the functional testing framework was just created in tandem, and it is now noticing issues with the code, except my changes didn't actually touch the code logic, they simply exposed the functionality

Some of the choice ones i have noticed, a continuation of prior post i wrote. * Someone did testing on some code, ironically not QA but another developer, of the curry descent. They decided to test malformed json by passing a string with a value of "null", not to be confused with a null value to the request. Confusing arose because i was expected to know which was which. Why not use garbled text or something instead of using a value which is historically known to have a certain expectation? * All environments are open to developers, from DEV all the way to pre prod. To get around the approval issue, everyone has access to self approve their own deployments. This has lead to many, many issues as there is no mechanism to stop bad builds from being promoted, since the dev can promote through an override. * Per my manager, all the coding was done in a week and thrown into a production environment, and the idea was to go back and fix it later. I added a very small change to some endpoints, which is what eventually caused complete system failure when the experimental functional testing started running its test cases. See the functional testing framework was just created in tandem, and it is now noticing issues with the code, except my changes didn't actually touch the code logic, they simply exposed the functionality

(post is archived)

[–] [deleted] • 2 pts

We're in the early stages of moving to Oracle Cloud from Oracles antiquated, on-premise retail solution.

We used to deal with a piece of software that handled all of our B2B transactions; proprietary fixed-length files. While we no longer use that software, I've been instructed to move forward with continuing to use the legacy file mapping.

Meanwhile, we're moving into the cloud...we have the ability to create REST and SOAP services...we have the ability to encode data to EDI standards...we could just come up with a new proprietary format.

But no. We will use the legacy format. It will have to be altered to allow for new functionality that would be out of the box if we went with EDI.

After making a "bad face" on a zoom call when I heard that decision, I was later advised by my direct supervisor that the CIO has a target on my back.

Wrong-face. It's a thing.

[–] • 1 pt

Reliability is having an "old" interface working along a new one

I see plenty of "let's rewrite this" just not know of all situations that are handled by the old cruft AND have no plan to handle in the "new version"

Result, lots of pain

Your boss has been burned before, you will in the near future

[–] [deleted] • 1 pt

Yeah, a parallel deployment would be ideal.

But no. Knife-switch. It's a full on clusterfuck wrapped in FUBAR served with a soup sandwich.

[–] • 1 pt

It's amazing how stuck in the old ways people in IT actually are while pushing the shiny new thing every time there's a shiny new thing.

I say this as I'm sitting on a NOC where it is "break-fix/do it for them" half the day.

[–] • 0 pt

they simply exposed the functionality

Or lack of?

[–] [deleted] • 0 pt

Drugs might be needed in this case.