Software Engineering: Why List＜E＞ interface is additionally introduced in collection hierarchy?

Software Engineering: Why List＜E＞ interface is additionally introduced in collection hierarchy?

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 rwong (softwareengineering.stackexchange.com/users/620), user overexchange (softwareengineering.stackexchange.com/users/131582), user Nebu Pookins (softwareengineering.stackexchange.com/users/185865), user Malachi (softwareengineering.stackexchange.com/users/62519), user Holger (softwareengineering.stackexchange.com/users/108809), and the Stack Exchange Network (softwareengineering.stackexchange.com/questions/288737). 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

abstract classdesignengineering