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.

Systems Technology InstituteIt 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.

Principles Of Software Engineering ManagementI 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.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.