Does anyone here reject a requirement because there exists no elegant solution to it and you shall die before writing spaghetti code?🤔

Can you elaborate, you have piqued my interest.

@ymas we are working with a government organisation and a big it company provides them the backend. Now they have exposed an api for us.
Highlights being
1. Fuckin SOAP API
2. Verification is via fucking client verification ssl certificate

Now just because they decided to do things differently, i have to write spaghetti code everywhere to make the system architecture compatible with their fucking api fucking fucktards.

@party101 I see, why would SOAP force you to write spaghetti code? Can't you create a client and a façade on top of it?

The problem is not with the soap api per se. It’s how the existing code is written (which is also spaghetti ). With functions spanning 1k lines of code and 20 functions doing almost the same thing and no concept of inheritance. The system is fucked up. And there’s nothing that can be done as the CEO insists on a system that just works, so i am left everyday fixing some crap that the previous dev had made. Now this combined with the added nuisance of soap has started to become a pain in the ass.
On top of this, the domain of the api is https with a broken certificate chain, which the it team refuses to accept and also insist on using https😕

Well, the situation sucks, no doubt about that. I like mangled legacy code because it allows me to practice my refactoring techniques. Keep requesting the certificate issue is fixed, just write a ticket and request a follow up everyday. If you can refactor the codebase then great, if you can't/don't want to then ask to be assigned to another project. Government projects are money pits and you would be super lucky to get anyone to budge, or if you do manage it, it'll be time to retire soon. Good luck.

@ymas RETIRE??😰
I am just 20😕😂😂