57 Kenwoods Circle
K7K 6Y1 Canada
Phone: (613) 542-3293
Websites: http://www.stevenblack.com , http://www.fox.wikis.com
Steven has been a Fox developer since 1986. He markets Steven Black's INTL Toolkit, a multi-lingual framework for FoxPro and Visual FoxPro, which he created in 1993 and continues to refine. He has been a featured speaker at over forty FoxPro Devcons and regional conferences, and his contributions occasionally darken the pages of VFP books and magazines. Steven is also the creator and webmaster of the Visual FoxPro Wiki, an innovative VFP community knowledgebase, which is found at http://www.fox.wikis.com. His company, Steven Black Consulting, is based in Kingston Ontario, and operates worldwide. He specializes in multi-lingual, multi-site, and other challenging FoxPro projects, including out-of-control project turn-arounds and cleanups. He consults with small developers as well as large corporations, national and international government agencies, and software development companies to elevate their development teams.
FoxPro is dead! Now what do I say?
The Business case for developing a new application using FoxPro
Assuming you've got a suitable technical case for development with FoxPro, then what? The business case for software development is a space where the technical issues are but one aspect of the internal and external forces that must be addressed and balanced. In this session Steve will outline a framework for thinking about the various business angles underlying software development so you can create truly evident and meaningful value propositions for your company and your customers. Target Audience: Independent software developers, team-leading corporate developers, and consultants. Prerequisites: None.
Visual FoxPro's built-in data handling capabilities make it among the best platforms available for creating data-configured and data-driven applications. In this session, Steve informally introduces some application meta data design patterns and idioms for Visual FoxPro developers. Since we all have different third-party and home-grown ways of structuring application metadata, and given that metadata-driven elements are core, some standardization would be nice so that, as sharing developers, we could all better interoperate. But first we need a way to abstract the whole application metadata space, which is what this session is all about.