If you were in charge of the curriculum at a college teaching web development, would you ensure the curriculum was regularly updated with bleeding edge technology? Or would you establish a slower moving curriculum with tried and true technologies? That’s tough. You can’t just flip a coin. It may be impractical to re-invent the curriculum too often. Maybe it even leads to worse outcomes, for example, because the staff has no time to iterate and improve on a foundation, or the choice of cutting edge technology turned out to be a flash in the pan. It also doesn’t have to be one or the other. I’ve never been intimately involved with planning a curriculum, but I’ve spoken with a decent amount of people in charge of this job over the years, and it’s more of a spectrum. As in, there is likely foundational courses that tend to stick around (databases, APIs) and others that are designed to be more de jour . Like more freeform capstone course building a portfolio or projects for a real business.…