Some of them can actually scan you or your friend's internal organs to see if they're alright too - that's not going to be php on a lamp stack. I'm guessing they are probably not moving fast and breaking things either. They may be taking it easy with your friends internal organs, just so they don't get sued by the growing legal community on HN.
There's also all that bizarre software that somehow delivers you to the airport of your choice. I wonder how that happens - do they have their Agile/Waterfall/Kanban/Nonsense boards on their office walls in order to get you there?
Agreed on the pyramid scheme. But the challenges listed strike me as mostly hardware, physics, and non-software science/engineering related. A Waterfall-like process is probably a good fit here since failure is far more costly than project budget/time overruns. Also, didn't the Apollo guidance computer suffer several failures? ;)
To me, software looks like the least-difficult part of the space program. Doesn't mean it's easy. But let's not overstate its importance.
Also, most developers aren't working on mission-critical stuff. I think it's fair to apply the 80/20 rule here.
> Some of them can actually scan you or your friend's internal organs to see if they're alright too - that's not going to be php on a lamp stack. I'm guessing they are probably not moving fast and breaking things either.
Funny you should bring up medical equipment. Recently, a laser caught fire inside a friend-of-a-friend during a bronchoscopy. Had to put him in an induced coma (Happy ending: he pulled through).
Just out of curiosity, does anyone here think there's anything inherit to either mainstream process (Agile, Waterfall) that puts direct controls in place to prevent complexity? Both talk about "Managing complexity" but very little on mitigating complexity. To me and prevention and elimination complexity is something our profession still struggles with.
Read what it actually covers and the topics they test and tell me there's something on there that is completely useless.
I've worked in waterfall shops. Sections I through V are very similar to what we aspired to do. Look, it's not like this knowledge is worthless. It's just that what is outlined in these sections is a very thorough but expensive ($$$ and labor) and time-consuming process that that when put into practice often insulates itself from the business problem at hand. Just because it looks good on paper does not mean it will look good when you start applying it to the real world with real people.
I'll say this: If you want to participate in an organization that is culturally waterfall and practices waterfall this certification will prove quite valuable. Anywhere else though, and you might give the impression you're not a good "culture fit" for the organization.
That's funny.
So, not-UML?
<a><b>something</a></b>
I do say it's not XML.
An overview of the exam: http://ncees.org/Documents/Public/Exam%20specifications/PE%2...
Not something I'd feel inclined to get unless this somehow became an industry requirement- which is unlikely - Agile and progressive Software Dev shops are probably throwing up a little bit in their mouths at this thing. Replace Agile with "Extreme Programming" and you've got something that looks like it came straight out of the 90s.