Best Programming Certification??

Hello,

What is the best (by best I mean most highly regarded by employers) programming certification available today?

I was thinking about persuing the MCSD since I suspect that C# is the programming future (please correct me if I am wrong).

I am already doing a degree in computing but would like to stand out with employers.

Thanks in advance.

Are you after "Learning" (with the capital L) or inmpressing employeers?
If second then you won't survive in this industry for more than a few months.
You must decide first upon what do you really want to do - don't rush into anything.

Good luck.

Definitly into learning as much as I can. Thanks for the advice.

What is the most highly regarded will differ between prospective employeers.

An MCSD isn't going to mean squat to someone looking for a SQL Server Database Administrator.

Quote:

---

Originally Posted by 01010011

I was thinking about persuing the MCSD since I suspect that C# is the programming future (please correct me if I am wrong).

---

Where are people hearing this crap? I'm guessing the same people that said VB was going to replace Cobol.

C# was created by MS to help ease the transition of C/C++/Java programmers into the .Net world. Now that it's a buzzword, employers are just throwing it on job descriptions because they don't know what they're actually looking for. This causes schools to teach more Java/C# instead of VB, which sucks for students because VB is a very powerful language on it's own.

Now that I got that out of my system, I must agree with Hack and Rhino. Your certs should match your desired career path.

I see no problem in getting both. Some employers have no idea about computer science. But they know who Microsoft is. Remember the person doing the hiring may my not be a technical person. If it is a technical person I would only be interested in your degree and experience. MCSE and MCSD's are as far as I am concerned just something people buy from Microsoft.

When it comes to the newest MCSD Certs... it doesn't matter ... there's three tracks you can take... the C# Track, the VB Track and the WebDev track.... So you either endup with a MCSD C# or a MCSD VB or MCSD WebDev cert.... but a cert is a cert..... Here's the dark side of it that no one seems to talk much about - the tests are (supposed) to be designed to be aimed at the career developer. Much of what's on the tests are NOT book stuff, but experience type of things - things you'd know by having been there done that.... But it's still possible to pass them w/o any experience what so ever.

Some employers put too much stock in Certs... while some don't consider them at all.

-tg

C# is NOT better then VB.NET. They both are based upon the same framewwork. Sure there are minor differences but vb can do things what c# cant and visa versa.

Forget MCSD as its going to be retired in March. Go for the 2005/2008 MSPD and MCTS, that is if you are looking for a programming job. MCSE is if you are wanting a networking job.

http://www.computerworld.com/action/...rce=rss_news10

Either case, do read this article.

Quote:

---

Originally Posted by ComputerWorld - Frank Hayes

August 18, 2008 (Computerworld) Don't do it. Don't head off to one of the top schools profiled in Computerworld's "IT Schools to Watch" in this week's issue. Don't spend a year in the classroom, or a couple of years of nights and weekends, to get your master's degree. At least, don't do that if your goal is just a bigger paycheck.

If you're just chasing paper, there are better ways to do it.

Yes, an IT-related master's will probably boost your salary. So would an MBA or a law degree. At the least, you can expect it to pay for itself within a few years.

But then, the same used to be true of a whole slew of IT-related certifications.

The process was simple: Study up, fill out the workbook, pass the test. You'd get a new line to add to your résumé and a string of letters to tack onto your e-mail signature -- and, usually, a hefty boost come payday.

Pretty soon, we had a glut of certified test-passers. That's when the value of certifications started to plunge. Employers began to look for practical experience, not just pieces of paper.

Understand, the problem wasn't merely an oversupply of certified IT people. There's a curve to these things. At the start, the people getting certifications wanted to take the next step. They were looking for an opportunity to solve problems others didn't know how to solve, to master a technology in ways their peers couldn't. The certification was just icing; the cake was the knowledge they gained.

The result? They gave certifications a good name. They really were worth more money, even though that wasn't what the people were looking for.

But money attracted the workbook-fillers, the test-passers, the résumé-padders -- the people who just wanted to make a quick investment in a certification that would bump up their salaries. They weren't worth the money. In the end, they gave certs a bad name.

And those master's degrees? Right now, they look good. And they should. The people who have gone back to school in the first wave of IT-related graduate programs want to kick their abilities up a level or two. They have experience, but not the breadth of vision they'd like. They've proved they can solve problems, but they'd like more options.

They want a better grasp of how business and IT intersect and sometimes collide. They want depth, and knowledge, and leadership ability. Most of all, they want an edge that will give them and the people they work with a better chance at both IT and business success.

Yes, they'll make more money. And they'll be worth it. But not because of that piece of paper.

Eventually, that paper will lose its value, too. That'll happen because the money will attract paper-chasers, and we'll end up with a glut of people with IT-related master's degrees -- and nothing else to offer.

So don't do it. At least, don't just do it for the paper -- the diploma and the money.

But if you want an edge at the place where IT and business meet, and you're willing to stretch your knowledge and experience to gain that edge, maybe this is the way for you to get it.

Corporate IT isn't going to get any easier, any less complicated or challenging. We need people who can take it to the next level.

---

:wave:

Don't bother wasting your money. Most developers will get a job regardless of there qualifications because most places have some form of test in there interview process. The best thing to do would be to build a portfolio of programs/theories and send that in with your CV.

If you feel like you want to "Expand" your mind learn C (not C++) and understand pointers. Learn why recursion in any language is a hidden evil and know when to use an iterative process instead. Write a non trivial program that uses GOTO effectively and explain why no other method will work. You should also take a peek at ADA just for ha has and then Lisp.

In fact right now go to amazon and buy joel on software, more joel on software, code complete 2 and pick up every article CC2 recommends. The more you read the more informed you will be. Your first AH HA moment will be when you realize that every programming language has its flaws and the only way to get better is to learn loads of them!

Go me!

Quote:

---

Originally Posted by CodedFire

Don't bother wasting your money. Most developers will get a job regardless of there qualifications because most places have some form of test in there interview process. The best thing to do would be to build a portfolio of programs/theories and send that in with your CV.

If you feel like you want to "Expand" your mind learn C (not C++) and understand pointers. Learn why recursion in any language is a hidden evil and know when to use an iterative process instead. Write a non trivial program that uses GOTO effectively and explain why no other method will work. You should also take a peek at ADA just for ha has and then Lisp.

In fact right now go to amazon and buy joel on software, more joel on software, code complete 2 and pick up every article CC2 recommends. The more you read the more informed you will be. Your first AH HA moment will be when you realize that every programming language has its flaws and the only way to get better is to learn loads of them!

Go me!

---

And what does all that get you? Still a lot of knowledge with no actual practical application of it. At least with a cert it shows that the knowledge is appliable. there is a point where you can know too much... too many different things. It's called being a jack of all trades, master of none. It's one of the reasons I don't do web development, except for fun, I don't do ASP any more... I've decided to stick with one area, VB desktop development, and do it well.

Quote:

---

Originally Posted by CodedFire

Write a non trivial program that uses GOTO effectively and explain why no other method will work.

---

It's a myth... I've never come across a situation in the last 15+ years of VB where a GOTO was the only way. There was always another (usually better) way.

BTW - I learned ADA.... and it wasn't for ha-ha's either.... I used it for exactly 4 months..... and then threw out all that training to learn VB. Go figure. There's nothing wrong with learnign new languages, sometimes it can lead to new ideas.... but becareful.

-tg

Actually i beg to differ. How can you develop functional software if you have only learned one language or if you do not understand certain concepts which where used to design the very OS that you are righting for. The reason the majority of people like the idea that to much knowledge is a bad thing is because they have difficulty learning certain concepts. If you are tasked with refactoring someone elses code to make it use less memory on the stack would it not be important to know why he used a recursive function in the first place as this operation would be the first to look at.

If you are working for a development house that is creating an application and they cannot decide between language X and Y would it not make sense to know the differences between those languages not just the trivial ones. The OP made a comment regarding C# being the way forward. Surely anyone who thinks in this frame of mind would be a prime candidate for learning the differences between languages.

And if you are under the impression that there is always a better implementation than GOTO and have indeed learned ADA surely you would be aware that even ADA, the most scrutinised language availble even has GOTO. Why would the designers leave this in if there was always a better implementation. In fact if you pick up CC2 there is a brilliant example of where GOTO is better in VB of all languages.

Further to this the original white paper that stated that the amount of goto's in an application was proportionate to the amount of errors in said program has been disproved many times.

Go Me Again!

Quote:

---

How can you develop functional software if you have only learned one language

---

Problem was this intent didn't come through in your posting.... but I get your point... some of the tricks I've done over the years comes from my understanding of how ASM (at the time) works.... to the point where it's second nature.... so your point holds water... and I get it. But like I said, that's jsut not how it came across.

Quote:

---

Why would the designers leave this in if there was always a better implementation.

---

Again.... your GOTO comment was in the context of a VB Forum... and we all know how inherently bad THAT can be..... and yet*cringe* there is still is.... But, put in other contexts, it's a different story. It was left in VB (and .NET *shudder* still because.... well, there's a noisy minority out there that for what ever reason couldn't live w/o it.) And I'll concede that a JMP is just about the only way in ASM.

Quote:

---

If you are working for a development house that is creating an application and they cannot decide between language X and Y

---

*sigh* unfortunately some of us don't have that luxury.... otherwise we'd be in the middle of converting to C# :P

Bottom line, my point is that your points didn't (at least in my opin) have the proper context... now they do. ;)

-tg

In my past and current occupation, a certification never made a difference in the hiring process or the bonus/salary increase decisions. Practical experience was by far the major factor we were looking for (I obviously don't mean to indicate that a developer shouldn't take the time to broaden his knowledge base). The only time we actually looked for people with an MS cert was to satisfy a requirement of one of the companies we wanted to represented.

Ah yes context, never my strongest point!