You know, it never occurred to me that I would have to do something like this but I'm gonna start.MD5Sum!
Don't blame noodle he was smoking hash when he wrote itYou're a real sum' bitch
Ideals like this don't actually apply to corporate america.Did you tell them security through obscurity is a well known anti-pattern and reeks of a core vulnerability?
Last Cert I took wasYou will need to study since those types of tests tend to ask you obscure questions about stuff you never actually use in reality.
I'm working towards my VCDX right now. Been annoyingly taking the required Certificates for the Cloud Management Track as they won't let you do your Defense until you've completed then ;_______________;.Google just announced the start of a new certification path for Android developers. I'm fully prepared to look at a some aspect of it and think something along those lines Vinen.
Really need to merge each change individually don't you, or won't their changes break your mods?Code management question bros:
We have our code base. It's based on a base code by a 3rd party vendor with all of our changes on top of it. It's pretty massive, around 22k files.
Every quarter we receive a drop from this 3rd party vendor that we need to merge into our code base. Due to the intermingling of code, I can't just copy and paste their code into ours as it will wipe out our stuff.
On a small scale, just diffing the two codebases would be fine, but what's my best option when I'm dealing with such a massive behemoth? Is it still a manual diff?
Should I put their codebase on a separate repo/branch, merge, and deal with conflicts?
Not develop this way. Holllly shit does this sound like terrible practice.Code management question bros:
We have our code base. It's based on a base code by a 3rd party vendor with all of our changes on top of it. It's pretty massive, around 22k files.
Every quarter we receive a drop from this 3rd party vendor that we need to merge into our code base. Due to the intermingling of code, I can't just copy and paste their code into ours as it will wipe out our stuff.
On a small scale, just diffing the two codebases would be fine, but what's my best option when I'm dealing with such a massive behemoth? Is it still a manual diff?
Should I put their codebase on a separate repo/branch, merge, and deal with conflicts?