unlabelled-event-logs VS system-design-primer

My problem is sorting input and window logs where input logs are logs of every keystroke on client machine and window logs are logs of every window opened. My prospective employer uses these, runs something like https://github.com/diogoff/unlabelled-event-logs and then advises clients on how to improve their business processes.

I am trying to port this: https://github.com/diogoff/unlabelled-event-logs

I have one interview for a role writing/adapting algorithms for process mining like this: https://github.com/diogoff/unlabelled-event-logs

✅ donnemartin/system-design-primer: https://github.com/donnemartin/system-design-primer

View on GitHub

I've been giving interviews for past couple of months and this github repo has helped me so much for system design perspective and I can see myself excelling at interviews. - https://github.com/donnemartin/system-design-primer

You'll be on opiod's probably the first 1-2 days, so sleeping should be fine. Everything will be allright, don't worry too much. Just use the time now to prepare for the time after, make sure you go through post-surgery-essentials thread. Once you are out of the OR you won't have the energy to think about those details, so make sure you take that prep serious.

Tooling isn’t architecture. Figure out what you need to handle both personas and volume/throughput and then lay out the capabilities you’ll need. As you lay out points of ingress, egress, consumption you can start to lay out sequences(think in persona and sequence diagrams to express interactions between services). Lastly, evaluate tools that offer some of these capabilities and weigh the trade-offs (there are always trade-offs: https://github.com/donnemartin/system-design-primer).

[1] https://github.com/donnemartin/system-design-primer [2] https://www.teamblind.com/post/My-Approach-to-System-Design-V4SJARdx