Novell's Certified Linux Engineer
AEnertia writes "Novell have been quick in moving ahead with their recent aquisition of SuSE. I was browsing their site when I found this page describing their new certification (CLE) under their certifications programs. Looks like they are positioning their well respected certification program for their newest asset."
I went to a real engineering school to learn Computer Engineering (a 4 year EEE + CS program), and every time I see a company create a certification program that takes less than a month to become an "engineer", well... it makes me cringe. I know in other parts of the world that it's not legal to abuse terminology like that, and wish the US would adopt some similar standards. This dilutes the prestige associated with earning an actual engineering degree (really, there is some!).
I know the difference between a real engineer and a fake one, but I'm not so sure the average guy on the street understands the distinction. I also suspect people in hiring positions give a lot more weight to a certification that pretends to be an engineering degree than they really should.
Oh great. Another reason for non-engineers to call themselves engineers.
Since the only *real* purpose of a cert is to give companies "good vibes" about you or get your foot in the door, who cares what the real training is? A person has good troubleshooting & admin skills, or they don't. Other than that, if your cert is printed on absorbent paper you could wipe your ass with it. I've worked with too many people who had more certs than Seymour Cray who were dumber & more useless than a bag of rocks. Anyway, if Novell/SuSE takes off, having this cert could open door for you, and it's then served its only purpose.
Its a poor craftsman who blames his tools.
Its an even poorer craftsman who cant tell a good tool from a bad one.
Anything NOT worth doing is NOT worth doing well...
The Novell page doesnt seem to reference how long the cert is good for - even in the faq..
Anyone know?
GPL'd web-based tradewars themed space game
Novell mentioned it was comming in '02 and announced it at Brain Share '03.
The only reason to have a certification is to be able to prove to someone who doesn't have a clue about computers that you might know what you're doing, ie: it's something to flash the HR lepton who has concocted a bunch of hiring "qualifications" that they themselves don't understand. I've held an MCSE for nearly 5 years now and I still have yet to be asked to produce it. I'm just glad somebody else paid for it. A certification is no replacement for the problem solving skills that only experience can teach you, but try telling that to some HR drone. That's one of the reasons I decided to go the self-employed route. For some weird reason, it's a hell of a lot easier to bid a support contract for a company than it is to get hired by them, even though you may be doing the exact same thing for more money!
You're using her as bait, Master!
I think most *nix people, like myself, are turned off to MS not simply because their servers are less stable or more bug prone, god knows that *nix admins have to run patches a lot too. I think my biggest gripe has to be the cumbersome nature of admining a box with a UI that was really designed for a user-friendly home machine. Compared to linux or solaris, where I can admin a hundred boxes by typing in one command (of course, after I set everything up to do that), its a bitch to admin multiple windows machines. On linux desktops, if i want to set up printers, i simply copy over the cups config files to the new machine. 1 second, done. Windows, you must go through a myriad of printer configuration screens, esp. if your printer is on an lpd server. I could ghost a windows image and burn it in to each machine, preserving settings, but that is as well, time consuming. I could copy out the registry settings and reimport them at install, but its still easier to scp/rcp files and be done with it. Now a good MCSE is a master at his/her craft and I admire his/her patience (hehe) and his/her ability to navigate and troubleshoot a poorly documented and closed source system. However, I do agree with the parent/parent/parent/.. that the MCSE test is quite lacking. Real-world scenarios in a lab and not on a A-B-C-D answer sheet would make the MCSE test more worthy of the money that you put into it.
Its also quite easy for people to make fun of things they dont understand; I love how people always say MS stuff is simplistic, until they need to fix it. Then they just say its poorly designed. Maybe if they spent time trying to understand how the OS or application does things, instead of complaining about it, they could fix it.
Actually that's not my problem with Windows. My problem is that it's too complex, too convoluted, and simply lacks the tools to properly diagnose and repair. Sure you can buy third party tools to make up for some of these deficiencies but I'd rather use Linux. The configuration for pretty much everything is plain text and documented freely instead of hidden behind a single-point-of-failure binary registry and anonymous GID identifiers. The system internals are all public and I can access any part of it I need without gagging NDAs and/or paying for the privilege and finally -- I am not tied to one megacorp with a penchant for monopolistic practises and stifling innovation. I have enough problems with running a business that I don't need to compound the issue by welcoming the vampire into my house.
Basically my beef with Windows and my desire to use Linux stems from the simple fact that when something does go wrong, I can fix it far easier and without paying for the privilege. And in those cases when Microsoft is either unwilling or unable to fix something, I can always hire a programmer to fix it for me.
I suggest that any good technically competent person is lazy, and someone I'd rather hire. Put yourself in a supervisory role for a moment. Who would you rather hire:
The second person, disliking the "fireman" syndrome so common in support departments, would have to be defined as lazy in that he/she is disinclined to work putting out fires. One can argue that the time spent in preventing the fires in the first place disqualifies the person from being called lazy. It's a shame that upper management tends to look at hard numbers, and it is much more difficult to provide a number for prevented problems, than it is to provide a number for solved problems. Upper management sees that person A solved 30 problems, person B ( the lazy one ) solved 10 problems in the same time period. However, management often does not quantify the extra work person B did to prevent those 20 problems, they just give person A great praise, and quietly replace person B for "underperforming".
Suffice it to say, I'd rather hire the lazy ones.