There is a heated argument between a SharePoint Developer, a Java/.Net Programmer, a Web Designer and an Infrastructure expert over the current project we are handling. The SharePoint Developer is insisting that the Web Designer cannot have
a certain feature which the Web Designer thinks is achievable. The Java/.Net Programmer have had a some nasty experience with SharePoint in the past week.
The basic issue is user friendliness and functionality . The Web Designer has no knowledge of SharePoint architecture and is basically fiddling around to achieve his objective. The SP Developer maintains that a project has
timelines and deliverables and he cannot jeopardize that for
cosmetics , especially at this critical-less-than-4-days-to-go-completion time.
Please tell me your views on what makes SharePoint different from regular programming, regular and dynamic web design using the languages available today? I am asking this because I think it is key.
You've only got one life; help as many people as you can, and enjoy it while it lasts.
View Complete Post