grokking-the-object-oriented-design-interview VS system-design-primer

I'm trying to figure out the structure of my program but a few things don't make sense to me. So I have designed a user object using this OOP guide (grokking the object oriented design) and factory design pattern. Here is my object of a user

If this guy can't google "movie ticket booking assignment" and look at the very first result which is a working version of the project he wants to do with diagrams and code, he doesn't stand a chance.

Go through Grokking the OOD. There's most likely going to be at least one OOD question, sometimes I've seen even two or three. Purpose of these questions aren't coming up with an algorithm, but to test how you design classes and functions. Make sure to ask a lot of clarifying questions, because most likely they'll ask you something really vague like "Design a parking lot" or "Design the game Battleship." Grokking is honestly a bit overkill, but it'll guarantee you know what you're talking about during the interview.

Here's a good GitHub repo that has several examples of OOD case studies with code written in Python: https://github.com/tssovi/grokking-the-object-oriented-design-interview

Someone posted this link of project ideas.

Check these, those examples are written in Python but can be easily translated to Java

tssovi/grokking-the-object-oriented-design-interview (github.com)

✅ 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