Splitting up method in base class to avoid errors if developer forgets to call parent: a good idea?
Channel: Roel Van de Paar
Date: 28/08/2022

Software Engineering: Splitting up method in base class to avoid errors if developer forgets to call parent: a good idea?

Helpful?  Please support me on Patreon: https://www.patreon.com/roelvandepaar

With thanks & praise to God, and with thanks to the many people who have made this project possible! | Content (except music & images) licensed under CC BY-SA https://meta.stackexchange.com/help/licensing | Music: https://www.bensound.com/licensing | Images: https://stocksnap.io/license & others | With thanks to user JacquesB (softwareengineering.stackexchange.com/users/172693), user Conor Mancone (softwareengineering.stackexchange.com/users/243180), and the Stack Exchange Network (softwareengineering.stackexchange.com/questions/350390). Trademarks are property of their respective owners. Disclaimer: All information is provided "AS IS" without warranty of any kind. You are responsible for your own actions. Please contact me if anything is amiss at Roel D.OT VandePaar A.T gmail.com