Thank you for that insight… It’s a really neat way of thinking about
Here’s one issue that we face:
The “advising” application allows faculty to see all kinds of student
data. Of course, students wouldn’t be “advising” themselves, so they
would get at the data through a different method. Grade Checking would
be separate, but would need to be called from within Advising (I want to
see your grades and I am your advisor).
Normally, I’d just render partial and get what I need. How would I do
that if the apps are separate?
I would think that separate apps would be easier to maintain…
.Developer A wouldn’t need to check out the whole big app just to work
on his Advising piece. However, is there a better way to build this in
pieces and still keep it all together?