Hello, I have recently joined a company for the php developer role. Previously I had 1 year experience working with laravel, react. Now at my new job I have to work with legacy code. so php 7 codeigniter 3.1.
As a laravel developer I do find it demotivating to work on a tech that is outdated. I am seeking for suggestions like if I work here for a year or two what should be the takeaway for me. Working on legacy codes and modernizing it ?
Basically the crm we work on is the company's and the whole business run on it. so I am still a littlbit confused. In future when I apply for laravel dev jobs. would this be seen as my weakness or strength ?
Don't be a Laravel developer, be a developer. You can't always dictate the tech stack, and you should be interested in learning new tools. It's definitely a strength.
I haven't worked with CodeIgniter in over 10 years, but I thought it was ok back then. It's not as feature rich as Laravel, but you can write good software with any reasonable tech stack.
If I were you, I'd push for upgrading the versions since PHP 7 is EOL and hasn't received security updates in years.
You got lucky to get your first job with Laravel and React. There's an enormous number of legacy websites out there that serve an important purpose. Developer experience is never the end goal. The end goal is to provide useful software to the end users.
@tanjilurrahman21 You should be concentrating on languages rather than specific frameworks. A PHP developer that has experience with, and can turn their hand to, multiple PHP-based frameworks is going to be far more employable than someone who has only ever worked with and written code in a single framework.
So, stop looking at the negatives and instead look at the positives: you are getting experience with an additional framework that you can add to your résumé, as well as working with and maintaining legacy code. It’s very rare to join a company and be working on a brand new, greenfield project from scratch, so to have demonstrative experience jumping in and working with existing and legacy codebases is only going to be an advantage.
