Senior: Rule out the idea of making one class "Receipt" for all kinds of receipts, it should have the same load info + operations{emp,operationType, datetime, oprationDetails}
Junior: How you want to generate a detection receipt
Senior: Make a VM for the receipt
Junior: What if there is an edit on the load while moving through operations, what happens to the receipt?
Senior: OK, shove up the fucking edit details as an operation in the receipt ass

  • 2
    Abstraction, inheritance, polymorphism, and encapsulation. Those are the rules. Loosly coupled and tightly encapsulated. Make one class, and use inheritance. Your senior needs to relearn the rules. Probably won't, though.
  • 2
    Don't go overboard with inheritance tho. The whole banana gorilla thing
Your Job Suck?
Get a Better Job
Add Comment