26
rudinskiz
14d

how to be a shitty client:
- have a legacy database where column names are misspelled and everything is nullable
- hire external help which instead of helping break the ui (bonus points for breaking the api too)
- demand a very much custom auth logic but decide to use aws cognito for shits and giggles
- demand 1hr daily meetings
- demand biometric auth with 0 knowledge of how biometric auth works (the previous devs just had a face id prompt which does nothing and retrieved email and password saved on the device???)
- message me at 2am because you don't understand how timezones work + demand a build while you're at it
- call me a "heretical pagan" because i took a day off on a holiday you don't celebrate (???)

i could go on but i think this is enough

Comments
  • 0
    Edit: damn it! this is the second time I mixed this up with Kylo Ren more gif! lol
  • 1
    the real more!
  • 1
    sounds like you should scam them like all the prior people also scammed them

    you can make them _feel_ scammed while actually being honest though btw
  • 4
    that started bad and ended at lawsuit levels
  • 1
    I thought you were @Root
  • 0
    Just stop responding to emails and disappear. That’s it
  • 2
    @kiki Honestly not too far off from places I’ve worked.
  • 2
    update: we have a meeting today, so i'll bring in more tomfuckery when we're done
  • 3
    @Demolishun here's more:

    - ask me to hardcode api keys

    - hire an external pentester who instead of testing the actual app tries to pentest aws itself (runs tls scan on aws lambda????)

    - be passive-aggressive when i mention vacation because you can't fathom the idea of labor laws

    - bully me into a build even though i told you it's not ready 10 times already

    the only saving grace is that our release names are based on pink floyd song which makes me very happy
  • 0
    @rudinskiz just the bigotry would be enough for a lawsuit, you're a very patient person
  • 0
    @rudinskiz it’s all about brain damage and money, eh?
  • 0
    - use zod for objects with cca 30 fields but everything is optional
    - conditions everywhere
    - we don't learn new things so we will use what we know the way we know even it is not intended to use it that way
    - bring thinking and logic from different framework than you are using now and wonder why it is not working
    - top down data manipulation concept but data types are vague and can be different for the same thing

    ....
Add Comment