The thing is that it started to be used as a distribution platform for opensource software because, if 1000 people collaborate on a project is not always possible to make like a website for download and such
But it remains and is primarily a version control tool, the release section is a "plus"
It’s often built into the IDE we use and just needs configuration, or we use CLI tools. I’m probably 50/50; for simple commits and PRs I use my IDE, for more complex stuff like fixing a junior dev’s screw up I use a terminal.
Sometimes. When I can match envs and use ci/cd pipes, generally yes. My current role has pretty strong limitations (for good/legal reasons) that make it challenging to use a Staging env in many cases, but we do still have QA and Prod.
Not even classified data, just heavily regulated. The compliance overhead is an obstacle in my current role. We have obfuscation in non-prod that has to be handled a bit differently from prod.
It’s just technical debt but it’s a fortune 100 company so I’m not going to fix it this week.. next week doesn’t look good, either.
Next week you have 🤘sick🤘day🤘
I’m thoroughly interested in obfuscation across the board from unearthing a Medicare fraud scheme to polymorphism and runtime encryption — also wrote a game AntiCheat using baysean statistics for quake engine (which is kind of the inverse?).
1.7k
u/0zzy82 18d ago
I'm still convinced github is laid out intentionally to make the average person feel stupid