<p>In a language such as (since I'm working in it now) PHP, which supports procedural and object-oriented paradigms.</p>

<p>Is there a good rule of thumb for determining which paradigm best suits a new project? If not, how can you make the decision?</p>

[{'answer_id': 3998, 'author': 'Chris Bunch', 'author_id': 422, 'author_profile': 'https://Stackoverflow.com/users/422', 'pm_score': 5, 'selected': True, 'text': '<p>It all depends on the problem you\'re trying to solve. Obviously you can solve any problem in either style (procedural or OO), but you usually can figure out in the planning stages before you start writing code which style suits you better.</p>\n\n<p>Some people like to write up use cases and if they see a lot of the same nouns showing up over and over again (e.g., a person withdraws money from the bank), then they go the OO route and use the nouns as their objects. Conversely, if you don\'t see a lot of nouns and there\'s really more verbs going on, then procedural or functional may be the way to go.</p>\n\n<p>Steve Yegge has a <a href="http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html" rel="noreferrer">great but long post</a> as usual that touches on this from a different perspective that you may find helpful as well.</p>\n'}, {'answer_id': 4039, 'author': 'ggasp', 'author_id': 527, 'author_profile': 'https://Stackoverflow.com/users/527', 'pm_score': 2, 'selected': False, 'text': "<p>If you're doing something for yourself, or if you're doing just a prototype, or testing an idea... use the free style that script languages gives you. </p>\n\n<p>After that: always think in objects, try to organize your work around the OO paradigm even if you're writing procedural stuff. Then, refactorize, refactorize, refactorize.</p>\n"}]
['https://Stackoverflow.com/questions/3978', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/572/']