Can a unified software engineering philosopy shape the right context in a curriculum?
Bridging the gap between software development requirements in the industry and eudcations in the academia
On explaining the why before the how
What info to convey, when to stop?
Usable tips also applyable to grownups?