Note that there are some explanatory texts on larger screens.

plurals
  1. USuser44298
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. CO@user310291 all can be useful sometimes in software design things can be very subjective & the wrong things can work better then the right things in certain cases. I think the only good design patter really is: Don't follow design pattern specification blindly. Also everyone is entitled to an opinion & I personally find to classify your interfaces as mandatory or not may come in handy.
      singulars
    2. COit's likely to AddCourse() to a teacher with a DateTime - it's more simple for a developer to pickup this approach then having to understand where to add a course & time slot for a teacher which would be located in the ClassSession class?? I'd be disappointed if I enter a new work place and things are not straight forward Teacher.AddCourse() but it's new ClassSession (Teacher,Course,Datetime). Which one you find easier to understand ? So I am after: 1) Unnecessary complexity without theoretical or practical need 2) No extra properties to justify the mapping class. Otherwise it can be done np.
      singulars
    3. COLastly: "Simply asserting that writing one more class was too much of a maintenance burden and would not be used isn't any improvement" this isn't at all what I'm trying to put up front, I just point out the obvious - more code more work, it's a side effect. What I do argue is that you don't need an extra class to hold a mapping between a teacher & course. Aslo another big problem that I see here is that I cannot see the practical use of it. You rarely search or display UI screens for "class seesion" rather you display the schedule of a teacher or teachers for course, think about it
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload