Software Engineering, as a discipline in its own right, is reaching the end of its third decade. As such, we might legitimately be expecting that Sofnvare Engineering curricrrla will reflect some level of maturity, both with respect to the conception of software as an artefact and with respect to the incorporation of effective engineering principles. I will argue that this is simply not the case andfurther that the trend may well be the opposite of what engineers from traditional disciplines might respect.