76
Godisalie
77d

Sometimes I wish I was allowed to just strangle my colleagues...

Example from the 'code base':

try:
do_something()
except Exception as e:
log(e)
do_something()

When I asked why they would redo the same call right after it failed I was told that 'It works the second time because it takes time to raise the Exception '.

Bitch, you've got a race condition in your sensitive banking software. You know it's there. Do you really want to trust the time needed to raise your exception will always be enough to synch that dumpster fire you call code?
Show some fucking respect for your craft and fix that shit. But of course they won't, because it will work flawlessly until it suddenly stops working. Taking down who knows what in this damn, undocumenred monolith with it....

Sometimes I'm honestly afraid to trust banks with my money.

Comments
  • 12
    I already ++ after the first sentence
  • 3
    Oh it didn't work the first time? Why not delaying it instead of actually understand what went wrong!

    People sometime.... people...
  • 1
    time.sleep(2)
    do_something()
  • 6
    I work for banks. Many banks. You shall never trust them with your money.
  • 1
    Your anger is misplaced, though. Each and every single one industry holds on spit and wire because it's cheap and it holds until it doesn't. Fintech is just the tip of the mountain.
  • 2
    They are incentivized to make features. They are not incentivized to make good code.

    This idea doesn't just exist in banking. I've found it in every industry and technical debt always comes due.
  • 0
    This reminds me of
    try:
    something();
    catch(e):
    if(something() == failed)
    log error();
    throw Exception();

    try; catch; finally; I guess.
Your Job Suck?
Get a Better Job
Add Comment