In the first place you should have" created a single page for each class that does both the create and the update. Whatever fields are different between the two operations can be made different when you are populating the page. That will cut down signficantly on the amount of code you have to maintain.
It will also make it easier when new things are added to the classes, because the changes will need to be made in only one place.
You could create a base page class that other will inherit from. If there is common functionality there that can be reused, that's probably a good starting point. No if you are direct editing of tables, since you have like a table per class aproach, then maybe you could use some framework or create a generic edit feature for simplier tables.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.