15-organising.Rmd

# (PART) BUILDING YOUR FUTURE {-}

# Organising Your Future {#organising}
You might find it a bit scary thinking about your future. You might be tempted to procrastinate making important decisions, especially when they are potentially life changing, see figure \@ref(fig:schedule-fig). There is a risk of [thrashing](https://en.wikipedia.org/wiki/Thrashing_(computer_science)) or getting stuck in a `do-nothing` or [`busy waiting`](https://en.wikipedia.org/wiki/Busy_waiting) loop. This guidebook is here to help you break out of that loop. One way to breakout of an unproductive loop is to organise and schedule some time every week where you work on personal development and job applications. Doing good applications takes time and you'll probably find you can't do as many applications as you might like, especially when you consider [Hofstadter's law](https://en.wikipedia.org/wiki/Hofstadter%27s_law): It always takes longer than you expect, even when you take into account Hofstadter's Law.

```{r schedule-fig, echo = FALSE, fig.align = "center", out.width = "100%", fig.cap = "(ref:captionschedule)"}
knitr::include_graphics("images/is-it-just-me.png")
```
(ref:captionschedule) The biggest waste of time is the time spent not getting started on a project. Your future might seem big and unknown but it's really not as scary as you might think and getting started can be surprisingly enjoyable. [New Project? Every time…](https://bryanmmathers.com/new-project-every-time/) by [Visual Thinkery](https://visualthinkery.com/) is licenced under [CC-BY-ND](https://creativecommons.org/licenses/by-nd/4.0/)

Your future is bright, your future needs organising, so let's start organising your future.

## When and where can I start building my future ? {#make}
How you start organising your future will depend on what stage of your degree you are at 

* First year pathway, see section \@ref(year1)
* Second year pathway, see section \@ref(scheduling) 
* On placement or internship pathway, see chapter \@ref(starting)
* Final year pathway, see chapter \@ref(debugging) 


In section \@ref(by-quantity) and \@ref(by-quantity) we discussed the importance of timing in your job search. *When* you apply for jobs will determine *what* kind of jobs are available because most graduate schemes and graduate jobs follow a rhythmic recruitment cycle of some kind. How many jobs you apply for is largely a function of how much time you spend doing it. The more time you spend, the more applications you can do.

We haven't explicitly discussed the timing and organisation of the activities outlined in the preceding chapters:

1. *Designing your Future* in chapters \@ref(rebooting) to \@ref(computing)
1. *Testing your Future* in chapters \@ref(debugging) to \@ref(speaking)

Let's imagine you could precisely specify all of the tests using [make](https://en.wikipedia.org/wiki/Make_(software)) in a `makefile` or specify them somehow in your favourite Integrated Development Environment (IDE). Ideally, you'd like to automatically run these tests, so that you can build your future systematically. You'd like to repeat these tests periodically, e.g. once a day, week, month or whatever your schedule is, similar to [build automation](https://en.wikipedia.org/wiki/Build_automation) in software engineering. Attempts to automate aspects of job applications and interviews have so far had very mixed results. [@airesume; @dastinai] But, as another thought experiment, let's image it was possible

## Breakpoints {#bp6}
(ref:breakpoint)

```md
* PAUSE ⏸️
```

* So what's in your make file? 
* How often will you run it?
* Which tasks can you automate?
* Which tasks are always going to be manual?

```md
* RESUME ▶️
```

## Second year pathway {#scheduling}

If you're a University of Manchester student, the live *Coding your Future* (COMP2CARS) workshops sessions are also here to help, every Tuesday at 4pm.  COMP2CARS complements the second year tutorials (COMP2TUT) at the University of Manchester and takes place in the same slot as COMP2TUT when you meet your personal tutor. See your timetable at [timetables.manchester.ac.uk](https://timetables.manchester.ac.uk/). The outline is:

* Weeks 0: Welcome
* Weeks 1 and 2: COMP2TUT, meet with personal tutor
* Weeks 3 to 5: Seminars in Lecture Theatre A, Crawford House
* Week 6: Reading week - take a breather
* Weeks 7 to 10: Seminars in Lecture Theatre A, Crawford House
* Weeks 11 & 12: COMP2TUT, meet with personal tutor


### Week 8: Choosing & achieving {#week8}

Tuesday 12th November, 4pm: 

* Choosing Your Future, see chapter \@ref(writing)
* Achieving Your Future, see chapter \@ref(achieving)

### Week 9: Speaking {#week9}

Tuesday 19th November, 4pm: 

[Penny Gordon Lanes](https://uk.linkedin.com/in/penneygordon-lanes) from the Careers service will be talking about services offered to help you prepare for interviews: [www.careers.manchester.ac.uk/applicationsinterviews/interviews/](https://www.careers.manchester.ac.uk/applicationsinterviews/interviews/)


### Week 10: Speaking again {#week10}

Tuesday 26th November, 4pm: Speaking Your Future, see chapter \@ref(speaking)

### Week 11: Tutor {#week11}


Tuesday 3rd December, 4pm: Meet your tutor 

### Week 12: Tutor {#week12}


Tuesday 10th December, 4pm: Meet your tutor 

Items ~~crossed out~~ below have been completed

### Week 0: Experiencing {#week0}

~~Welcome week, starting 16th September:~~

~~Welcome week activity, welcome back to year 2 with Afroditi Galata and *Experiencing your Future*: a Q&A panel of returning Industrial Experience students with chaired by Duncan Hull.~~ 

~~* Thank you to our panelists for sharing your expertise with incoming year 2 students, see [www.cdyf.me/experiencing](https://www.cdyf.me/experiencing) 🙏~~

### Week 1: Debugging {#week1}

~~Tuesday 24th October at 4pm:~~ 

~~* *Either* COMP2TUT: Meet your tutor see [digital.cs.manchester.ac.uk/student-groups/](https://digital.cs.manchester.ac.uk/student-groups/)~~
~~* *OR* COMP2CARS: Debug your CV (self assessment) using section \@ref(checklist) and: ~~
    ~~+ Get robotic feedback on your CV from [careerset.com/manchester](https://careerset.com/manchester)~~
    ~~+ Read *Debugging your future* (chapter \@ref(debugging))~~ 
    ~~+ Read *Hacking your future* (chapter \@ref(hacking))~~
    ~~+ Complete the `CV Essentials pathway` if you haven't already done so at [www.careers.manchester.ac.uk/services/ondemand/pathways](https://www.careers.manchester.ac.uk/services/ondemand/pathways/)~~

### Week 2: Debugging {#week2}

Tuesday 1st October at 4pm

* ~~*Either* COMP2TUT: Meet your tutor  (if you didn't meet them in week 1)  see [digital.cs.manchester.ac.uk/student-groups/](https://digital.cs.manchester.ac.uk/student-groups/)~~
* ~~*OR* COMP2CARS: Debug your CV (self assessment) using section \@ref(checklist) and: ~~
    + ~~Get robotic feedback on your CV from [careerset.com/manchester](https://careerset.com/manchester)~~
    + ~~Read *Debugging your future* (chapter \@ref(debugging)) ~~
    + ~~Read *Hacking your future* (chapter \@ref(hacking))~~
    + ~~Complete the `CV essentials pathway` if you haven't already done so at [www.careers.manchester.ac.uk/services/ondemand/pathways/](https://www.careers.manchester.ac.uk/services/ondemand/pathways/)~~

### Week 3: Hacking {#week3}

~~Tuesday 8th October, 4pm: Hacking Your Future see chapter \@ref(hacking)~~


### Week 4: Finding {#week4}

~~Tuesday 15th October, 4pm: Finding Your Future, see chapter \@ref(finding)~~


### Week 5: Exploring {#week5}

~~Tuesday 22nd October, 4pm: Exploring Your Future, see chapter \@ref(exploring)~~

### Week 6: Resting {#week6}


~~Tuesday 29th October, Take a breather, its reading week~~

### Week 7: Writing {#week7}


~~Tuesday 5th November, 4pm: Writing Your Future, see chapter \@ref(writing)~~


## First year pathway {#year1}

If you're in your first year, here's five steps you could take to start *Coding Your Future*:  

1. Join a society, or start your own see section \@ref(other)
1. Attend a hackathon, either as a participant or co-organiser, see section \@ref(tinkering) 
1. Contribute to Open Source Software, see section \@ref(opensource)
1. Volunteer to build your skills, see section \@ref(volunteering)
1. Apply for spring insights in first year, see section \@ref(areuexperienced) 

See chapter \@ref(experiencing) for ways you can start *Experiencing Your Future* in your first year.