Geek Answers Handbook

Disconnect from SharePoint

Have you ever tried to run from sharepoint? I have worked with sharepoint enough to know that this does not interest me. My interests are more consistent with the principles of API / backend / distributed development. Have any of you found, as consultants, an opportunity to move away from sharepoint and continue to explore other things of interest? I am now in a position where sharepoint is in great demand, and I can’t find a way to simply abandon it. any suggestions?

+6
sharepoint
source share
10 answers

If I correctly formulate that you work in a consulting firm, then find out what other things your firms work. Learn these technologies better than the people who currently work for them for your company, attract themselves to these projects, even if they are on the talk line in the corridor, and come up with better (faster, cheaper) solutions to the problems that your firm.

Your options really seem 3x

  • convince your boss your talents are best used elsewhere
  • convince your colleagues they want you in other teams
  • to convince your company customers that they want you in particular.
+7
source share

Learn Java or Ruby.

Microsoft's “attach” sales model, through which they sell a solution consisting of several technologies, and then sell the next solution based on “it’s good that you have already invested in SharePoint, so you already have the skills and infrastructure for this new bit of technology we have have "to stay ... it is very successful.

SharePoint is cloud computing for businesses that have MS stores ... you avoid this without doing C #. If you are doing C #, then you have enough time, your applications will have to run in the corporate cloud, and you should monitor your career by hugging it.

Just my 2p. Sorry if this is not exactly the answer you need.

+6
source share

I know exactly what you mean. I think you do not mind the idea of ​​a product like SharePoint, but you really hate the way it is implemented and how problematic it is. I know his nightmare for work.

As a C # developer, I compress when I hear the word SharePoint, SharePoint - Lord Voldemort. But, unfortunately, this is due to the fact that he is a senior C # / Microsoft developer.

I say, unfortunately, because most likely, if you work in a corporate structure sooner or later, you will have SharePoint in your solution. Not because it's good, but because, as others have said, MS uses SharePoint as a Trojan horse to get and maintain a business.

Perhaps there is hope for a new version of SharePoint (2010). Perhaps this finally includes a better programming / implementation model.

Otherwise, either work in small companies (usually less, but not always), or try, if possible, to use your skills as a MOSS developer. Never actively sell them if your salary does not depend on this. Remove the skill from your workshop and cancel jobs that are fully focused on MOSS. Some MOSS integration here and there you can live. The entire MOSS-centric solution will put you in a crazy state.

If all else fails, learn languages ​​other than Microsoft, and within a year or 2, SharePoint will be just a faded memory.

I know many developers who are thinking about abandoning IT because of SharePoint. I would say not to let this end your career.

And finally, bitch and moan, and let managers know weekly / daily about why you are struggling in SharePoint. Let them know and constantly remind them how bad the technology is.

+4
source share

When life touches you with lemons. Make lemonade.

Seriously, if you see SharePoint in such high demand, perhaps working with a beast is the best idea. SharePoint is really average software. SharePoint may simply be the distribution point for your solutions (for example, a user interface such as a web application can be hosted in SharePoint through a portion of the web content). If you look at this, SharePoint might be useful as a document repository or a small data warehouse in the form of lists.

+2
source share

Perhaps you should refuse the contracts of SharePoint and accept the contracts interesting you.

+1
source share

Depending on which market you are in, you can simply tell your boss at the consulting company you work for so that you are no longer interested in Sharepoint projects and that you will be forced to look elsewhere if they continue invest you in Sharepoint projects. This will work around Western Michigan, where the demand for the developer is high and the supply is sub-par.

+1
source share

I'm, on the other hand, just starting to use SharePoint to cover my boring C # projects. I am starting to use it as an interface for distributed and complex systems: simple setup and configuration, reporting, management, system control - it seems that all this is available in this package, which is easy to do for technicians and beginners.

0
source share

I personally no longer want to work with SharePoint. I worked on developing a solution for it and even fully charged web integration. I hated it.

First you need to master the terrible programming model, and then handle all the deployments, and that didn't even start. If you are developing a product for SharePoint, you need to debug the software itself, which is its feat.

My solution for this is to be very frank. I do not mind doing knowledge transfer and helping people, but I do not want to develop / deploy SharePoint applications.

My boss will get it, my friends will get it.

Our last joke comes from someone who said a few months ago that “simply and quickly deploying an application with SharePoint” was quick and easy. Joke? "Did he just put / quick in the same sentence as SharePoint?"

So, if you haven’t lowered your salary because of this ... downplay your skills and be ready for your boss. :)

0
source share

Have you ever watched Alfresco ( http://alfresco.com )?

It serves many of the same purposes as SharePoint, but does so from the Open Source J2EE application. He will use your collaboration / content management experience and provide you with a whole bunch of open source technologies.

Full disclosure: I work for Alfresco.

0
source share

I already gave this offer to another guy ... Running from SharePoint is not difficult, because the technologies are similar to each other in accordance with their structure. SharePoint is not the worst technology to use, although it is somehow limited ... Fortunately, the scope of the software is too wide not to be afraid to find anything that might interest you.

0
source share

More articles:


All Articles