MostofaL's avatar

Best Design Patterns for a Helpdesk Ticket System

I'm developing a CRM system project including support ticketing and sales leads.

I don't have enough prior experience with all the design patterns, and due to project deadlines, I don't have the time to go through them in detail, one by one.

Are there any specific design patterns that you would advise focusing on them first for this project?

0 likes
4 replies
Tray2's avatar

Yes, there is one you should focus on, and that is the KISS pattern.

Don't overthink it, keep it simple. Don't make your code more complex by using this or that pattern, they all have their time and place, but for a first project, second project, and 100th project, I'd still recommend using KISS.

Keep It Simple Stupid.

1 like
martinbean's avatar

@mostafaalotfi@gmail.com Design patterns aren’t something you just throw in a project. Applying design patterns doesn’t magically make your code “better”; they can have the opposite affect if you’re just shoe-horning design patterns and in where they don’t belong or don’t fit.

If you have deadlines then deliver the project, then look at opportunities to refactor based on any new knowledge.

1 like
MostofaL's avatar

@martinbean Sure. that's right and I'm in the refactoring phase of the project and seeking the advice of the experienced.

jlrdw's avatar

@mostafaalotfi@gmail.com Just use MVC. But I suggest perhaps looking at some on Github for some ideas. Not saying use one of them, but looking over the code and gain some ideas.

I myself have improved a custom framework by studying the laravel framework code (framework not laravel) and I have got many ideas from @taylorotwell.

Or you may even find one on Github you can use.

1 like

Please or to participate in this conversation.