Member Since 2 Years Ago
4,930 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
try/catch isn't the worst idea either...
@ohffs Thanks for your response; I understand what you're saying about migrating the code into the new app; but it is so bad... it is so difficult and time-consuming to grok the current code nevermind making a necessary change!
I am not an Angular expert, but I suspect that it also follows a similar pattern as the Laravel code.
Maybe I should find new work...
I have inherited a very messy Laravel 4.2 / Angular app - it has an inconsistent, sometimes surprising API; there are no tests; controller are fat and full of procedural code; models are being used more like repositories with special-purpose queries, and none of Eloquent's features are being utilised.
My preference is to do a complete rewrite to 5.4 and not copy a single line of the 4.2 app code into the new app, but I will need to continue to support and maintain the 4.2 app until end of life. My fear is that the current 4.2 app will fall out of step with the developing 5.4 version.
Does anyone here have any similar experience and thoughts they can share?