Related
I know that SuiteScript is the NetSuite platform built on JavaScript that enables complete customization and automation of business processes.
I want to know that SuiteScript is in demand? How would be the future if I do following certifications
SuiteFoundation Certification
SuiteCloud Developer Certification
I've worked with NetSuite development (SuiteScript 1.0 & 2.0, administration, and integrating NetSuite to many other systems) for about seven years now. I have no NetSuite certifications, and I have never found a need for them.
That being said, some employers think highly of certifications. Whether you need the certs really depends on whether you can be self taught and whether the company you want to work for wants you to have them before you are hired.
I have been working on NetSuite for 4 years now. I have done SuiteScript 1.0, 2.0, workflows, searches, reports, etc (all normal admin and developer tasks with NetSuite basically). I am now certified Developer (meaning I passed the 2 exams you mentioned) and because I am a consultant I am now a certified ERP consultant as well. I will probably take the analytics, admin, and eventually SuiteCommerce as well.
So with that background, the answer to your question depends on what you want to do. If you are already working with a company who is using NetSuite, an end client probably doesn't care a ton about the certifications. If you are looking to get a job in this, then it may help you a lot. If you are looking to be a consultant, it will probably be a requirement at some point. For consulting companies, certifications help them look better to clients.
I also will add that I find that by studying for and taking the tests I have learned about features I did not have exposure to prior. This pushes me to learn those areas, talk to others, and better my overall skills beyond the exam itself. If you are only self taught, in my experience, you eventually fall into the "if your own tool is a hammer, than every problem looks like a nail". You won't have all the possible tools to do the best job
I personally found my certifications valuable. Last year, I completed the SuiteFoundation and Administrator exam, both of these guided me into different segments of NetSuite I had never used before.
I'm currently studying for the SuiteCloud developer exam, and I've had the same experience. It's forcing me to look into new modules and test out new functionality. With that being said, I'm a jr. level developer at best, so combining my js training with NetSuite-specific training is relevant.
There is a solid website that recently did a informal survey on this topic, if you want to learn more about value added from NS certifications you can visit: https://netsuite.smash-ict.com/
I recommend all NS newbies to complete the SuiteFoundation training. This applies to everyone, developers, admins, and end-users.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am a Asp.Net developer, currently working on Webforms in 3.5. I do C# now, used to do VB.Net. I am also a middle tier developer (business layer and data layer) working on refactoring the current code base to use the Service-Repository pattern.
My boss asked me if I would like to start doing Sharepoint development (company is currently upgrading to 2010, so I would assume I would be doing 2010).
I have read on here that it takes a long time to get up to speed with Sharepoint development, and I don't want to be thrown into the fire while still learning and not knowing what I am doing.
Also, any good places to start learning? I told my boss I would look into it for about a week and get back to them.
Some good links:
Get Started on developing on
SharePoint 2010
SharePoint 2010 Advanced Developer
Training
SharePoint Hands on lab
SharePoint Developer Center
SharePoint Foundation Development in
Depth
Good luck to you
I'd recommend finding out what they anticipate the company's needs are and whether they anticipate that this will become your primary role. Ask about what projects they have in mind. (Of course they're going to say a small percentage, and no, you'll be expected to continue with your regular duties...)
It may be helpful to schedule a 'state of the union' meeting a couple months out to realistically assess how much of your life Sharepoint has taken over, and whether someone else should be brought in to help (or take over).
It certainly can't hurt to get another set of skills under your belt. Having the background that you do will certainly help you be competitive. If you don't like the work, there's nothing saying that you have to include it in future resumes...
Don't be scared to learn SharePoint. It may seem like a difficult task at first, but if you take it one step at a time you should be ok. In fact, SharePoint is just a (really big) asp.net web application, so all your existing skills come in handy.
Also the fact that MS finally put some good quality project templates for SharePoint development in Visual Studio 2010 makes the learning curve less steep.
There are also some good books available to get you started. If the company wants you to learn SharePoint, I suppose they would be happy to pay the bill for those. :-)
Yes, SharePoint development has a steam learning curve, but from what you already do, you're half way there.
The best place to start is here:
http://channel9.msdn.com/learn/courses/SharePoint2010Developer/
I agree with the answers above. Only thing I would add is, if you had to learn SharePoint, starting with the 2010 version such an advantage over 2007. Especially when you add in Visual Studio 2010...
Regarding where to start, can't hurt learning from the horse's mouth (i.e Microsoft's MSDN sites). Also, be sure to request that your company get you adequate hands-on developer training.
It might be helpful to know that SharePoint.SE is dedicated to only SharePoint questions. If you have a non-programming related SharePoint question, or even a programming one, that is a good site to use.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
Right now, our teams are using a combination of a bulletin board and an excel spreadsheet to keep track of tasks and to draw a burndown chart. Backlogs are keep on index cards in envelopes.
This works well when the stakeholders are in the same location. However, we will soon have Scrum teams in two geographically distant locations and I am looking for best practices on how we can leverage Sharepoint to help us communicate around Scrum artifacts (backlog, burndown chart, velocity, etc.).
How did you leverage Sharepoint for that purpose, what are the best practices and the potential pitfalls?
We actually use Sharepoint for our Agile development and have found it works pretty well for project management/collaboration.
There are 2 things we do which I found particularly useful, metrics tracking and automated testing. We use the document library and infopath to add all of our stories for the project to the site. The infopath form should contain all the information you need for a story: points, estimated time, developer, tester, story tasks, test cases.
For metrics, we create web parts for: burn down charts, velocity, points per iteration, etc.
This is especially nice for Managers or customers to see that progress being made on the project and will help them make decisions regarding features vs. release time.
For testing we have a simple SEND-RECV-ASSERT language which runs the tests nightly by scraping the XML for automated tests. The we have a little Green/Red webpart on the main page which tells you the stat of the tests.
This can be done pretty simply with some XML parsing since the backend of the document library is XML. (We currently use some simple ActiveX and javascript)
The metrics are pretty easy to set up (just some xml parsing and html charting). The automated testing takes some time to set up a test runner, but once its in place, and easy enough, you can even have customers/managers write acceptance tests! Agile! :)
If you have SharePoint in house already,along with a user base that is comfortable using it I think it would be fairly easy to get started with using it for SCRUM. I would start with the following:
A site collection to hold 1 scrum site per project
A scrum site should contain:
Document library for the electronic files (add columns for categorization as appropriate)
List of team members
Discussion board
The site can be built from a Wiki site template if its necessary.
Once you get the scrum site "feeling right" save it as a template so its easy to spin up a new one.
This solution may not be designed for SCRUM to the nth degree, but it should be enough to get you started. It seems a lot easier than having the entire team learn a new tool when it sounds like you are undergoing some other pretty radical changes.
my $0.02
jt
You really should consider something like Trello, VersionOne, Rally, or even Basecamp for this. They all have hosted solutions and offer free community versions that you can try out to get started. My experience with SharePoint is that it takes a lot of resources to maintain. If you were using Team System and had a lot of the stuff pre-built for you, that might be different -- although I have Team System and still choose to use a Wiki for my project management tasks. If you already have an investment in SharePoint as an intranet and all of the support staff, then it might be a viable solution in that case, too.
SharePoint is not the tool I would think of first for agile development. YMMV.
You need to try and keep the tool from getting in the way of working. In an ideal world the team will all be sat in a single room with big white boards, however often this is not the case and teams are distributed, or theres a push for some form of backup for the post-its.
I'm a big SharePoint fan and where you have this in house already, your already doing collaboration and team work on the platform. Adding another tool, with unique login's can work but the team need to really want to use them.
I've tried getting SharePoint out of the box to do what I wanted but it fell short. I've tried using Version One (on a number of occasions over many years, with many teams) but I find the tool is too much, there are too many otpions and things that need to be done that it gets in the way - it is a long way from the Whiteboard.
So I decided to develop what I needed for my projects. I needed a simple tool, and using the 37signals (creators of basecamp) approach I needed something with less features than the competition.
21Scrum is a simple scrum tool built on SharePoint that uses the platform, add the things that you need (white board, burndown charts) and leave you to get on with the project.
Perhaps this may be the best option for people who already have and use SharePoint - at least thats the goal.
We've setup a SharePoint workspace with lists for Release/Sprint planning, Product Backlog and Sprint Backlog.
Central element is this Task Board for SharePoint - we can drag & drop stories and tasks - even if we are not at the same location.
http://www.youtube.com/watch?v=XW89M0C3N7Q
A burndown report visualises the progress automatically.
Works great!
AFAIK, Sharepoint is ASP.net with free goodies. It is not designed for agile project management.. so you'd have to roll your own site.
IMHO instead of trying to bend the job to the tool you have.. switching to a better tool for the job would be a better option. Check this thread out to see if there is something more lightweight that fits your bill.
Also personally I'm a big fan of not digitizing the development activities.. So I'd use a spreadsheet for the backlog and post its and Big Visible charts. Use a digicam to persist diagram/design discussion snapshots (google whiteboard photo for tools) or for reports. I find that most of the "project management" tools are just excuses for generating instant status updates.. it gets in the way of software development (which is the main goal) and inhibits social interaction way too often.
(disclaimer: absolutely 0 experience with sharepoint.. except what I've read in the last 2 days so may be totally off track)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
So, my question is how do people get the word out that their website or blog exists? Do blogger invest in ads? Is is just through word of mouth? Or searching Google? I'm just curious how does a website build it's popularity. Do you just put your website up on the web and hope people find it? I know you can make your site SEO friendly, create sitemaps and such but what other techniques are used?
Thanks,
John
The big thing is, build a good site! have good quality relevant content. SEO and page linking will help. Most search traffic comes from Google imho. I would suggest
http://www.google.com/webmasters/start
Submite a sitemap would be high on my todo list.
Also Use relevant and unique - page titles, Friendly urls and relevant H1 tags
Hope that helps
My blog has been running for about a year and a half. I tried some tricks or tips on promotion that I read from around the Internet. Sure, you can get some activity bursts from promotion on other places, but I've found that the number one factor for a blog is simply to have good quality content. You can trick people into visiting with clever reddit or digg titles, but they'll never turn into repeat visitors. With quality posts, the search engine and referrer inflow will be steady.
If you only blog for popularity or money, and don't really care about putting out worthwhile content, it will show, and the people will not visit your site. I changed pretty early on from quantity over quality to quality over quantity. After all, ask yourself: wouldn't you rather subscribe to a blog that gave you a great read once a month rather than a blog that flooded your reader inbox with shallow, forced posts?
Among hobbyists, the usual approach is to make a polite announcement on related forums, and when a subject comes up on a forum or blog that you have addressed on your blog or web site, include a link as a part of your response.
Among professionals, advertising, advertising, advertising.
This thread at Hacker News is a good starting point.
Well, this site was started by Jeff Atwood and Joel Spolsky (if I'm correct), so they both mentioned it on their blogs. Then they asked for people on those blogs to join the beta version. By the time the live version came out, people were already here. Then... wait for word of mouth to spread. If your site is great, they will come.
Join the ASP, read and participate in their forums... I learned a lot from them and highly recommend them. Ignore the politics.
I used Myspace as my own free advertising engine, perhaps a bit a-moral but it did the trick till I caught my server on fire.
Having a community of users is very important in having a popular site. Typically your site would have a message board of some sort where users could interact with each other. Also having a large source of reference information is also important. Once you have your site up, you need to go out and promote it. It takes time, be patient but never give up promoting it.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Have any of you ever tried to run from sharepoint? I've worked with sharepoint enough to know that it is not something that interests me. My interests are more along the lines of APIs / backend / distributed development. Have any of you found ways, as consultants, to move away from sharepoint and keep learning other things of interest? I'm currently in a position where sharepoint is in huge demand and I can't quite find a way to simply step aside from it. any suggestions ?
If I infer correctly that you work for a consulting firm then find out what other kinds of things your firm works on. Learn those technologies better that the people who currently work on them for your firm, involve yourself in those projects, even if just in a hallway conversation manner, and come up with better (faster, cheaper) solutions for the problems your firm is solving.
Your options are really seem to be 3-fold
convince your boss your talents
would be better used elsewhere
convince your co-workers they want
you on those other teams
convince your company's clients that
they want you, specifically.
Learn Java, or Ruby.
The Microsoft sales model of "attach" whereby they sell a solution comprised of multiple technologies and then sell the next solution on the basis of "well you have already invested in SharePoint so you already have the skills in place and the infrastructure for this new bit of technology we have" is here to stay... it's very successful.
SharePoint is cloud computing for business who have MS shops... you avoid it by not doing C#. If you're doing C# then given enough time, your apps will need to run in the corporate cloud and you should be looking after your career by embracing it.
Just my 2p. Sorry if it's not quite the answer you wanted.
I know exactly what you mean. I think you don't mind the idea behind a product like SharePoint, but really hate the way its been implemented and how problematic it is. I know its a nightmare to work with.
As a C# developer, I cringe when I hear the SharePoint word, SharePoint is Lord Voldemort. But unfortunately it comes with the job of being a senior C# / Microsoft developer.
I say unfortunately because its likely if you're working in a corporate structure sooner or later you will end up having SharePoint in your solution. Not because its good, but because as others have said - MS use SharePoint as a Trojan horse to get and keep business.
There might be some hope with the new version of SharePoint coming out (2010). Maybe this will finally include a better programming / implementation model.
Otherwise either work for smaller companies (usually less pay, but not always), or try to play down your skills as a MOSS developer if possible. Never actively market them unless your salary depends on it. Remove the skill from your skill matrix, and turn down jobs that completely focus on MOSS. Some MOSS integration here and there you can live with. An entire solution focused on MOSS will drive you insane.
If all else fails, learn other non Microsoft languages, and within a year or 2, SharePoint will be but a faded memory.
I know lots of developers who are thinking about quitting IT because of SharePoint. I would say don't let it be the end of your career.
And finally bitch and moan, and inform managers on a weekly / daily basis, as to why you are battling in SharePoint. Let them know, and constantly remind them how bad a technology it is.
When life deals you lemons. Make Lemonade.
Seriously, if you are seeing SharePoint in such high demand, maybe working with the beast is the best idea. SharePoint is really just middle-ware. SharePoint can simply be a distribution point for your solutions (i.e., a user interface such as a web application can be hosted on SharePoint through a Web Content part). If you look at it, SharePoint may even prove useful as a document respository or small scale data store, in the form of lists.
Maybe you should turn down SharePoint contracts and accept contracts that interest you.
Depending on the market you are in you can simply tell your boss at the consulting company you work for that your not interested in doing Sharepoint projects anymore and that you'll be forced to look elsewhere if they continue putting you on Sharepoint projects. That would work around West Michigan where the developer demand is high and the supply is sub-par.
I'm, on the other hand, just starting to use SharePoint to enreach my currently boring C#-only projects. I'm starting to use it as a front-end to the distributed and complicated systems: simple configuration and customization, reporting, management, system control - looks like all this is available in this package it it's easy to make is usable by non-techies and by beginners.
I personally don't want to work with SharePoint anymore. I've worked on developing a solution for it and even went full charge with a web integration of it. I hated it.
First you have to master the awful programming model then handle all the deployments and it's not even the beginning. If you are developing a product for SharePoint, you have to debug the software itself which is a feat on it's own.
My solution to this is to be very upfront about it. I don't mind doing knowledge transfer and helping out people but I don't want to be developing/deploying SharePoint applications.
My boss get it, my friends get it.
Our latest joke come from someone who said a few months ago that it was "easy and fast to deploy application with SharePoint". The joke? "Did he just put easy/fast in the same sentence as SharePoint?"
So unless you salary would be lower because of it... downplay your skills on it and be upfront to your boss. :)
Have you ever looked at Alfresco (http://alfresco.com)?
It serves many of the same purposes as SharePoint, but does it from an Open Source J2EE application. It will leverage your existing collaboration / content management experience and expose you to a whole bunch of open source technologies.
Full disclosure: I work for Alfresco.
I've already given this suggestion to another guy...Running from SharePoint won't be difficult because technologies are similar to each other according to their structure. SharePoint is not the worst technology to be used, although it is limited in some way... Fortunately, software sphere is too wide to be afraid of not finding anything you can be interested in.