11/26/2024 7:26:01 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
SLX Developer
Posted: 26 Jun 06 4:52 PM
|
fiogf49gjkf0d Not sure if this is the correct forum, but my company may be searching for a SalesLogix developer. How important is it that this person knows SalesLogix itself? Any information is greatly appreciated! |
|
|
|
Re: SLX Developer
Posted: 27 Jun 06 8:03 AM
|
fiogf49gjkf0d Michele,
You will probably get a wide variety of opinions on this.
IMHO
If you are hiring someone to actually code & design: the minimum requirements would be VBScripting, Client Server Technology, some DB knowledge and a commitment to send the new person to both SLX Admin and SLX Development class. In other words it can be done. Having said that, SLX has a lot of 'behaviors' and 'gotchas' that make it difficult for a new developer to quickly adapt. A new dev can create and force results, but the design portion of their tasks will frequently yield undesired results on either the business side or the administrartion side until a good understanding of 'SLX inner workings' is acheived.
|
|
|
|
Re: SLX Developer
Posted: 27 Jun 06 9:01 AM
|
fiogf49gjkf0d Michele,
If the developer has good programing skills they can always learn what they need to know about the SalesLogix environment. They will need to know the application and how your company uses it before they can effectively modify it.
Having prior experience with a CRM development would be a plus. |
|
|
|
Re: SLX Developer
Posted: 27 Jun 06 4:15 PM
|
fiogf49gjkf0d I'll reiterate what is said based on my experience as a self taught developer/administrator. A book, a class, or working with someone "in the know" is extremely valuable, not to mention sites like this that can answer the various issues that pop up. Second, a LOT of testing time is necessary to work through all of the pitfalls. I spent 9 months or more converting all of our Legacy 5.x code to VBScript but it taught me so much I don't think I could have done it any other way. A major reason it took so long is the fact that I do way more than just SalesLogix work alone, but finding and adjusting to all of the quirks took a large part of that time as well. In a normal programming environment, coding against quirks in the platform is frowned upon but in SalesLogix land that may be the only way your customization sees the light of day.
SalesLogix changes rapidly as well so what is broke in one version may work in another, but the cool part about 6.x is the fact that it's way more stable than previous versions. As I upgrade I find such quirks are often reduced so it's also valuable to have a nice testing environment to play with new versions ASAP. Waiting until planets and stars align just to get started is a waste of time in my book. If you approach it as a MS developer where new versions of SalesLogix are like new versions of Visual Studio then it makes sense to have the latest tools in the hands of your workers and that SalesLogix development for the most part is as important as the next iteration of a custom peice of software your company uses. The major differences are you aren't really given adequate source control, unit testing, or many of the modern influences in programming that is present in other development platforms. Development can be easier because it often doesn't take a "recompile", there's a lot of stock code that does almost everything someone needs to do, and it can be difficult to screw things up (though when some people do, they tend to stay in a state of mind that their way is correct).
Good programming skills, as Frank mentioned are key but more than that: humility. Your way may be one of dozens that gets the job done or one small quirk may cause all of your assumptions to be flawed. There's a right way, and a more right way often than not so if you ask for help expect people to comment on your methods, but don't take it as a personal attack. |
|
|
|
Re: SLX Developer
Posted: 29 Jun 06 11:23 AM
|
fiogf49gjkf0d Also, some CRM experience (ie. ACT!) would definitely be helpful |
|
|
|
Re: SLX Developer
Posted: 03 Jul 06 12:33 PM
|
fiogf49gjkf0d There's really several skill sets needed:
A - Good engineering problem definit/solving skills
B - Business knowledge (after all, SalesLogix is about solving business problems)
C - Development/Programming - VBScript/vb skills (>NET is nice but that's not what (typical) customizations are done in.
D - Good intrepersonal skills (work w/ peers/subornates/upper management
E - Willing to give up every second of their day/night weekends 
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|