It will still be tracked. Here’s an example of how code checkins work. This is an open source GitHub repository. The code here is real code created by one of the tech bro kiddies, Marko Elez. Note how the visualizer that compares what he checked in with previous code. These kids can’t come in and change the way source code is generated i…
It will still be tracked. Here’s an example of how code checkins work. This is an open source GitHub repository. The code here is real code created by one of the tech bro kiddies, Marko Elez. Note how the visualizer that compares what he checked in with previous code. These kids can’t come in and change the way source code is generated into the production system through the repository. That would be a monumentally difficult task.
Likely - I get it, I work with software engineers. With back doors, they can work and wait, and figure out how to override or work around GitHub, if that’s what they are using.
I agree it’s harder. But not impossible especially if you’ve built access in. Muskrat smart enough to playa longer game.
There are many things going on that I just know are wrong. In this, I understand how wrong their access is and all those annual security trainings at work make me panicky.
So angry. Thank you for responding though - I appreciate it.
Can I just add that you have the right to be very angry? I would not, under any circumstances, wish to to dismiss those feelings or make light of how serious this all is. I’m glad that the “team” seems to be dissolving in real time. It’s a reflection on the fecklessness of these nutcases. And late last night, a judge finally put at least a temporary stop on it. Will it be honored and/or enforced? Who knows?
It will still be tracked. Here’s an example of how code checkins work. This is an open source GitHub repository. The code here is real code created by one of the tech bro kiddies, Marko Elez. Note how the visualizer that compares what he checked in with previous code. These kids can’t come in and change the way source code is generated into the production system through the repository. That would be a monumentally difficult task.
https://github.com/markoelez/pyslam/commit/75d6fc2226e50f7b5b14fac7da929631c09dddd5
Likely - I get it, I work with software engineers. With back doors, they can work and wait, and figure out how to override or work around GitHub, if that’s what they are using.
I agree it’s harder. But not impossible especially if you’ve built access in. Muskrat smart enough to playa longer game.
There are many things going on that I just know are wrong. In this, I understand how wrong their access is and all those annual security trainings at work make me panicky.
So angry. Thank you for responding though - I appreciate it.
Can I just add that you have the right to be very angry? I would not, under any circumstances, wish to to dismiss those feelings or make light of how serious this all is. I’m glad that the “team” seems to be dissolving in real time. It’s a reflection on the fecklessness of these nutcases. And late last night, a judge finally put at least a temporary stop on it. Will it be honored and/or enforced? Who knows?