Unless you work for a body shopper, then there is no hierarchy at all.
In the US, the Amalgamated Union of Corpse and Body-Part Purchasers (AUCBPP), carefully moderates the purchase of dead bodies and body parts.
The AUCBPP is administered by Stewards who are elected from the fifty state memberships, and they, in turn, elect a five member Executive Council, who, in turn, hire a professional Executive President who is given the honorary title "The Grand Ghoul."
There are three degrees of certification : all include various degrees of Hazardous Materials (HazMat) training, formal examination, field-testing.
Purchase of living bodies, and body parts from the living, or partially living, or comatose, etc., of course, is in the hands of many other groups ranging from the Mafia, to the Triad, to various secret government agencies, and, last but not least, private enterprise.
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
Unless you put it in your sig or bio, we can't. The email address in your profile is hidden; the email link opens a webform that sends an email to the recipient without showing the sender the address (antispam feature).
It is a truth universally acknowledged that a zombie in possession of brains must be in want of more brains.
-- Pride and Prejudice and Zombies
I'm busy making some changes to my front end application and I just came across some horrifying code written by my ex colleague.
timeAtendancePunch.MiscCategoryID = (short)int.Parse(cmbChoose.SelectedValue.ToString());
// Note that timeAtendancePunch.MiscCategoryID is of type long
timeAtendancePunch.PunchTypeID = 0;
// This is a foreign key in a static table in the db, but the ID's aren't static, their identity columns
privatevoid rdbPunchKey_CheckedChanged(object sender, EventArgs e)
grbKeyType.Visible = true;
grbKeyType.Visible = false;
// Note, rdbPunchKey is a radio button and grbKeyType is a group box
And there is many many more of this...
All this is written by a guy with 3 pages of programming qualifications on his CV(Including MS certifications) and several years commercial experience.
The last example is not so bad, it is handy for setting breakpoints on certain conditions. Note, that while you can do this is in the debugger, it adds tonnes of overhead. In your case, it probably does not matter.
Often you'll need to set more than one thing or add some debug code
Maybe the developer had problems with that code not working and added a debugging line or a breakpoint or maybe he saw that in the future he might need to enable a menu option
grbKeyType.Visible = true;
I definitely wouldn't see that as a wtf, there could be loads of reasons why that ended up like that. It doesn't look like the kind of code that's going to sitting in a big loop and if it is then there are probably bigger issues with the code than an unnecessary if statement
in the last example, he is just being verbose - nothing wrong with that
could have been done on purpose for any number of reasons.
however, someone with time on the job, all things being equal, would normally write grbKeyType.Visible = rdbPunchKey.Checked
given a choice i would rather see this kind of WTFs than the ones that introduce logic errors
let this be a lesson for all you certifications fanboys...
Opium is my business. The bridge mean more traffic. More traffic mean more money. More money mean more power.
Speed is important in business. Time is money.
You said opium was money.
Money is Money.
Well then, what is time again?