Picture the scene: you're working your first day at the new job, all eager to get to work with all these shiny new technologies that make development a breeze and improve the quality of life. And then you are handed with your first assignment. But the project that you open is not the company's biggest, brightest, most important project. It's not even the second most important one. With rising dread, the dawning of an understanding building deep inside your mind finally gives form to those two words, the words most abhorred by all programmers, software developers, coders, hackers and testers out in the world:
Legacy system.
You've been handed a legacy system. A summary briefing takes place, which actually doesn't take long since all they can tell you is that the previous person working it was some guy called Gurd and nobody has any idea when Gurd actually even resigned. The handover is over in almost an instant.
You are left with simple instructions: "Make the tests pass, and provide a tester with instructions on how to install it and run the tests. I don't care what you do or how you do it, as long as the tests pass. Also, if you want to demonstrate your mastery over PHP and legacy projects, go ahead and make the project more presentable and up-to-date - as long as the tests pass."
- Fork this repository, and push all the changes that you make to your forked copy.
- The instructions for how to run the app and the tests should be added to the repository's README.md file (this one).
- Important: the file README.md must also describe which parts of your solution were not made from scratch - this includes but not limited to usign generative AI such as ChatGPT, copying code from StackOverflow or other online resource or using any other existing resources such as Google search results. If the entirety of your submission was made from the ground up by yourself, please state this as well.
- Once finished, reach out to your recruitment contact in Planet to let them know you have finished the assignment.