November 0806
When I started my new job, well on day 2 actually, I went into a meeting with my manager and his manager and was given a very quick presentation on the new BIG project that I was brought in to lead on. At the end of which they asked whether I thought we should buy in a 3rd party solution, such as Moodle or whether I would recommend building one from scratch.
Well there's a big part of me, as a developer, that just wanted to write the whole application; hell that's why I'm a developer. But the deadline was quite tight and starting with something that's already been developed and has been tested and is widely used seemed a good idea. So after saying how much I'd like to write it from scratch we agreed that, given the timescales, it would be prudent to investigate 3rd party solutions that could be used as a base and extended upon. A quick chat to the new team and a search of Google turned up Sitefinity as a viable option; viable because it's a .net application and one of the primary reasons for developing something new was to move away from ColdFusion and to use VB.NET as the company already employs a number of quite experienced VB developers, and also because its so cheap... and written to be extended and worked on through Visual Studio.
However... I'm now beginning to regret my decision a bit. Support response time is 48 hours (though often much longer), though the support is usually very good it doesn't usually solve the problem but simply moves the goal posts a bit. Case in point, I've been trying to extend the features, something that it is designed to support (though the tutorial series promised for August 2008 still hasn't been completed), but am having difficulties because I simply don't understand their API and find their documentation lacking in examples or simply nothing more than a list of properties. I have had a support ticket open for 2 months for one problem. On the face of it the problem is pretty simple; I need to allow admins to add job vacancies, with a pdf attachment and dates for final applications. There's even an existing module that does everything I need and more, but though customising it should be relatively simple - hell I should be able to just use Reflector and see how their version is doing things and follow that logic right? Well yeah - but its not having any of it.
So really it comes down to me being unable to decypher the error messages and debug effectively because I haven't written the entire application so I don't understand what's going on or where things are going wrong. Sure the help could be better, but honestly I don't expect someone to come round and sit with me to help me do my job, so I can't and wont complain (further) about the help because much of the help has been superb. But should we (and by we I mean developers of all sorts) use 3rd party products as part of a larger project and when things go wrong be left looking sheepish and waiting for support to get back to us, or should we try to re-invent the wheel every time we start something, even though there's a guy selling wheels next door?
cfec5bf6-2cf6-45cb-a42d-eccf0c7560a2|1|4.0
Permalink |
Comments (4)