Skip to main content

SW Fox: Why NOT Show your own apps?

One of the sessions that I didn't get to attend last night was the "Show us your apps". I think that session would have been really interesting.

Many of the attendees I spoke to were fairly shy about their own FoxPro applications. They would talk about it (as it is their "baby" so to speak) but when asked about specific features that they should show, they seemed to shy away.

That's unfortunate - because I don't think I've ever seen a single FoxPro app (with the possible exception of some purely framework-based apps) that hasn't included a unique feature or hook.

That's one of the reasons I'm particularly excited about Cathy Pountney's session about customization vertical market apps.  Only problem is that it's on right when I've got to get ready to leave. I think I'll have to corner her separately for a quick interview.

But back to my point, one my client apps is an application that was ported from DOS and brought kicking and screaming up to Windows and now finally over to SQL. It has TONS of Bad features (filtered grids, etc). BUT...it also includes some great features: built-in alerts, custom business rule validation.

So when asked to show my apps, I wouldn't show the bad stuff (well, I might to show that it exists everywhere) but the really cool stuff.

Everyone's got some kind of cool in their applications somewhere...why not show it?
Labels:

Comments

Cathy Pountney said…
It's interesting that you mention my session in reference to showing an app. The concept for my "customizing a vertical market application" session came about after seeing two other people show their apps at user groups. I took ideas from both of those apps, combined with some new ones of my own, and came up with the conept I showed at SWFox. Seeing what other people do in their apps can trigger great ideas for you to implement in your app, even if you do it differently.
October 21, 2008 at 3:10 PM
Post a Comment

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com
1 comment
Read more

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...
Post a Comment
Read more

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...
12 comments
Read more