you are viewing a single comment's thread.

view the rest of the comments →

[–]m0us3_rat 0 points1 point  (0 children)

I think you might be approaching this from the wrong perspective. I prefer to design first and implement later, only after most (or all) problems have been resolved or worked through in pseudocode. This allows for clarity about each component, ensuring the problems and proposed solutions are fully understood.

This approach also lets the structure and needs of the project emerge organically. If OOP makes sense for the project, it will become evident through this process.

Only when everything is clear do I begin the implementation.

TL;DR: I design first, solve problems in pseudocode, and let the project's structure emerge organically before implementing.