Skip to content

Instantly share code, notes, and snippets.

@yh2n

yh2n/gist:011e72a2138a143c4c0fd559352ddbae

Created April 16, 2019 14:33
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save yh2n/011e72a2138a143c4c0fd559352ddbae to your computer and use it in GitHub Desktop.
Save yh2n/011e72a2138a143c4c0fd559352ddbae to your computer and use it in GitHub Desktop.
Download ZIP
Changelog
Raw
gistfile1.txt
Having a tool to visualize activity allows the company to be more prepared for the unexpected bugs. I think using
database triggers could be a way to anticipate or at least be more responsive when it comes to those bugs. For instance,
we could implement a trigger on some specific fields in a form and every time any given field is submitted or modfied,
a separate row or a table could be created with information regarding the field targetted a timestamp and the user id.
This would allow to have a simple changelog. We could go further by usign websockets and get instant notifications from the
server for any given trigger/change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment