3 ms·
> it could actually be beneficial for software engineers to have an official accreditation I've waffled on this, and I'd be curious to hear input from others.
by abeppu 8y ago
> it could actually be beneficial for software engineers to have an official accreditation
I've waffled on this, and I'd be curious to hear input from others. On the one hand, software engineers are building systems which have incredible reach and impact. It's reasonable to want to ensure these systems are being built by people with some solid body of knowledge and skills.
However, software engineering as a field changes relatively quickly, and we hardly ever reach a consensus about the best way to do anything. It's often somewhat unclear to me whether we're making forward progress at all (because we keep inventing "new" ways to build the same things). And because software is in every kind of system, two very skilled and productive software engineers might actually have very few overlapping tools in their toolbox. Could we ever agree on what should be part of the official accreditation, and how long would it be good for?
- logicchains 8y agoMy university had a "Masters of Software Engineering" course that was accredited by some European engineering body, and a significant amount of the content was UML diagrams, OO and writing huge reports. "Engineering" as it is practiced in other fields seems fundamentally tied to the waterfall approach, which makes less sense in software.