Hi Vittorio, you mean that it created a buyer, an item and an invoice? Yes, I agree, this was just an example to illustrate the open-closed principle, in real-life example I wouldn't create it all in one method.
Amazing, I was just out of a round of interviews for Senior dev where I probably was in top 5 and did not get the job.
One of the topics that I want to improve so it's not a diferentiator vs the other candidates is to properly explain SOLID Principles usage in Laravel. A quick answer could be, "the vendor packages are closed to modification because once they are updated you lose the changes, but open to extension if you need extra functionalities that the vendor does not provide"
Hi Povilas, but the invoiceController class doesn't go against the first principle of Single Responsibility?
Hi Vittorio, you mean that it created a buyer, an item and an invoice? Yes, I agree, this was just an example to illustrate the open-closed principle, in real-life example I wouldn't create it all in one method.
Amazing, I was just out of a round of interviews for Senior dev where I probably was in top 5 and did not get the job. One of the topics that I want to improve so it's not a diferentiator vs the other candidates is to properly explain SOLID Principles usage in Laravel. A quick answer could be, "the vendor packages are closed to modification because once they are updated you lose the changes, but open to extension if you need extra functionalities that the vendor does not provide"