Surviving | Object-oriented Projects

Many teams transition to object technology expecting a "silver bullet" for productivity, only to find themselves trapped in refactoring loops or complex inheritance hierarchies that make the codebase brittle. To survive, you must treat the project not just as a technical challenge, but as a management and cultural shift.

Focus on picking nouns for classes and verbs for methods to stay close to the actual business problem.

Avoid deep inheritance hierarchies (more than two levels is often "brittle") and prefer composition to keep the system maintainable. 4. Manage the Human Element Surviving Object-Oriented Projects

Before writing a single line of code, identify the nature of your project to set realistic expectations and staffing:

An experimental project designed to identify future implementation hurdles. Many teams transition to object technology expecting a

A high-stakes move to transition the entire organization to an OO paradigm. 2. Adopt the "Incremental" Habit

Instead of modeling the entire world, plan by feature and build a list of tangible functionalities to deliver. 3. Invest in "Object-Think" Over Tools Avoid deep inheritance hierarchies (more than two levels

Building a successful object-oriented (OO) project is less about mastering syntax and more about navigating the human and structural "holes" that swallow most software initiatives. Based on the principles in Alistair Cockburn's seminal work, Surviving Object-Oriented Projects , and modern industry insights,