4 ms·

Absolutely spot on, and I have exactly the same experience. What completely baffled me when I did quite a bit of SharePoint development of late is, that you ar

Absolutely spot on, and I have exactly the same experience. What completely baffled me when I did quite a bit of SharePoint development of late is, that you are essentially doing web application development, except everything you know about web development is somehow not valid anymore because it has been buried under layers and layers of abstraction. So you have to go on at least one SharePoint development course, to re-learn web development as you know it.

DanielBMarkham 13y ago
Several years back I had a friend with a small business who wanted to do some SharePoint stuff, so I picked up 3 or 4 books on it and read them all. Oh. My. God. That tool will solve world hunger, land a fighter on a carrier deck at night in a storm, and compute the answer to life, the universe, and everything. It does frickin' everything. So it also does nothing. You end up having to digest a huge learning curve, creating all these specialty libraries to handle workflows, understanding that you need a view for this, a link for that. It's like having to learn Klingon just to get a cup of water. Whenever I hear SharePoint any more, I just smile. It's a great tool, and it can do an incredible ton of stuff. I just know the pain that's involved with it, and unless I have no choice I want no part in it -- except for maybe using it as a document repository, and even then Dropbox does all I want with zero learning curve. Microsoft is constantly distracting me with the coolness of their tools instead of enabling me to quickly solve somebody else's problem. The developer has become the market for them -- and that's really bad for both developers and end users.
- martijn_himself 13y ago
  Thank you very much, those comments made my day :). I very much share the sentiment. I am developing in SharePoint and I am sometimes impressed at what it can do; however lately I have been thinking of jumping ship and start developing small business applications (in Golang) that solve user problems quickly and iteratively.

DanielBMarkham 13y ago

Several years back I had a friend with a small business who wanted to do some SharePoint stuff, so I picked up 3 or 4 books on it and read them all. Oh. My. God. That tool will solve world hunger, land a fighter on a carrier deck at night in a storm, and compute the answer to life, the universe, and everything. It does frickin' everything. So it also does nothing. You end up having to digest a huge learning curve, creating all these specialty libraries to handle workflows, understanding that you need a view for this, a link for that. It's like having to learn Klingon just to get a cup of water. Whenever I hear SharePoint any more, I just smile. It's a great tool, and it can do an incredible ton of stuff. I just know the pain that's involved with it, and unless I have no choice I want no part in it -- except for maybe using it as a document repository, and even then Dropbox does all I want with zero learning curve. Microsoft is constantly distracting me with the coolness of their tools instead of enabling me to quickly solve somebody else's problem. The developer has become the market for them -- and that's really bad for both developers and end users.

martijn_himself 13y ago
Thank you very much, those comments made my day :). I very much share the sentiment. I am developing in SharePoint and I am sometimes impressed at what it can do; however lately I have been thinking of jumping ship and start developing small business applications (in Golang) that solve user problems quickly and iteratively.