“We don’t want to be dependent upon Oracle.”

I have lost a lot of projects due the little sentence: “We don’t want to be dependent upon Oracle.”  (I just lost another one this week.) It has been used to justify all sorts of crazy decisions such as: Spend millions of

Tagged with: , , ,
Posted in Consulting, Development, Products, Resources, Training

Normalization Still Matters in System Design

When I wrote Oracle8 Design for UML Object Modeling in 1998, Martin Fowler was my technical editor.  I remember having a very serious discussion with him about whether normalization mattered for UML class diagrams. If you look at Martin’s diagrams in his writings,

Tagged with: , ,
Posted in Consulting, Resources

Business Rules Explained to a Seven Year Old Kid

My son Robert is seven years old.  My wife Ileana (one of the smart persons in my company – her lapse in judgment in marrying me notwithstanding) and I were discussing business rules in the car and Robert asked what

Tagged with: ,
Posted in Other

Business Rules – Object Rules

Object rules are the primary type of rule with which we have to concern ourselves. They include everything we can say about the “stuff” in our system.  Database people would call these entities; OO people would call them classes.  “Stuff” is the

Tagged with: , , , , , ,
Posted in Consulting, Development

Business Rules Architecture

Business rules people may not really like this architecture.  It is pretty technical.  But I am not trying to build pretty documents, draw pictures, or talk to users for the sake of making them feel loved and understood.  I am

Tagged with: , , , ,
Posted in Consulting, Development

The Business Rules Perspective

“Business Rules” is not simply a technology, it is a fundamentally different approach to systems engineering. Years ago, when I first heard the term “business rules,” I remember thinking that we had some up with a new buzzword meaning the same

Tagged with: , ,
Posted in BLOG, Consulting, Development

Changes in direction that the IT industry should have never made

From where the industry was when I started Dulcian back in 1995 to where it is today, I have seen massive changes in direction. Many of these changes make me miss the “good old days”.  I would like to point

Tagged with: , , ,
Posted in Consulting, Development

Why Dulcian and what is that?

Finding a name for a company is tough.  Unless you want to call your company something that looks more like a strong password, everything in the world is already taken.  Somebody has even registered “PaulDorsey.com” on the off chance that

Tagged with:
Posted in About Dulcian, FAQ, Other

Don’t be thick – Use a “Thick Database” approach

The trend in recent years has been to decrease reliance on the DBMS (database management system).  Using this approach, all code and logic gets moved to the middle tier.  The database becomes nothing more than “a place to store persistent

Tagged with: ,
Posted in BLOG, Consulting, Development

And the #1 killer of performance in a web application is…

OK, sure, if you write a query that takes 10 minutes, then your performance is going to be terrible.  But of all the systems I have seen, usually there is somebody around who can both detect a long running query

Tagged with: , , , , ,
Posted in BLOG, Consulting, Development
Disclaimer
The information presented on this blog is presented to provide general technical information. If, while attempting to apply any of the ideas, procedures, or suggestions herein, you experience any kind of programming or system problems or failure, it will be as a result of your own actions. Dulcian, Inc. and all authors of text found anywhere on this site, and all internally-linked Web sites, Mail Lists, Blogs and/or e-mail group discussion, disclaim responsibility for any user's actions and any damage that may occur based on information found on this website and associated Mail Lists, Blogs and/or e-mail group discussion. Any technical advice or directions found on or through this site is provided AS IS and its provided without warranty or any guarantee of its accuracy. You perform any modifications to programs or software AT YOUR OWN RISK.