I'm back at the foxite.com forum, but I had to rejoin with a different online persona. It's not easy to remember my user name and password when I have been inactive for so many years.
Anyway, I am not back in order to solve some programming problems. I'm here to jog my memory and to remind me of the challenges I hurdled when I migrated from Clipper to Visual Foxpro. Of course, I do have my diaries to provide me with great material for blogging.
Tuesday, February 24, 2009
Thursday, February 19, 2009
Cannot Stop Programming in Clipper
I joined comp.lang.clipper and comp.lang.xharbour to get in touch with other Clipper programmers out there.
My first post in the comp.lang.clipper forum:
And then, responding to a post by another programmer, I was able to articulate my thoughts about Clipper's place in my plans:
And so, as promised, I'm now activating several of my blogs about programming. In particular, it's rather fitting that I have a blog Cannot Stop Programming in Clipper to hold whatever I know and whatever I'm doing with Clipper.
My first post in the comp.lang.clipper forum:
I'm new to the group so I'd like to say hello to everybody.
I'm a Clipper programmer since 1988 and right now, although I'm programming in the newer languages, I have decided to rewrite my old programs using newer programming techniques. Actually, I started rewriting in 2006, but it is only now that I have more time to finish it.
My decision is based on a rather frequent observation of computer users. Some people, I observed, are better off using simple programs written in Clipper.
Anyway, I'm still using Clipper 5.2e. But now, I'm redesigning everything I wrote and incorporating Class(y) plus several public domain libraries that freely available on the internet.
And then, responding to a post by another programmer, I was able to articulate my thoughts about Clipper's place in my plans:
Actually, I'm programming again in Clipper so I will have a DOS-based application in my product line that do not cost much to produce and deploy. Clipper meets my objectives while staying within my resource constraints.
Right now, I'm also developing in Visual Foxpro 6 for my main product offerings. I've been doing this since 2001 so I got a lot invested in it already. It's only because I cannot surpass the usability and responsiveness metrics of a Clipper application that I was forced to recognize its value.
As for web-based and Linux-based system, I'm going the Java and PHP route. For me, it's very important that I will have access to the large amount of Java and PHP resources available out there in the open source community.
To further complicate matters, I also managed to learn C and a little bit of C++ while reviewing for a certification exam.
Now with all these knowledge, my approach/policy/strategy now is a hybrid solution package where client software written in various languages will be able to access a common database with each application performing in the areas they perform best. Clipper fits the low development cost, maintenance-free and high responsiveness areas perfectly.
Anyway, I'll be activating several blogs in the next few days so I will be able to expound on various issues in software development and at the same time confer with other programmers like yourself.
And so, as promised, I'm now activating several of my blogs about programming. In particular, it's rather fitting that I have a blog Cannot Stop Programming in Clipper to hold whatever I know and whatever I'm doing with Clipper.
Sunday, January 11, 2009
Software Engineering
This is how it all began for me—why I am a computer programmer and why I am in this business of software publishing.
When I graduated from college in 1987, I was attracted to computer programming as the computer industry was poised for growth. It seemed to me that civil engineering and the construction industry were less promising for somebody attracted to knowledge work esp. the opportunities offered by the information society. Instead, it seemed rather obvious that computers and software were the future.
It was fortuitous that I got a scholarship at Systems Technology Institute (STI). At the time, it was the leading computer programming school in the country and its graduates were sought after for hiring. However, I opted out of STI's hiring program and instead got a scholarship with Fujitsu. After training, I was slated for hiring at the National Computer Center. But it was then that I traded the hectic life in Manila for a chance to venture on my own in a smaller city.
In 1991, I started my own software company. This was a period when the local software industry was still at its infancy and computer geeks like me were in high demand and in short supply. But even when the market was growing fast, I had to struggle during my early years to keep the business solvent. It was expected because like everyone else, we lacked the knowledge to run our ventures as a business.
It was inevitable. Going bankrupt was a common outcome in our industry. I was no exception. But that was not the problem that kept me awake at night. I know that there will be still be plenty of opportunities in the future. So, I wasn't afraid to fail. For me, the most challenging problem was production. If somehow I managed to solve the productivity problem, I'm sure I can translate that to commercial success.
I wanted something similar to civil engineering applied to computer programming. Back then, software engineering methodologies were not widely used, but there were books about the subject. One such book was Tom Gilb's 1988 book, Principles of Software Engineering Management. However, in 1988, it would still be years into the future before technology became more widely available esp. the software engineering tools. Only in the past 10 years have I seen technology and knowledge become more widely distributed to be of practical use to me and my plans.
I've come a long way since I started programming in my PC-XT. Although, the kind of software I'm producing now is no longer limited to computer programs, my main problem is still the same. I need to produce a lot of software. And I need to do a lot of knowledge work.
I have not been a civil engineer for more than a decade, but my problems demand someone with civil engineering background to manage several ongoing projects. It's true that it is out of necessity that I now assume the role of project manager. But it is equally true that I am the right person for the job.
When I graduated from college in 1987, I was attracted to computer programming as the computer industry was poised for growth. It seemed to me that civil engineering and the construction industry were less promising for somebody attracted to knowledge work esp. the opportunities offered by the information society. Instead, it seemed rather obvious that computers and software were the future.
It was fortuitous that I got a scholarship at Systems Technology Institute (STI). At the time, it was the leading computer programming school in the country and its graduates were sought after for hiring. However, I opted out of STI's hiring program and instead got a scholarship with Fujitsu. After training, I was slated for hiring at the National Computer Center. But it was then that I traded the hectic life in Manila for a chance to venture on my own in a smaller city.In 1991, I started my own software company. This was a period when the local software industry was still at its infancy and computer geeks like me were in high demand and in short supply. But even when the market was growing fast, I had to struggle during my early years to keep the business solvent. It was expected because like everyone else, we lacked the knowledge to run our ventures as a business.
It was inevitable. Going bankrupt was a common outcome in our industry. I was no exception. But that was not the problem that kept me awake at night. I know that there will be still be plenty of opportunities in the future. So, I wasn't afraid to fail. For me, the most challenging problem was production. If somehow I managed to solve the productivity problem, I'm sure I can translate that to commercial success.
I wanted something similar to civil engineering applied to computer programming. Back then, software engineering methodologies were not widely used, but there were books about the subject. One such book was Tom Gilb's 1988 book, Principles of Software Engineering Management. However, in 1988, it would still be years into the future before technology became more widely available esp. the software engineering tools. Only in the past 10 years have I seen technology and knowledge become more widely distributed to be of practical use to me and my plans.I've come a long way since I started programming in my PC-XT. Although, the kind of software I'm producing now is no longer limited to computer programs, my main problem is still the same. I need to produce a lot of software. And I need to do a lot of knowledge work.
I have not been a civil engineer for more than a decade, but my problems demand someone with civil engineering background to manage several ongoing projects. It's true that it is out of necessity that I now assume the role of project manager. But it is equally true that I am the right person for the job.
Saturday, September 1, 2001
Joined Foxite.com
I joined foxite.com today to become more familiar with Visual Foxpro 6. It seems to me that my biggest problem right now is about saving and retrieving records to and from the database. Hmm. How do I lock the file or records? I can't understand this optimistic and pessimistic locking. What if the automatic lock fails? What then?
Hmm. So many questions, I hope the programmers in this forum will give me the answers.
Hmm. So many questions, I hope the programmers in this forum will give me the answers.