Skip to main content

I am (or aim to be) a problem solver

Back in 1995, O'Reilly published the first edition of Oracle PL/SQL Programming. Changed my life...thanks readers! The following extended dedication appeared in that first edition, early evidence of my compulsive verbosity. But I still like it and thought I would offer it for your reading pleasure.

Sometimes I have trouble explaining to my about-to-be-nine-year old son, Eli, the nature of my professional occupation. The statements "I work with computers" and "I write programs on computers" certainly describe my means of employment, but they do not afford much of an explanation.

After some thought, I have found what I believe to be the simplest and also most accurate statement of my professional role in life:

I am (or aim to be) a problem solver.

Every time I write a program or assist other developers with their code, I work to solve a problem. The problem might be as broadly defined as "Build an application to keep track of all product complaints." It could also have a scope as narrow as "Find out why the string parsing mechanism in Sam's package doesn't work." At hear, there is really very little difference between these two requests. 
I am asked to bring logic, experience and technical skill to bear on an unresolved issue – and resolve it.

Solving problems is an extremely satisfying experience. This is part of the reason, I believe, that software programming can be such an addictive habit. In 1995, the quality of life – indeed, the very lives – of hundreds of millions of people around the world are threatened by the greed and out of control ambitions of a very few. Software, with its simple rules and clearly defined boundaries, offers a haven, an oasis, a paradise, into which we can escape, debug out programs, and feel that we have accomplished something constructive.

I dedicate this book to my youngest son,. Eli Silva Feuerstein, in the hope that as an adult he will be an effective and compassionate problem solver, both in the area of his professional interest and in the infinitely more troubled world at large.

I also dedicate this book to my parents, Sheldon and Joan Feuerstein, as a meager expression of my thanks for their lifelong dedication to the happiness and success of their five children (and now six grandchildren).

Eli is now 27 and an Oracle Application Express developer! But I am pretty sure he likes music more than software....


  1. Hello Steven,

    Lot of philosophy contained in that dedication :):)

    Yes, software can be a nice refuge from the real life if one likes to solve problems
    just for proving him/herself that he/she is able to do so, and not just for producing money
    ( most typically for somebody else ... ).

    Unfortunately, at least based on my own experience, this ability does not make you a better
    "competitor" in the real life ... the "more troubled" one as you called it :( :(

    Writing beautiful software is very close to creating beautiful music, they are both arts,
    if one is only capable to enjoy software only "up to the door" where it gets outside from the realm of art .... so, I think it is quite explainable why Eli felt inclined towards both :):)

    Most artists in the history, and the greatest ones first of all, were always unhappy people ...
    but they surely could have never chosen another way in their lives ...

    Thanks a lot & Best Regards,


Post a Comment

Popular posts from this blog

Get rid of mutating table trigger errors with the compound trigger

When something mutates, it is changing. Something that is changing is hard to analyze and to quantify. A mutating table error (ORA-04091) occurs when a row-level trigger tries to examine or change a table that is already undergoing change (via an INSERT, UPDATE, or DELETE statement). In particular, this error occurs when a row-level trigger attempts to read or write the table from which the trigger was fired. Fortunately, the same restriction does not apply in statement-level triggers. In this post, I demonstrate the kind of scenario that will result in an ORA-04091 errors. I then show the "traditional" solution, using a collection defined in a package. Then I demonstrate how to use the compound trigger, added in Oracle Database 11g Release1,  to solve the problem much more simply. All the code shown in this example may be found in this LiveSQL script . How to Get a Mutating Table Error I need to implement this rule on my employees table: Your new salary cannot be mo

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch,

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p