Kinda annoyed at NDA's right now

Can't discuss what I'm working on with old classmates for another opinion. And my co-workers are self-taught on this job as they needed so everything I'm doing seems like magic to them

So they're probably not going to spark that inspiration I need right now

And I can't reach out to the R&D department full of programers with this cause they're heavily behind so we're told no distracting them

@rEaL-jAsE self taught is cool. But they're only so far as what's needed when it is. They're not going really into programming which is my issue with bouncing ideas off them

I hope no one thinks I'm criticizing self taught programmers in general. 😅😅😅😅

Honoring NDAs is for chumps. 9 times out of 10, the project you're working on is not as important as your company thinks it is.

@jester5537 I'm self taught, 16 years in the industry, don't blanket rule us all.

@nitnip

I don't think that you have seen a full fledged NDA, which is legally binding.

Despite monetary fines, breaking an NDA can result in a law suit which can then unfold into criminal charges - e.g. for spilling trade secrets. A criminal record is in certain countries set in stone and will prevent further employment very succesfully.

Gossip spreads with warpspeed even in our times... Reason I'm very careful when it comes to NDAs. There must be just one idiot who spills the tea and one psychopath who wants to terminate your work contract and your life can be completely fucked up.

@C0D4 I don't mean to I'm just bad at wording things. In a reply on here I mentioned they only learn enough when needed and don't really go into programming unless they have to. So that's what makes it difficult to bounce ideas specifically off them.

@jester5537 A conundrum situation.

I'd write an open letter calling for brainstorming I'd guess - as specific as possible listing your current problems and possible solutions.

I'd definitely think about changing the workplace if someone thinks a call for help is "disturbing" devs - as the show must go on in all projects.

Priorities aside, when one project stalls or becomes a shit show due to insufficient knowledge / mentoring, it's better to disturb them now than to have to redo the project later cause it's unmaintainable.

Can't you generalize the problem? You wont break the nda it you discuss the underlying system with broad general terms and really only try to brainstorm a similar generic problem that also applies to your Situation.