MockMotor
Vladimir Dyuzhev
MockMotor Creator
We Know What You Did Last Summer
With many teams comes the need for an audit
Gone are the days when a mock environment was developed and maintained by a single person. Now there are usually a few people, sometimes separated by oceans, each focusing on their own part of the application functionality.
And sometimes the work of these different people conflicts.
Until recently, if someone changed a mock reaction or a mock account, it was hard to figure out who did it (and why), so fixing it was hard. It was still possible, but required reading the logs.
After a few time-consuming investigations, I added an audit layer to MockMotor. This is not a “police state” thing. MockMotor merely helps you to find the relevant person to fix the issue fast!
All objects being saved go through a compare stage. For new or changed objects, MockMotor creates an audit record that lists who made the change and which fields were changed.
For the time being, those records are only available on UI for the mock accounts. But next, I will add them to mock reactions and other often-changed objects.
AI created no part of this text. It isn't the Butlerian Jihad, but it is something anyone could do.