2 minute read
It’s always interesting to me what people decide to write to me about directly versus in forums or as comments here on my blog. Here’s one that I think is definitely of general interest that I got today. I’ve edited a little and scrubbed a few things out of it, as it’s clear that the sender wouldn’t want to be identifiable. (I did leave in the nice things that s/he said about me, though. C’mon, I’m only human!)
I feel the time has come for me to move into a role where I can use these new abilities, but every job posting I come across is either looking for someone strictly admin level (i.e. managing farms, creating new subsites, backups, etc) or is a developer (VB, C#, plus a ridiculous number of other languages not necessary in SharePoint). What advice or tips can you give a Middle Tier Designer such as myself?
Once again, thanks for all your great blog posts! You are a true asset to the SP community.
One of the things I want to help change is this vast misperception that development in the Middle Tier can’t create real solutions of value. There is a tremendous amount of excellent work being done in the Middle Tier every day in many, many places. (There’s also horrible work being done in the Middle Tier *and* in Visual Studio. I’ll say it again: Tools don’t kill SharePoint; bad developers do.)
So where can you go to be a rad Middle Tier developer? Somewhere that is progressive and realizes that big budgets aren’t a sign of success. If you want to be a Middle Tier developer, you need to be able to convince people of the benefits and show them examples. Offer a challenge: Give me and a .NET developer a problem and let’s see how the two of us solve it. Then let’s see which solution stands up better.
The term ‘SharePoint Developer’ has been a misnomer for a long time now. We can’t have a movement around this without doing some work. Get out there and convince people!
So what do *you* think? What’s your advice for this brave soul?