Greetings! I'm quite new to the Laravel community, so far I'm absolutely impressed with the framework's capabilities and rapid deployment.
Now, to the matter at hand:
I was recently hired by a company as a full-time "App/Web Developer & File/Graphics Designer" (not kidding, actual title on contract), anda few weeks in my employer asks me to take a look at a "Client Portal" that my predecessor had developed for them, so I could make a few upgrades/bug fixes.
Upon inspection I quickly surmised that it was built upon Laravel e began consuming Laracasts "From Scratch" videos and Documentation.
As I progressed with it, the more this projected seemed clunky, disorganised and dirty to me. Now don't get me wrong, I know I'm new to the framework so if I'm speaking nonsense just let me know, but it seems to me that the developer who built this did not make use of most of Laravel's easy deployment and creation capabilities!
It's as if they decided to simply improvise most of the files names, locations, folders, and managed to duct tape it all together to make it seem fully functional.
Alas, for instance, not even the password reset is working!
Anyway, briefing/rant being done now, I'm looking for some guidance on how to go about this project, and also how to explain all this to my employer without seeming like a made up excuse to extend deadlines.
By the way, this was done on Laravel 5.3, and when I joined the company Laravel was already at 5.7, so I'm not really sure upgrading is feasible, considering the "custom" nature of the project.
If anyone's interested, I can setup a temporary FTP to a Dev copy of the project (not using the same databases as live project, and all files inside a subdomain).
Thanks bunches, hope to learn a lot here!
