Here's an article that was previously promised to Advisor but they didn't feel it was useful specifically for Foxpro developers. Oh well. Enjoy.
It used to be that building a self-running video or demonstration of software required a great deal of expertise and money, hiring a production company who did the work in their own studio. Today, developers and trainers are building these "screencasts" themselves and in this article I'll go through several options that are available to you.
Heard on ProFox - you think the Visual FoxPro EULA is bad?
A woman wanted to resell software that she would no longer use.
...She met neither requirement, Livingsoft told her, particularly because "when the president of Livingsoft contacted you personally to remind you of company policy in this matter, you informed him that your reason for selling was that the software 'sucks' ... that reason doesn't qualify for an exception to our general policy."
...I find it similar to buying a car, deciding to sell it, and then being told that I can do whatever I want with the car but transferring the keys to someone else is illegal."
Joel explains why XP isn't the answer to everything:
"Many times, thinking things out in advance saved us serious development headaches later on....As I worked through the screens ... I realized that Aardvark would be just as useful, and radically simpler...Making this change in the spec took an hour or two. If we had made this change in code, it would have added weeks to the schedule. I can’t tell you how strongly I believe in Big Design Up Front, which the proponents of Extreme Programming consider anathema. I have consistently saved time and made better products by using BDUF and I’m proud to use it, no matter what the XP fanatics claim. They’re just wrong on this point and I can’t be any clearer than that."
Nothing quite like it when the original architects get interviewed and attempt to debunk recent statements on the criticisms of the implemented world. Such is the case with this interview that Ted points to with Chris date.
I think he may have a point when he refers to the fact that "an object/relational system done right would simply be a relational system done right, nothing more and nothing less. "
But he does sound like a bit of the arch-typical college professor when he says "But the trouble with the relational model is, it's never been implemented--at least, not in commercial form, not properly, and certainly not fully."
Great interview. Thanks for the link, Ted and congrats on your MysQL Certification!
The FoxShow is one of my FoxPro and development business-related podcast. The latest episode (issue, cast, whatever) had an interesting piece that a colleague suggested I share in other areas as well.
It starts about 8 minutes into it and talks about how even though every one may have a different title in a company, when it comes to customers, EVERYONE is a sales person, a support person and a developer.
Part of this comes from the Return on Customer book I'm reading but it's also something that I think many people see in their every day life.
You're always selling something - an idea, a product, a service, a design methodology
You're always supporting something - same as above
and everyone is always developing something - it may be an idea, a software product, a hardware product, - you're always trying to take it and make it into something more.
The key takeaway - if you see someone in your organization that isn't thinking this way, then think of the conseq…
This has been discussed numerous times before but Windows Vista brings it up once again.
I went on a rant on this on this week's FoxShow related to user interface design but I agree.
"As I pointed out last week, it's not a beta until it's feature-complete. Microsoft is showing off a prototype, a demo. When they have the new UI in place, and lock down the features they plan to actually ship, then it is time for beta evaluation and testing."
Rick Borup notes that he's reaching the point of information overload, even with RSS.
What is needed to make it easier to read 1000 RSS feeds a day? It would be useful if the News reader learned about the types of items that you DID read and then suggested key ones to you. (I can envision an interface similar to that of the Automatic Playlists in Windows Media player - feeds I read at night, feeds I read during the day, random pick, etc)
This might make it a little easier - it would also be useful if the NewsReader aggregates the feeds themselves - so that if 10 sites all referenced the same main story - it only appeared as one news item, instead of ten (but with 10 different "story comments")
If you've never read Steve's posts, they are amazing. I don't like that his Atom feed only shows the shortened text version (the posts themselves are full - Thanks Rick for clarifying that in comments) but it's rare that I don't forward them onto my business associates.
And he was a FoxPro guru too....Great blogs Steve.
Claudio - I always thought that it was because C programmers didn't know how to count (or was it ActiveX developers?)
Maybe it was just the Microsoft ActiveX guys - because by the time they got to the Outlook object model, at least they remembered that 1=1.
It may just be a throwback to when people said "I'm going to punish the punchcard guy by shuffling his cards" or wouldn't it be fun to do
#DEFINE True .F.
#DEFINE False .T.
right at the start of my code?
But your comment on "logic" reminded me: I took a philosophy class in university and after going through Plato, Aristotle and others, we came to logic. Do you know what the prof said? (this is why I hated that class)
"Don't try to understand logic - Logic doesn't make sense - just memorize it" - Philosophy professor , Trent University, Canada around 1989.
In fact, Logic (and Aristotle) were about the only things that made sense in that whole class.
Kevin notes that the entry for xBase says you have to use Clipper to shoot yourself in the foot. But if you read a little further,you'll see:
You buy a gun. Bullets are only available from another company and are promised to work so you buy them. Then you find out that the next version of the gun is the one that is scheduled to actually shoot bullets.
That sounds like an awful lot of other products that aren't mentioned in this article too.
But I love the ones near the bottom :
You shoot yourself in the foot, but can't figure out how you did it so you find a dozen new ways to do it.
You shoot yourself in the foot and everything goes so smoothly that you go ahead to to shoot yourself in the other foot then your legs, then your torso and then your head. Problem solved.
Great article on hiring great programmers, as opposed to good ones.
What's interesting is when Joel takes the stats of min vs max hours and then only looks at the top 25% (in terms of grades) - the differences in time are still there. As he notes with these studies: The quality of the work and the amount of time spent are simply uncorrelated.
It's not just a matter of "10 times more productive." It's that the "average productive" developer never hits the high notes that make great software.
Rick is wondering about where to put Ajax technology in something like the West-Wind store.
I've been reading a lot of the Michael Mahemoff's posts about Ajax as well as I become more and more familiar with Ajax.
Certainly, it makes certain things easier to work with but it is just an approach that reduces screen redraws and server trips.
That said, where could it be used in an e-commerce approach?
1. Searching for products in a large inventory. As it finds new items, they get added to the list of what's available.
2. Recommended items based on what a user has chosen.
3. Reducing the way "pages" are handled in a web -based application. Instead of having to go back to the server for each page, it could "flip" automatically.
Sure, these are things that can be done today with a traditional approach but they all require server round-trips. You order an item and then once it's been processed, it makes some suggestions. When I am just looking at a produc…
David Stevenson has posted his entire interview with Ken and Yag on Sedna (no longer the tenth planet) and the future of Visual foxPro.
Great stuff David.
I find it interesting that Alan Griver is referring to the decision to support Vista with Sedna to be akin to shifting from DOS to Windows or from 16 to 32 bits.
I hope that is to do with the XAML support that Ken showed in his Channel 9 video.
My favorite part of the Interview: "People always talk about programming languages being written in themselves. The .NET framework was written in C# and in VB. More and more parts of Visual Studio are now written in the managed (.NET) languages. It’s the same reason that anything that we add for ourselves benefits our customers. This means that if we add new extensibility capabilities in Sedna and we prove how much can be done – you know, if we can do half the things we defined in Sedna without touching the core product, you know what, Fox is a hell of a product."
That was my reaction over a year ago when Craig showed me what he was doing and it still is. Combine a solution explorer with Arg's Property Browser and now this is precisely what Craig Boyd was talking about when he said build better developer components.