A possible solution to a technical assignment.
I was trying to apply a functional programming approach (which I love so much) as much as it was possible. The project mostly consists of pure functions, the only control structure being used is if, there is no variable declared with let, and there are very few mutations in general.
I was trying to build the project (with special focus on the front-end part) as close to production-ready as possible.
Therefore I was concentrating a lot on:
- performance
- usability
- accessibility
- reusability and composability
- maintainability and readability
- testability, and testing in general
The repository consists of two applications:
- a server application located in the
/serverfolder - a client application located in the
/clientfolder
The server and the client applications were meant to run together.
It probably would have made sense to break down the client application further to an actual application and a component library, but I found that unnecessary for a project of this size.
You can read more about both applications in their respective README.md files.
I made a few assumptions while completing the assignment:
- I assumed that that no authentication towards the server is required – although this is most certainly not true.
- I assumed that the server and the client run on the same domain (hence there are no CORS issues to deal with).
- I assumed that the server would respond to
GETrequests. - I assumed that
nameandemailwould be available for every employee/manager – although this might not be true.
I am following the “commit directly to master” branching strategy.
If any of this was to be released in any way, or if multiple developers were to work on this project, I would probably recommend Git flow.
Check the commit history. My commit messages are sometimes almost as hilarious as my comments.
MIT, have fun!
Made by Bence A. Tóth.
Feel free to reach out at tothab@gmail.com.