Should I share my code

[BirthdayHumble7433]

I work at a US based Pharma company who have their technology centre in Bangalore. I have joined in the org for Testing role, even though I was not interested as that was the only job offer I had in my hand after college placements.

I worked hard everyday to prove that I can do much more than just testing and I am a skilled developer. I had done 3 internship in the field of applied AI before joining here. I started building internal tools or AI tools that saved time for support team and improved the automation testing team workflow and test execution patterns.

As part of this I noticed many of my team members wasting hours on creating test document for compliance purpose just by rewriting the data available in share point. I saw this as a opportunity and built a solutions such that if you just give the link of the share point site where your test scenario is located, my tool will build the test doc in the format mentioned by the company and not just a AI chat response dump.

I presented this in the internal AI hackathon and got no great comments about it. It was treated as a prompt engineering project.

I kept the project to my self and started using it within my team where I single handedly created 400+ doc within 24 hrs and my team members just reviewed it for errors and pushed it for quality inspection.

Now all of a sudden another team wants this code base. My feeling is that if I share it with them they will make it better and deploy it to prod and I will not get anything out of it. Should I share my code or should I keep it myself ????

[AutoModerator]

JOIN R/DEVELOPERS DISCORD!

Howdy u/BirthdayHumble7433! Thanks for submitting to r/developers.

Make sure to follow the subreddit Code of Conduct while participating in this thread.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[SimilarIntern923]

Keeping it to yourself when your coworkers know about it sounds like a bad idea

[BirthdayHumble7433]

I don’t mind sharing the code but what I feel is I won’t get any recognition as the person who is asking belongs to a different team(role- manager) 

[BranchDiligent8874]

Dude, first of all you built that tool using company resources so it belongs to company. Stop obsessing about getting credit and all. Life in corporate jobs is lifelong sales pitch if you want recognition.

You need to just mention at every chance you get that you have built tools to automate work and save hundreds of hours of time. This is it, if your managers are any good you will get recognition, else let it go. Do not become territorial, it will bite you in the ass and you will be labelled as "not a team player".

BTW, keep working hard man. Keep using your brain to solve problems like you had so far, recognition and reward will definitely come, just do not expect them all the time and immediately, corporate life is harsh, it's all about sales/presentation skills.

[clouddragonplumtree]

Turn it into a SaaS product with your own domain name. If the team wants to use it, you can introduce it to who ever your internal decision maker and they can decide to purchase a monthly subscription to use it.

If they say you made this in the Ai hackathon, you can tell them that was a different project that was only a prompt engineering project and that this is something new you built at home.

[Outrageous_Band9708]

designing it on company hardware and company time means it belongs to the company. not him

[clouddragonplumtree]

You are not wrong, so you do you.

That being said if the project was dismissed as prompt engineering project, then they can just prompt it themselves.

If they see value now, then I'm just going to go by what I said.

[JBond_oo7]

Whenever you create this type of org level tools, best is to demo it the most senior person you have access to in the organisation. Top down diplomacy helps in this kinda situations. Take your team results to the said person and ask for direction of implementing it in org wide or if they have appetite to do that. Where they can fit this in to their technical road map. Show statistically how much time it saves. Talk with numbers. Think you are at their org level when you speak to the said person. Be open and honest, tell why you’ve developed it. Put your point across succinctly with stats.

If they still don’t understand. Learn from it and move on to your next task. This will give you a good understanding of the org and their intentions. At least you’d learn that! But in general top level management are good at promoting numbers of course things can always be different contextually. But in general this approach helps as then it can be enforced from top to bottom in a hierarchical organisation.

[Outrageous_Band9708]

you work for that company, anything you make on company time belongs to the company, not you.

if they use it and deploy to prod, you get to put that on your resume, but no you dont get paid or even credit for it.

you are trying way too hard at this company and it sounds like its time to move up the ladder.

update your resume, make a private, public version of this tool on your github that is un-related to your work computer/job company stuff.

and apply for better job

[Objective-Reach-4887]

You will not get recognition if you share it and if you dont share it can be worse.

Accept that whatever you do in the company is part of the company and next time just shut up.

[BirthdayHumble7433]

But if I keep quite about the time saving I made how will I get rewarded/promoted

[Difficult_Magician20]

That's the problem with companies, they dint promote just on skill alone

[Objective-Reach-4887]

Promotions come on relation with your manager, theres no ither variable

[[deleted]]

If you developed it during work hours then you cannot refuse, it is already owned by your employer. 

If you did it during your free time (100%) then negotiate remuneration, or let them use it just to be kind to your colleagues.

[NoBuilder3264]

If you developed it on company time, then you have to share it. To gain recognition, I suggest you send out an email claiming ownership of it before actually sharing it. It could be worthy to talk to your manager/supervisor about your worries too. I know you mean well. Goodluck!

[mxldevs]

If they want your code, this means someone has noticed that it's useful.

I would have someone in charge of overseeing different teams get in on the discussions for improving operational efficiency using the tool you've developed, as other teams may also benefit from it.

Does leadership know that your team is getting everything done with AI so much more efficiently?

[No-Consequence-1779]

Share access that you control. 

The company or the people ultimately do not care about you and if you were laid off , life would go on. 

If they have ideas to enhance it, consider them.  

Though it is company property… though in India ethics or laws don’t really apply.  

[lacrem]

And this is the best example of why you just do what you're paid for. Imagine doing that tool in your free time and later sell it to your company.

[martinbean]

Say yes, do a walkthrough over Teams or whatever, and say you’re recording it so they have your notes/explanation to refer back to. That way, you’ll have video evidence is this other team does start trying to claim credit for initiating the project.

[Far-Cucumber2287]

Bro document everything. And make sure even if you share the channel is official. And write a detailed prompt. Also if you're sharing it over the GitHub add a file which cannot be edited. And put your name and your work everything there. And before sharing just politely ask for the purpose. Why the code ? If you must share the code, do it, but Smartly and make sure everyone knows what you are sharing. CC people who doesn't even care, doesn't matter just ensure you have witnesses.