Mixing
Career advice - SharePoint development [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
-2
down vote
favorite
I am a newly graduated computing science student and have taken up role as a sharepoint developer, working with C# and TypeScript.
I enjoy the work but anyone i have spoken to / read online about sharepoint development have said it awful to work with and isn't generally well regarded. I found that working with sharepoint has a few awkward quirks, but what technology doesn't?
I have also heard back from one or two companies that i applied to before i graduated.
My questions are, how well respected is sharepoint development among experienced developers? Is it a viable career path? Should i pursue a new job with the other companies i have heard from while i am still fresh from university?
software-industry career-development
closed as off-topic by Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn Dec 3 '14 at 18:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn
suggest improvements |Â
up vote
-2
down vote
favorite
I am a newly graduated computing science student and have taken up role as a sharepoint developer, working with C# and TypeScript.
I enjoy the work but anyone i have spoken to / read online about sharepoint development have said it awful to work with and isn't generally well regarded. I found that working with sharepoint has a few awkward quirks, but what technology doesn't?
I have also heard back from one or two companies that i applied to before i graduated.
My questions are, how well respected is sharepoint development among experienced developers? Is it a viable career path? Should i pursue a new job with the other companies i have heard from while i am still fresh from university?
software-industry career-development
closed as off-topic by Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn Dec 3 '14 at 18:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn
How would you define viable? Every technology has risks that it may or may not be used in the future, no?
– JB King
Dec 3 '14 at 17:54
I get this was shut down and agree. A better question is what software technologies make the best careers? In regards to just finding work software with lot of business demand but is maybe difficult to work with is a good choice.
– paparazzo
Dec 3 '14 at 18:30
Thanks for your feedback, this is the first question I've posted to stack exchange, please forgive my newbiness
– user30190
Dec 3 '14 at 18:52
There are still people ancient maintaining COBOL systems...and having become a critically endangered skill, gray-haired programmers with the ability remain in demand. That said, considering the hundreds of companies whose business is centered on building new SP applications, you could do well worse.
– tjbtech
May 5 '17 at 23:10
suggest improvements |Â
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
I am a newly graduated computing science student and have taken up role as a sharepoint developer, working with C# and TypeScript.
I enjoy the work but anyone i have spoken to / read online about sharepoint development have said it awful to work with and isn't generally well regarded. I found that working with sharepoint has a few awkward quirks, but what technology doesn't?
I have also heard back from one or two companies that i applied to before i graduated.
My questions are, how well respected is sharepoint development among experienced developers? Is it a viable career path? Should i pursue a new job with the other companies i have heard from while i am still fresh from university?
software-industry career-development
I am a newly graduated computing science student and have taken up role as a sharepoint developer, working with C# and TypeScript.
I enjoy the work but anyone i have spoken to / read online about sharepoint development have said it awful to work with and isn't generally well regarded. I found that working with sharepoint has a few awkward quirks, but what technology doesn't?
I have also heard back from one or two companies that i applied to before i graduated.
My questions are, how well respected is sharepoint development among experienced developers? Is it a viable career path? Should i pursue a new job with the other companies i have heard from while i am still fresh from university?
software-industry career-development
asked Dec 3 '14 at 17:43
user30190
closed as off-topic by Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn Dec 3 '14 at 18:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn
closed as off-topic by Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn Dec 3 '14 at 18:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Chris E, Joe Strazzere, IDrinkandIKnowThings, kevin cline, Telastyn
How would you define viable? Every technology has risks that it may or may not be used in the future, no?
– JB King
Dec 3 '14 at 17:54
I get this was shut down and agree. A better question is what software technologies make the best careers? In regards to just finding work software with lot of business demand but is maybe difficult to work with is a good choice.
– paparazzo
Dec 3 '14 at 18:30
Thanks for your feedback, this is the first question I've posted to stack exchange, please forgive my newbiness
– user30190
Dec 3 '14 at 18:52
There are still people ancient maintaining COBOL systems...and having become a critically endangered skill, gray-haired programmers with the ability remain in demand. That said, considering the hundreds of companies whose business is centered on building new SP applications, you could do well worse.
– tjbtech
May 5 '17 at 23:10
suggest improvements |Â
How would you define viable? Every technology has risks that it may or may not be used in the future, no?
– JB King
Dec 3 '14 at 17:54
I get this was shut down and agree. A better question is what software technologies make the best careers? In regards to just finding work software with lot of business demand but is maybe difficult to work with is a good choice.
– paparazzo
Dec 3 '14 at 18:30
Thanks for your feedback, this is the first question I've posted to stack exchange, please forgive my newbiness
– user30190
Dec 3 '14 at 18:52
There are still people ancient maintaining COBOL systems...and having become a critically endangered skill, gray-haired programmers with the ability remain in demand. That said, considering the hundreds of companies whose business is centered on building new SP applications, you could do well worse.
– tjbtech
May 5 '17 at 23:10
How would you define viable? Every technology has risks that it may or may not be used in the future, no?
– JB King
Dec 3 '14 at 17:54
How would you define viable? Every technology has risks that it may or may not be used in the future, no?
– JB King
Dec 3 '14 at 17:54
I get this was shut down and agree. A better question is what software technologies make the best careers? In regards to just finding work software with lot of business demand but is maybe difficult to work with is a good choice.
– paparazzo
Dec 3 '14 at 18:30
I get this was shut down and agree. A better question is what software technologies make the best careers? In regards to just finding work software with lot of business demand but is maybe difficult to work with is a good choice.
– paparazzo
Dec 3 '14 at 18:30
Thanks for your feedback, this is the first question I've posted to stack exchange, please forgive my newbiness
– user30190
Dec 3 '14 at 18:52
Thanks for your feedback, this is the first question I've posted to stack exchange, please forgive my newbiness
– user30190
Dec 3 '14 at 18:52
There are still people ancient maintaining COBOL systems...and having become a critically endangered skill, gray-haired programmers with the ability remain in demand. That said, considering the hundreds of companies whose business is centered on building new SP applications, you could do well worse.
– tjbtech
May 5 '17 at 23:10
There are still people ancient maintaining COBOL systems...and having become a critically endangered skill, gray-haired programmers with the ability remain in demand. That said, considering the hundreds of companies whose business is centered on building new SP applications, you could do well worse.
– tjbtech
May 5 '17 at 23:10
suggest improvements |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
I have done some Sharepoint development but I mainly specialize in PHP/CMS/LMS solutions and yes a little Wordpress.
First whether or not Sharepoint is a good solution, has a good API, is fun to code, or whatever else is irrelevant. The fact is that there are hundreds/thousands of companies using Sharepoint and many of these would love to have a good Sharepoint developer.
I worked with someone who turned a basic Sharepoint site into a fully functioning (with tons of bells and whistles) employee tracking and PM tool. This saved the company well over $1M in 3 years and worked better than most solutions I have seen.
The fact is that most developers are negative about the Sharepoint API (which is lacking and quirky) only strengthens your employment opportunities. There is nothing wrong with coding niche systems at all.
I have found that if a company goes this route and has a great developer they never stop using that crappy platform. But if they have poor developers they will move to something else quickly.
So if you are good you will have long-term employment if you want to keep doing that - maybe really long-term. I don't know how many developers my company has doing legacy stuff. These guys who wrote code in the late 90s and still supporting it. Yes eventually their stuff will be replaced. But guess what? They will be needed during the switch and quite possibly will know new code better than anyone.
My advise is that there is nothing at all wrong with being a Sharepoint developer. However please allot a good amount of time staying current with the industry/methodology that you want to be a part of in the future. Often doing this will allow you to take newer methodologies and implement them into sometimes older/not-quite-as-good APIs.
answered Dec 3 '14 at 17:59
blankip
19.9k74781
suggest improvements |Â
up vote
-1
down vote
Well regarded software and viable career are not the same.
SharePoint development is quirky. But it is popular at the business level so there is a demand for developers. The business will often get into a SharePoint site and get so far and discover they need to bring in a developer. SharePoint is marketed very successfully but many customer underestimate the amount of development required so it creates demand for developers.
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
suggest improvements |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
I have done some Sharepoint development but I mainly specialize in PHP/CMS/LMS solutions and yes a little Wordpress.
First whether or not Sharepoint is a good solution, has a good API, is fun to code, or whatever else is irrelevant. The fact is that there are hundreds/thousands of companies using Sharepoint and many of these would love to have a good Sharepoint developer.
I worked with someone who turned a basic Sharepoint site into a fully functioning (with tons of bells and whistles) employee tracking and PM tool. This saved the company well over $1M in 3 years and worked better than most solutions I have seen.
The fact is that most developers are negative about the Sharepoint API (which is lacking and quirky) only strengthens your employment opportunities. There is nothing wrong with coding niche systems at all.
I have found that if a company goes this route and has a great developer they never stop using that crappy platform. But if they have poor developers they will move to something else quickly.
So if you are good you will have long-term employment if you want to keep doing that - maybe really long-term. I don't know how many developers my company has doing legacy stuff. These guys who wrote code in the late 90s and still supporting it. Yes eventually their stuff will be replaced. But guess what? They will be needed during the switch and quite possibly will know new code better than anyone.
My advise is that there is nothing at all wrong with being a Sharepoint developer. However please allot a good amount of time staying current with the industry/methodology that you want to be a part of in the future. Often doing this will allow you to take newer methodologies and implement them into sometimes older/not-quite-as-good APIs.
answered Dec 3 '14 at 17:59
blankip
19.9k74781
suggest improvements |Â
up vote
2
down vote
I have done some Sharepoint development but I mainly specialize in PHP/CMS/LMS solutions and yes a little Wordpress.
First whether or not Sharepoint is a good solution, has a good API, is fun to code, or whatever else is irrelevant. The fact is that there are hundreds/thousands of companies using Sharepoint and many of these would love to have a good Sharepoint developer.
I worked with someone who turned a basic Sharepoint site into a fully functioning (with tons of bells and whistles) employee tracking and PM tool. This saved the company well over $1M in 3 years and worked better than most solutions I have seen.
The fact is that most developers are negative about the Sharepoint API (which is lacking and quirky) only strengthens your employment opportunities. There is nothing wrong with coding niche systems at all.
I have found that if a company goes this route and has a great developer they never stop using that crappy platform. But if they have poor developers they will move to something else quickly.
So if you are good you will have long-term employment if you want to keep doing that - maybe really long-term. I don't know how many developers my company has doing legacy stuff. These guys who wrote code in the late 90s and still supporting it. Yes eventually their stuff will be replaced. But guess what? They will be needed during the switch and quite possibly will know new code better than anyone.
My advise is that there is nothing at all wrong with being a Sharepoint developer. However please allot a good amount of time staying current with the industry/methodology that you want to be a part of in the future. Often doing this will allow you to take newer methodologies and implement them into sometimes older/not-quite-as-good APIs.
answered Dec 3 '14 at 17:59
blankip
19.9k74781
suggest improvements |Â
up vote
2
down vote
up vote
2
down vote
I have done some Sharepoint development but I mainly specialize in PHP/CMS/LMS solutions and yes a little Wordpress.
First whether or not Sharepoint is a good solution, has a good API, is fun to code, or whatever else is irrelevant. The fact is that there are hundreds/thousands of companies using Sharepoint and many of these would love to have a good Sharepoint developer.
I worked with someone who turned a basic Sharepoint site into a fully functioning (with tons of bells and whistles) employee tracking and PM tool. This saved the company well over $1M in 3 years and worked better than most solutions I have seen.
The fact is that most developers are negative about the Sharepoint API (which is lacking and quirky) only strengthens your employment opportunities. There is nothing wrong with coding niche systems at all.
I have found that if a company goes this route and has a great developer they never stop using that crappy platform. But if they have poor developers they will move to something else quickly.
So if you are good you will have long-term employment if you want to keep doing that - maybe really long-term. I don't know how many developers my company has doing legacy stuff. These guys who wrote code in the late 90s and still supporting it. Yes eventually their stuff will be replaced. But guess what? They will be needed during the switch and quite possibly will know new code better than anyone.
My advise is that there is nothing at all wrong with being a Sharepoint developer. However please allot a good amount of time staying current with the industry/methodology that you want to be a part of in the future. Often doing this will allow you to take newer methodologies and implement them into sometimes older/not-quite-as-good APIs.
answered Dec 3 '14 at 17:59
blankip
19.9k74781
I have done some Sharepoint development but I mainly specialize in PHP/CMS/LMS solutions and yes a little Wordpress.
First whether or not Sharepoint is a good solution, has a good API, is fun to code, or whatever else is irrelevant. The fact is that there are hundreds/thousands of companies using Sharepoint and many of these would love to have a good Sharepoint developer.
I worked with someone who turned a basic Sharepoint site into a fully functioning (with tons of bells and whistles) employee tracking and PM tool. This saved the company well over $1M in 3 years and worked better than most solutions I have seen.
The fact is that most developers are negative about the Sharepoint API (which is lacking and quirky) only strengthens your employment opportunities. There is nothing wrong with coding niche systems at all.
I have found that if a company goes this route and has a great developer they never stop using that crappy platform. But if they have poor developers they will move to something else quickly.
So if you are good you will have long-term employment if you want to keep doing that - maybe really long-term. I don't know how many developers my company has doing legacy stuff. These guys who wrote code in the late 90s and still supporting it. Yes eventually their stuff will be replaced. But guess what? They will be needed during the switch and quite possibly will know new code better than anyone.
My advise is that there is nothing at all wrong with being a Sharepoint developer. However please allot a good amount of time staying current with the industry/methodology that you want to be a part of in the future. Often doing this will allow you to take newer methodologies and implement them into sometimes older/not-quite-as-good APIs.
answered Dec 3 '14 at 17:59
blankip
19.9k74781
edited Dec 3 '14 at 18:06
answered Dec 3 '14 at 17:59
blankip
19.9k74781
answered Dec 3 '14 at 17:59
blankip
19.9k74781
answered Dec 3 '14 at 17:59
blankip
19.9k74781
19.9k74781
suggest improvements |Â
suggest improvements |Â
up vote
-1
down vote
Well regarded software and viable career are not the same.
SharePoint development is quirky. But it is popular at the business level so there is a demand for developers. The business will often get into a SharePoint site and get so far and discover they need to bring in a developer. SharePoint is marketed very successfully but many customer underestimate the amount of development required so it creates demand for developers.
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
suggest improvements |Â
up vote
-1
down vote
Well regarded software and viable career are not the same.
SharePoint development is quirky. But it is popular at the business level so there is a demand for developers. The business will often get into a SharePoint site and get so far and discover they need to bring in a developer. SharePoint is marketed very successfully but many customer underestimate the amount of development required so it creates demand for developers.
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
suggest improvements |Â
up vote
-1
down vote
up vote
-1
down vote
Well regarded software and viable career are not the same.
SharePoint development is quirky. But it is popular at the business level so there is a demand for developers. The business will often get into a SharePoint site and get so far and discover they need to bring in a developer. SharePoint is marketed very successfully but many customer underestimate the amount of development required so it creates demand for developers.
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
Well regarded software and viable career are not the same.
SharePoint development is quirky. But it is popular at the business level so there is a demand for developers. The business will often get into a SharePoint site and get so far and discover they need to bring in a developer. SharePoint is marketed very successfully but many customer underestimate the amount of development required so it creates demand for developers.
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
answered Dec 3 '14 at 18:06
paparazzo
33.3k657106
33.3k657106
suggest improvements |Â
suggest improvements |Â
How would you define viable? Every technology has risks that it may or may not be used in the future, no?
– JB King
Dec 3 '14 at 17:54
I get this was shut down and agree. A better question is what software technologies make the best careers? In regards to just finding work software with lot of business demand but is maybe difficult to work with is a good choice.
– paparazzo
Dec 3 '14 at 18:30
Thanks for your feedback, this is the first question I've posted to stack exchange, please forgive my newbiness
– user30190
Dec 3 '14 at 18:52
There are still people ancient maintaining COBOL systems...and having become a critically endangered skill, gray-haired programmers with the ability remain in demand. That said, considering the hundreds of companies whose business is centered on building new SP applications, you could do well worse.
– tjbtech
May 5 '17 at 23:10