How critical is the use of migrations in Laravel for a single project with a single developer?

Question

Laravel

Hello.
I already understood that migrations in Laravel are a kind of version control system for the database structure.
Tell me, how critical is the use of migrations in a project where there is one web developer (me) and a dozen tables with a dozen fields each (roughly speaking).
I'm just starting to learn Laravel and all this redundant functionality in the form of migration rollbacks, etc., only confuses me. It's easier for me the old fashioned way - through phpMyAdmin and dumps to work.
Would it be normal in such a situation not to resort to migrations at all?
And will I be able later, if necessary (for example, other developers will be added to the project or something else) to create the necessary migrations?
Thank you.

Answer 1

Answer from Alexey in the comments here: https://toster.ru/answer?answer_id=1340557#comment...

Answer 2

Migrations are always and everywhere, they are needed not for the team or anyone else, but for versioning changes in the database. It's like "do I need to use git if I'm the only developer in the project?!" - yes, damn it, you have to!
The sooner you get used to the right approach, the higher your value in the community.