4 ms·
You must work at Microsoft? A pound of paperwork for every new repo really shuts down experimental side projects. I showed my colleagues that we can share code
by fingerlocks 1y ago
You must work at Microsoft? A pound of paperwork for every new repo really shuts down experimental side projects. I showed my colleagues that we can share code via ssh or (painfully) one-drive anytime instead. They reacted like I was asking them to smoke crack behind the dumpsters. “That’s dangerous, gonna get in trouble, no way bro”
- mewpmewp2 1y agoIf you are working in a large corp and not your own side project, that honestly does sound like a bad idea.
- deleted 1y ago[deleted]
- fingerlocks 1y agoPlease, elaborate. I can share my screen with coworkers and talk about all sorts of confidential things, and I can even give them full remote access to control everything if I wished. So why would pushing a some plain text code directly to their machine be so fundamentally different than all the other means of passing bits between our machines?
- mewpmewp2 1y agoIf you share screen you are in control of what you show, if you give someone SSH access, what would stop them from passing/running a small script to fetch everything you have or doing w/e with your computer? I mean it's a blatant security violation to me. Just no reason to do that. In large corps you usually have policies to not leave your laptop unattended logged in, in the office, that would be potentially even worse than that.
- fingerlocks 1y agoI wasn't aware that I could run a small script and fetch everything from every host with an ssh git repo. TIL.
- JoBrad 1y agoI mean…git hooks are just scripts. If you can fetch, you can pull (or push) a script that executes locally.
- udev4096 1y agoIt's not. Unless you work at a shitty place, something like what OP mentioned is far from a big deal and most people would wanna know more about it
- mewpmewp2 1y agoThe code is considered IP of the corp and they probably have rules around how or where IP should be shared, access controls etc.
- fingerlocks 1y agoThere is nothing inherently special about code, than say, a confidential marketing deck or sales plan. If they can go a network drive, or a service like One Drive , why can't we put our code there? I'm not talking about the Xbox firmware or the entire Windows source. This is about little one-off projects, highly specialized tooling, or experimental proof-of-concepts that are blocked by bureaucracy. It's a misguided policy that hurts morale and leaves a tremendous amount of productivity and value on the floor. And I suspect that many of the policies are in place simply because a number of the rule makers aren't aware of how easy it to share the code. Look how many in this thread alone weren't aware of inherent distributability of git repositories, and presumably they're developers. You really think some aging career dev ops that worked at Microsoft for 30 years is going to make sensical policies about some software that was shunned and forbidden only a decade ago?
- udev4096 1y agoOP is fully soaked with corp bullshit. A fellow sellout! Please read this: https://geohot.github.io/blog/jekyll/update/2025/10/15/pathetic-losers.html https://geohot.github.io/blog/jekyll/update/2025/10/15/pathe...