Restructure the whole thing

[cyberhck]

We really should try the following so the entire repository is maintainable.
We add programs into separate individual files. We can add tests if applicable, or we try to compile and see if that worked. Additionally, we can use make to test a few more things, probably passing set of arguments should yield certain result.

I'd say for example, we've a quadratic equation program, we write in a C file, and not on LaTex or md file, we write in a good way easy to read and maintain, probably chunk them into functions, and if possible, unit test them, else at least do a compile.

thoughts? @fsmk/vtu-lab-manual-maintainers

If everyone agrees, I'll add a sample program (probably refactor a program) with all the tests, and structures over the weekend and send a PR then we can slowly migrate and make it really easy to maintain, easy for students to follow, and a consistent code style.

I'm not sure what's going on with syllabus, or does it make sense to only do this with newer syllabus at first, and slowly refactor the older ones later?

[cyberhck]

note to self: think code linting, testing on travis, building the whole file, using Makefile.