Planning Laravel Projects: TWO Things You Must Do First

I think we're not talking enough about what happens BEFORE we start writing Laravel code. Let me share my "philosophy".

Courses mentioned in the video:

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:

[hkhdev]

This types of video for me it's better than coding, if you search the internet you will not find any tutorial (FREE or PAID) that take the beginner, step by step from scratch to build a real project. I mean real project not just the general concepts of the development, like (Auth, CRUD etc..). Thanks

[lautaropiatti]

I roughly had a process, but I implemented this one today and went great for clarity, thanks for the content!😀

[fordprefect]

I feel this video is a very valuable advice. At least you suggest exactly the way how I am handling new projects.

[Buscalia]

Absolutely agree. I developed a few projects restarted until 3 times 'cause did not take the time for this basic analysis at least of tables, relationships & routes as I let me be dragged by customers' hurry up. The painful part in most cases was not the time to rebuild but convince customer that hurry ups do not works NEVER. If they has run out of time for the project then it is better to get a standar package and sacrify much of customization in favor of zero starting time. If anyway they don't want renounce to customization then I recommend him to have got the needed amount of patience and method to develop their solution. If none of both then drop that customer and move for another one more serious in his plans.

[utchas]

I also create a DB Schema or ER Diagram first and a feature list like you but after clarifying the technical questions from client party, I usually make a project plan, a Gantt chart to define project timeline and assign tasks to team members (I work as a team lead and almost all projects are multi-developer work)

[blessdarah]

This is exactly what I do all the time. Having a wrong understanding of how the schemas work will only just make it worse for you down the line because at the end of they day, even you don't know what you're building. So I always give a lot of time to map out the data models because to me, that's what will finally give the experience on the frontend which is what the user will be seeing all day long.

[asadmalik]

Taking clear inputs and description from the client is the important part of any project scope, but yeah in the end its totally depends upon client mindset as well.

[ebeneoyen]

Actually for me i usually get a UI/UX designer to design the system. This helps me and the client to be able to picture what the system will look like and also give room for discussion. Afterwards i develop the db schema using mysql workbench before exporting it as laravel migrations.
Though i learnt focusing on the tables and relationships first before drawing up the columns, I'll try that next time

[lucasj.pereira]

Damn, I wish I've seen this video 7 months ago... Thank you Povilas!

[einnlleinhatt_]

Thank you for this. I just started making my own peotfolio and I did many changes to the database. Like for example my projects table only have name in it and later I realized why not add url too.

[amitsolanki]

Sir how can i display all data from db according to user timezone dynamically in laravel i have set utc timezone in my app config file and i currently used but its not provided accurate result in some pages please help me..

[umahatokula]

Thanks for this video. How do you cost a project?

[FrancescoCicGramegna]

I really appreciate video's content like that. Do you usually use a road map for the project?

[_bijaydas]

Can you please share, how do you write these blogs? Do you use any markdown processor? Or use any headless CMS?

[richardwheatley]

Bit old school but you might want to start with creating a statement of work. One important element of this is commercial.

[r.y.s.]

Do you still update Quick Admin Panel? I'm considering upgrade my plan but im afraid that the project is already outdated. Please advise!

[infinito]

In the course you wrote:

_Of course, a lot of things are totally unclear in this simplified job description, and we don't have the contact with the client to ask, so we will assume a lot in the course below_

Call me idiot, but from the job description I missed a lot of things (more than you) and I struggle to "assume" many of the features you wrote.
So, excluding obviously concepts (like for reservation which includes start/end date/time) is there a way to hypothize missing info?
For example, what does it mean "...send out a link to fill their size"?
What are "sizes" in trips??
It will be almost impossible to build a basic schema without understand the basic informations and features. And will be hard to write a quote, and that's an important part.
Maybe, before writing a schema, I need a specific course to "decrypt" customer needs 😅.

[gryg]

Just build your own checklist, that every project quote will have to go thought.