You report it could have been Sally or Billy
Re:Git as a NoSql Database (2016)
by irrational on Tuesday April 06, 2021 @12:15PM
(#26713721)
That isn’t how this works. Based on OPs description, the fact that Sally made a change is gone since the last editor was Billy. It looks like Billy made the change to both column 1 and 2.
You tell your boss:
"Just so you know, we only take a snapshot every X minutes... so there's a chance Billy wasn't the person who made that change. If you had told me you were planning to fire people as a result of this tracking system I might have spent more than five minutes hacking it together with a cronjob and a git repository."
Re:Git as a NoSql Database (2016)
by TeeMassive on Monday April 05, 2021 @08:41PM
(#26706635)
Your boss let changes go through the production DB directly
Your boss decides to fire people as a solution
Your boss should be fired
Your boss doesn't micro manage
You should be taking care of this, not Billy
Re:Git as a NoSql Database (2016)
by TeeMassive on Monday April 05, 2021 @09:42PM
(#26707056)
Firing a team member for a team mistake is micromanagement.
Re:Git as a NoSql Database (2016)
by irrational on Tuesday April 06, 2021 @12:13PM
(#26713693)
I’m assuming Billy was fired because Sally made an unethical or illegal change.
Billy did nothing wrong!
Re:Git as a NoSql Database (2016)
by irrational on Tuesday April 06, 2021 @12:13PM
(#26713679)
I’m assuming the change Sally made was an unethical or illegal change.
Sally makes a change to column 1 of record 1.
Billy makes a change to column 2 of record 1 a nanosecond later.
You commit to Git again.
Your boss wants to know who changed column 1 of record 1.
You report it was Billy.
Billy is fired.