# Different ways of structuring code - what do you think is best?

**URL:** <https://forum.devtalk.com/t/different-ways-of-structuring-code-what-do-you-think-is-best/1304>\
**Category:** General Dev Chat\
**Tags:** organization\
**Created:** [5 August 2020 10:50 UTC](https://forum.devtalk.com/t/different-ways-of-structuring-code-what-do-you-think-is-best/1304 "2020-08-05T10:50:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Exadra37](https://forum.devtalk.com/user_avatar/forum.devtalk.com/exadra37/32/683_2.png) [@Exadra37](https://forum.devtalk.com/u/Exadra37)\
**Post date:** [6 August 2020 19:01 UTC](https://forum.devtalk.com/t/different-ways-of-structuring-code-what-do-you-think-is-best/1304/2 "2020-08-06T19:01:13Z")

</div>

> [@dimitarvp](#):
>
> “How to make and maintain a project in framework X with the minimum amount of files and boilerplate”

Well with the minimum amount files resonates to me as that huge files of code that do not separate concerns and actions.

I am not really a fan of one file to handle all the actions one a resource, but this is often the case, but what pisses the heck of me is when the files goes to the thousands of lines and deals with many resources… it’s just a nightmare and a sink hole of our time 😉

But probably the minimum amount of files you are referring to are not related with the code for the project itself?

---

_[View the full topic](https://forum.devtalk.com/t/different-ways-of-structuring-code-what-do-you-think-is-best/1304)._