Laravel, I've come to bargain...

laravel-I-have-come-to-bargain.md

I have been doing a lot of "pros-and-cons" stuff from a little over 2 years now - about using Laravel.

I made it a big deal (and I believe I regret it in a certain capacity).

It should not have been a big deal.

It is a just another framework.

Finally, I have caught up with my senses and I strongly believe that I was too arrogant or stupid to not go down the Laravel path.

I am far too young to allow myself to fall into such traps of "not-wanting-to-do-certain-framework-or-language".

Laravel, here I am, and I have come to bargain... and after that it's you "React JS and React Native"...

Kicking off from Laracasts, I would be starting with some of the basics, setting up everything using Docker and MySQL(or Postgres - for Laravel it's one and the same thing) on GitHub / GCP > Cloud Run / AWS RDS.

The "App" that I would be developing (after learning) would be the famous "noter" app (github.com/konnector-dev/noter) - the one that suffers.

Keep an eye out...

Laravel 8.x (latest at this point of time), on PHP 7.4.10 (latest as well)

Docker / docker-compose

Composer 2.0.3 (again, latest, 2.x released a few days back)

Damn it.. I really like CakePHP!

Although I really like CakePHP (or any generic PHP framework including SlimPHP ), but I strongly believe I need to move to Laravel... for multiple reasons... and yes, the ability to demonstrate the speed of development is one of the strongest one.

Most of the Laravel developers I have met/worked-with are "painfully" slow and the only reason I am unable to provide direct inputs is because of my lack of knowledge of the framework and the design patterns being used in the projects (by the framework and by the developers).

One of the biggest quirk I have seen with Laravel developers (the ones that I have worked with) is about the ORM/Model layer - ridiculing it a lot, and complaining about "slow performance due to slow queries" by blaming it entirely on Laravel. Without even looking at the official docs and searching Google/Stackoverflow or even Laracasts (the ones that I have work with have a licensed version of Laracasts) - I can guarantee that the problem is with the implementation by developers and not in the framework. Even if it is the framework (which is definitely not the case) any ORM can be used (CakePHP's ORM can also be used).

No caching
No clear understanding of security (and hence the lack of implementation)
No optimisation methodologies
No DB understanding (although not directly a part of Laravel, but I have seen a serious lack of understanding in this domain as well)

And probably much more other reasons would be identified as I dive deep into the learning path.

I am starting, correction - restarting, this weekend... wish me luck (again) and let me say this yet again....

Laravel, I've come to bargain....

#nazarRakheyo

+TailwindCSS

It's shockingly surprising how one's attitude changes when you do something out of sheer interest and curiosity vs when you are asked to do something.

Well, "that thing" happened with my "Laravel learning".

I was so pumped up to learn Laravel, and I got assigned to a project in which I have to code - and the framework is Laravel.

Suddenly, all my enthusiasm seems to be lost, and I am struggling to keep up the learning.

It's been a little over 2 months, and while I am still "learning Laravel", I have come to realise how my attitude changed, and that was definitely not for the best.

Now that I have realised this, I am back on track and have brought my best friend "passion" to the project (and my endeavour in learning Laravel).

Once again, restarting... #nazarRakheyo...

Here's the reason/excuse/justification for not updating this thread.

I was learning Laravel (damn it, that's the perfect excuse, especially in the context of this thread).

Anyhow, yes, that's true - I've been learning Laravel, and I don't mean "setup controller, model, views", I mean the whole shebang - routes, to migrations, to form-requests, service-providers, console commands, test-driven-development, using the first party packages (and third party as well), to add oh-so-many features.

Following tools have been added to my tech-stack and I have written more code in last 1 year than I have written in 10 years preceding that.

1. Laravel 9.x
2. Docker / docker-compose
3. Tailwind-CSS
4. Alpine.js
5. Terraform
6. Heroku CLI
7. GCP Cloud Run / Cloud SQL
8. AWS / RDS / Postgres
9. PhpStorm [probably "the-best" investment that I have done, like ever]

Packages/tools that I have been experimenting with:

1. Telescope
2. Breeze
3. Sanctum
4. PHP parallel lint, php-cs, php-md, php-security-checker
5. PestPHP
6. ZSH [z-shell]
7. Bladewind-UI
8. Blade-ui-icons
9. SVG icons, and the same icons as "fonts" - Material UI and devicons fonts

#nazarRakheyo
#keeyAnEyeOut

#forWhatIsComingNext

#dedicatedToTheLegend
#legendsNeverDie