I have received tons of shade from my organization for insisting we document business logic (literally had leads pull me aside and tell me to stop suggesting it) and I think I understand why now...

It's how some engineers stay relevant and useful in an org. They like being the one everyone comes to when we need to revisit previous business logic to make changes or verify that it's working like it "should".

Usually not the type to indulge in my own paranoia, but this one particular lead accidentally shared a window with a workflow diagram outlining our onboarding process while presenting during a virtual meeting, and when asked to share the doc, said he "accidentally deleted it", lol.

Idk, to me they're shady tactics. I just want to understand how the product should work so I can do my job. I don't want to have to come to you and extract information that could easily be public.

toxic

had a problem with people like that, not fun and kind of depressing

Document anyway, document as if they've got something to hide and you've got to cover your ass when the crap hits the fan.

Keep docs on your local drive, google/onedrive, etc and away from those prying eyes.

Paranoid? YES! Nothing wrong with a little CYA.

At my org nobody really knows how every line of code works anymore. So we discover how it works often by attrition. Yes, we have a very good idea how the entirety of the product works: electrically, physically, and software wise. But not the minute details of every line of code. Too many coders and too many years.

@jestdotty Yea, we had a dev that pulled that nonsense. Lie, spread rumors, etc. He's since been fired.