Skip to main content

Why FoxPro Matters: Development

Every developer has a starting point. It isn't necessarily the first time they wrote a line of code or the first computer they worked with. Rather, it's the first time they "got" it - the first time, they were able to put the separate pieces (the data, the code, the interface, the entire experience) together, not just for a client but for themselves as well. It's the light-switch moment - the kindling of the passion. Some developers write code their entire life but never find a connection to data. Others become pure DBAs - they don't write application code; but rather focus on how the database interacts with others. But most applications rely on the convergence of the two, the content and the delivery, to create the final solution.

When I meet a developer for the first time, I usually ask what they like to work with, what part of the development process gets their juices flowing. This helps me identify the best method of optimizing their strengths. There are a few common responses:

a) doesn't matter - the sign of either a developer who's given up or hasn't found their true passion
b) code - best to focus on logic
c) data - great opportunity for analysis and conversion
d) both - versatile
e) setup/configuration - tweaker!!

But the responses are also dependent on the languages and tools they have worked with in the past. Some languages are natural for this. They encourage data and code to work together. FoxPro is one of those tools. I have yet to meet a FoxPro developer who doesn't fall into the d) category above. When an architect talks about metadata tools, most FoxPro developers "get" it - because they are used to the meta-data that surrounds data, be it in the DBC or third party tools.

This isn't to say FoxPro doesn't have its faults - but rather that its strengths revolve around the convergence of content and delivery. Years ago, that wasn't always the case. Programmers focused on the intricacies of the code, rather than the delivery. Today, there are many other tools and frameworks, especially in the web world (Ruby on Rails and other MVC come to mind), that focus on that same convergence.

That convergence can be what separates success from failure and the tools that help ensure and promote a strong understanding and correlation between the two are usually the right tools for the job.

For me, FoxPro has focused my attention on how data works with the solution. There's a reason why I see an application in terms of its data and how users can get to that data and turn it into valuable information. If information is currency, then understanding how data turns into information is worth its weight in gold. FoxPro's value legacy will be in the developers who have that understanding and share it with their clients and their colleagues.

Comments

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…