Task 5

Topic: LATEX document typesetting

Submission: You will create file userid_q5.tex and will use it to generate userid_q5.pdf (where userid is your student number). These files must be in the Q5 directory of your repository. Make sure none of the LATEX intermediate files (such as .aux) are included in the repo.

You are a freelance software developer and you are seeking to advertise your skills. Prepare a document in LATEX introducing yourself and showcasing some of the projects you have completed so far.

Your tasks for this assignment:

1. Create a .tex document called userid_q5.tex where userid is your student ID. You must compile this with pdflatex. It may compile with warnings but the compile should not stop with errors.

2. Have a title area which has your name and your key skill or interest. You do not necessarily need to use the \maketitle command for this task; simply have the text laid out nicely.

3. Create a section containing a small biography of yourself, including your education, programming interests and other details. (Note: This information can be fictional; please don’t reveal personal information if you don’t wish to!)

4. Create a second section that contains two subsections: in the first one write a short reflection on how you plan to use the skills learned in this course in future projects. In the second one, write a short reflection on how professional conduct intersects with the creation, deployment and management of modern computing resources such as virtual machines and containers. Be sure to use basic styling techniques such as placing text in italics and in bold face. ("Short" means at least one paragraph but less than half a page for each of the two subsections.)

5. Create a third section containing some information about previous projects that you’ve completed. There should then again be two subsections:

• One subsection contains some maths. This could be anything you like, such as the famous e = mc2 .

• The other subsection contains a table. It should list columns ‘Component’, ‘StartDate’, EndDate, and ’LinesOfCode’, and should have a number of (fictitional) rows. Ensure the table uses appropriate cell alignments.