Looking For a Skilled SharePoint Developer and Architect? I’m Available This Summer

Due to some changes in plans and priorities, I’m looking for project or contract work within the field of, you guessed it, SharePoint. If you need or know someone who needs an experienced and skilled SharePoint developer/architect for 3-6 months, then feel free to let me know.

I’m not looking for a permanent position and won’t consider that regardless of offer. My rate is $200/hour, negotiable only for longer term projects (3+ months).

I can start almost immediately (early June) and will be available until around October 2012. However, for US clients, I can only work onsite in the US for up to three months due to VISA requirements. EU is no problem because I am a  Norwegian citizen. Other parts of the world varies.

Although I’m looking for work, I’m by no means desperate, so I will turn down offers that are not interesting.

Interesting work, however, would be along the lines of:

  • Technical training and mentoring for SharePoint developers
  • Solution architecture, SharePoint or otherwise
  • SharePoint 2013/15 evaluation/exploration
  • Evaluating ROI for existing or new projects

If you have or know of projects that might fit, feel free to email me at furuknap+summer2012job@gmail.com.

Here’s an excerpt from my resume:

Bjørn Furuknap

Senior solutions architect and SharePoint developer. Professional speaker and published author. USPJ Academy faculty member. Lead Editor SharePoint Magazine.

In 5 sentences

  • Senior solutions architect and developer with 16 years of experience
  • Published book author (18 books and journals) and online writer, community speaker
  • Multiple fields of expertise, including technical, marketing, and business
  • Actively working as teacher in online SharePoint university
  • Business advisor with good economic understanding

Skills

  • Expert in Windows SharePoint Services 3
  • Expert in SharePoint Foundation 2010
  • Expert in SharePoint Server 2010
  • Expert in C# development and ASP.NET
  • Strong in ASP.NET MVC and Entity Framework
  • Strong in Windows Servers, from NT4 to 2008
  • Strong in Windows infrastructure. (MCSE completed in one week)
  • Strong in Microsoft Office SharePoint Server 2007
  • Strong in XML and related languages
  • Strong in SQL server and SQL
  • Strong in Perl, VB.NET, and .NET
  • Strong in Server hardware design
  • Strong communication skills, towards both technical and business audiences
  • Working knowledge of several other languages such as C++, Java, ASP, and JavaScript/jQuery/jQueryUI.
  • Working knowledge of most Microsoft infrastructure products, such as SCM, MOM, and SMS.
  • Working knowledge of network design.

References

All references by request only. References will be chosen based on project requirements. Please note that most references will be Norwegian customers speaking English, but that due to time zone differences some may not be available for direct contact.

Why should you hire me?

I have extensive experience within several fields of IT, both from developer and IT pro areas. My education and experience as an entrepreneur means I also see the business side of IT. Combining these areas means I recognize problems both for developers and administrators and can work with both camps to resolve issues. With my experience from running and managing businesses I can add and present real business value from the projects in which I participate.

From my role as an architect in recent years, I have also gained experience with Agile methodologies and can lead teams of both developers, designers, and administrators using Agile methodology. I have also worked with both small and medium size businesses, as well as multi-national companies with thousands of employees around the world.

My active participation in online communities as well as my high visibility in the SharePoint community means I get access to new knowledge very fast. I love learning whatever I do not already know, and gladly share that knowledge both online and offline.

Further, my recent ventures into online training through USPJ Academy increase my ability to transfer knowledge to colleagues, team members, clients, and management. I have also been the principal business architect for the USPJ Academy organization, including developing business plans, optimizing processes in the organization, hiring and training staff, and mentoring C-level staff in the organization.

I work very hard and have a strong sense of loyalty. I have never been away from work a single day of my life.

Found this article valuable? Want to show your appreciation? Here are some options:

a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.

b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.

c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!

Pin It

Visual Studio 2012 – It’s Named

A few weeks back, I wrote a speculative post about the release date of Office 15 and SharePoint 15. In it, I referred to an Austrian SharePoint conference that used the name Visual Studio 2012.

In a comment, the organizers said something along the lines of the name being a mistake, but it now seems that, mistake at the time or not, Microsoft has now decided on the name.

While searching for something on MSDN, I found an article written for Visual Studio 2003, and although I don’t necessarily rush to adopt the latest and greatest tools, in this case, I needed something more recent. So, when selecting which version to view, I found the below screenshot, clearly stating that the name for the next version of Visual Studio, currently codenamed Visual Studio 11, is indeed Visual Studio 2012.

visualstudio2012

According to Google cache on May 20, it was still called Visual Studio 11 at the time, so change is fairly recent. Maybe this in preparation for official news in early June, although I haven’t heard anything related to this.

visualstudio11

Now, all we need to do is wait to see what the official name for Office 15 and SharePoint 15 will be, and I’ll be happy as a fiddle in heat.

.b

Pin It

SharePoint 2013/SharePoint 15 to run on .NET 4.0 Runtime

I’ve been keeping hundreds of subscribers updated on what’s going on in the SharePoint 2013 news scene over the past few months. In addition, I’ve been deep diving into the released protocol documentation to describe new features of SharePoint 15.

If you’re interested in obtaining a subscription, priced at $14.95 for the entire series (monthly issues, 25-35 pages each), head over to http://sharepoint2013beta.com/.

Regardless of the paid options, I’ve been posting information on SharePoint 2013 on my blog too, so feel free to check out the SharePoint 2013 tagged articles for updates.

This excerpt appeared in issue 4, published in early April 2012.


SharePoint 2013 uses .NET 4.0 Runtime – Prepare Yourself!

In the previous issue, I wrote about my thoughts and findings around the .NET version of SharePoint 2013. As you may remember, my conclusion was that I thought Microsoft would leave the current .NET version alone and go with the 2.0 runtime.

(Web note: In the March issue, I speculated that Microsoft would want to maintain a single .NET runtime version for all its SharePoint versions. At the time, I did not have any hard facts, so I elaborated on the reasoning behind the argument)

Right after I published the previous issue, a reader tipped me that, although the reader thought my reasoning was correct, the conclusion was wrong. According to the tip, SharePoint 15 runs on .NET 4.0.

Now, I considered emailing all subscribers immediately, but I wanted to verify the claims of the tipper. Sadly, I haven’t been able to accurately do so, and the people who know are keeping their lips more tightly sealed than ever.

Note: Since publishing the April issue, several other readers have said the same thing, including one person ‘in-the-know’ confirming that SharePoint 2013 is based on .NET 4.0 Runtime.

Assuming that my reader is correct, and I have no doubt that this is the case, this is a huge deal for SharePoint developers, both for those that work on projects and for component developers.

If you’re completely foreign to development, you can view the following discussion as one of compatibility between two versions of the .NET runtime. The .NET runtime is responsible for executing the code that developers write to interact with SharePoint.

Despite there being numerous .NET Framework versions, there are only two runtime versions, .NET 2.0 and .NET 4.0. The problem arises from the fact that .NET 4.0 is backward compatible, with some major caveats for SharePoint developers, and that .NET 2.0 is not forward compatible.

Let’s look at what this means for future developers.

First, because SharePoint 2013 requires .NET 4.0, and .NET 2.0 won’t run .NET 4.0 code, this means that any code written to interact with SharePoint 2013 will not work on previous versions. This means that developers who want to support both current and future versions of SharePoint will need to maintain two sets of code.

So, why can’t you just run the current .NET 2.0 code in the .NET 4.0 runtime? After all, I did mention that .NET 4.0 is backwards compatible. If you write your code for .NET 2.0, you could simply load that code into the .NET 4.0 runtime and you’d be set, right?

It’s not that simple, I’m afraid. Microsoft, in its infinite wisdom, has added code to explicitly prevent SharePoint 2010 to work with .NET 4.0 runtime. SharePoint 2007 simply won’t work and you will not be able to connect to any site if you use .NET 4.0.

Finally, because .NET 2.0 can’t load .NET 4.0 code (it’s not forward compatible, remember?) you also cannot write.NET 2.0 code to connect to SharePoint 2013.

These conditions mean that you will have two distinct development platforms; one that targets SharePoint 2010 and 2007, and one that targets 2013 and future versions. (At least until Microsoft puts a new runtime version out and upgrades SharePoint 2016 to that :-) )

Obviously, this impacts the cost of development of new code that attempts to work on both SharePoint 2013 and earlier versions. Technically, you can write code that is simple to switch between .NET 2.0 and .NET 4.0. If you wrote only code that worked in both versions, it would simply be a matter of changing the target framework in Visual Studio and recompile.

However, reality won’t be that easy. If you start doing development on .NET 4.0, you want to take advantage of the added benefits of that version. Otherwise, what would be the point? Well, if you do, you’ll have to maintain two different versions of your codebase and make sure that any changes you make are added to both versions. Although there definitely are methods you can use to make your code more portable, it will still increase the burden on developers and ultimately the cost to customers.

Of course, it may be that Microsoft has some tricks up their sleeves, but considering the minor but significant incompatibilities between the various .NET runtimes and SharePoint, I’d much rather prepare for the worst and assume it will be two separate target environments from now.

.b


This has been an excerpt from the SharePoint 2013 Beta series of USP Journal. To pick up a subscription that costs $14.95, including access to all back issues, head over to http://sharepoint2013beta.com/

As always, treat any unofficial information as pure speculation and don’t make any important decisions based on this.

Pin It