A quick piece of advice for fucking System Designers and Managers · 10:03pm Jan 27th, 2021
If you want a project written?
WRITE A FORMAL FUCKING DOCUMENT FOR THAT PROJECT.
DO NOT:
- Use periodic comments spread over a fucking week inside a Slack chat room as your official documentation.
- Use a string of emails as your fucking documentation.
- Ignore questions that you get asked, or worse get ANGRY when you are asked questions ... WHEN YOU HAD INSISTED THAT THE DEVELOPER DO SO IF THEY HIT ROADBLOCKS.
- Expect the developer to be able to work with a third party application ... AND NOT GIVE THE DEVELOPER THE PERMISSIONS TO ACCESS THAT FUCKING SOFTWARE'S CONSOLE SO THEY CAN OPERATE THE FUCKING API IN THE FIRST PLACE.
- Get angry at the DEVELOPER for missing YOUR comments, when YOU FUCKING MISS THEIRS AS WELL.
Fucking arshole.
Very informative.
My favorite is:
Or my other favorite, after the implementation:
5443147
No ... just bitter.
Immaterial now, since they laid me off.
5443491
... did we work together somewhere?? Because all of that sounds familiar.
Did you get the "it's all explained in the PDF I sent you," ... where they are referring to a PDF they stuck as an attachment inside a slack chat ... and I'm looking at the fucking PDF they attached to the actual fucking JOB ticket?
Or the job where they go ballistic at you for messing with API calls to a metered service ... and after two weeks of somewhat confusing to-and-fro you discover that the reason you're having all of these difficulties ... is because they didn't actually give you access rights to USE the APIs they want you to use ... AND it's meaningless anyway because a different developer had already written code to do what they're asking you to do again ANYWAY????