Home » Posts tagged 'applications'
Tag Archives: applications
Well, well, well… It’s been a looooong year, but here we are, at the very end of it. I thought I would reflect on some of my running goals, the peaks and troughs, and what running resolutions I might set for 2017.
So how did it go? All in all, I don’t think it was a bad year. There wasn’t a lot of progress in pacing, per se, but I was a lot steadier and more consistent in getting out for runs, and I had some really good months (unsurprisingly during the summer).
|January||32.4 km over 4:51 across 6 runs||It’s hard to remember this far back…||The usual New Year weather blues!|
|February||94km over 8:31 across 16 runs||Picking up training volume again, including a 54:23 10k||The number of runs that are just shy of 5k|
|March||90.4km over 8:13 across 14 runs||First 10k+ run (13.7km in 1:13)||That my average pace starts a slow decline here|
|April||94.2km over 9:06 across 15 runs||Steady as she goes…||Noticeable pace decrease, including two 10ks (57 and 59)|
|May||131.8km over 12:05 across 13 runs||Two half-marathons (first ever at 1:57, second at 1:58)||That I was too cheap to pay for the Runner’s World app training…|
|June||91km over 8:16 across 12 runs||I at least managed an 8-miler||I couldn’t face a long long-run this month, having done halves in May|
|July||112.82km over 10:06 across 17 runs||A good increase in the number of runs||Quantity =/= distance|
|August||136.4km over 12:25 across 22 runs||Still on the up, including some 10-milers and some 8-milers||Average pace is down, though…|
|September||113.1km over 10:47 across 19 runs||Holding fairly steady and enjoying the sunshine||Only one 8-miler|
|October||60km over 5:32 across 12 runs||Despite travel and moving house, I’m still managing a few runs a week||Most runs now pretty short|
|November||70.75km over 6:29 across 15 runs||Got in a 10k and a 5-miler||Pace is still trending down|
|December||76.18km over 7:05 across 14 runs||Starting to pull back up again, distance-wise||Still a bit slower|
I have found myself slightly frustrated with Strava after discovering that it didn’t have the delightful Excel download feature of RunKeeper, so pulling together my stats was a bit of a hassle. I’m going to have to think about whether I try Nike+ Run Club (which I think lets you download stats), or the paid-for version of Strava.
- The two half-marathons I did, just by myself.
I’m happy that my first one ever was supposed to be a 10-miler that I just pushed on with, and it came in sub-2:00. But the fact that I only managed two and then my half-marathon-a-month plan fell apart is indicative of a fairly basic fact: I’m not that interested in longer distances.
- Running is more part of my everyday routine than in 2015.
There was almost no week when I didn’t run at all. I had some niggles, like shoulder cramps (yep, a weird one) or tight ankles, but still trundled on when and how I could.
- That the half-marathon-a-month plan fell by the wayside so easily.
I’m partly baffled by quite why this happened, and partly glad that it helped clarify quite what I’m running for.
- That I still haven’t figured out how best to get speed workouts into my routine.
I do these workouts intermittently, when I’m feeling guilty or in a clear rut. If I want to “progress”, which I guess means getting faster, then I need to take these more seriously, as well as strength training, etc.
- That my pacing seems to have decreased.
If this is a function of running longer, then it’s disappointing that I haven’t picked up a great deal across the year, which may reinforce the point above about speed workouts.
It’s that time of year, and I’ve been refreshing my academic CV to see how it’s taking shape. Although I’m a part-time PhDder and work full-time in another industry, I try to be as active as I can in academic endeavours, so there’s plenty of updates and tweaks to be made.
Taking a look at some colleagues’ CVs for tips and hints on structure, etc., it began to strike me that those of us who are interested in digital humanities face a challenge: where do our programming skills belong?
Sometimes, it’s easy. There is a role or project that involved particular development work. But increasingly people put HTML, or CSS, or Java alongside French or Japanese, with a “fluent” beside them (I’ve yet to see anyone using an ILR or CEFR scale marking, though). The first time I saw this I smiled a little smile to myself. Well, we’ve got to try to get these things on the CV somehow. But after a while, I started to wonder: when we say this, do we mean it? As a literary scholar, I have strong feelings about the fact that words mean things. And as a spouse of a professional developer, I feel sceptical.
What does it mean when we say we are “fluent” in a programming language? Is coding ever so smooth, graceful and effortless as speaking or writing in a ‘natural’ language? Do we ever code easily and accurately in the same way as we might speak our mother tongue?
The rate of bugs or errors in your average professional code—the type produced by developers at Apple or Google—is about 1 every 10 lines. If one were to have a typo or lexical error in every 10 sentences of written work, one’s supervisor would raise a red flag!
Now, perhaps we may quibble about whether a line of code is equivalent to a sentence (or, indeed, the comparison to a mother tongue), but I think the point stands. The rate of error is much higher in professional “fluent” code than in academic written prose.
Similarly, professional coders do not for the most part store the whole or majority of the language intuitively in their brain in the same way as one’s mother tongue. The reliance on coding reference materials, such as Stack Overflow, is higher than the reliance on linguistic ones, such as dictionaries. Tales of developers finding a perfect and helpful answer on such repositories, only to discover that they themselves submitted it years before, are legion. What would be the equivalent in terms of a ‘natural language’? Stumbling across the idea of using consonance to convey a certain effect, having forgotten that it existed?
All in all, reading “fluent in HTML” on an academic CV strikes me as a category mistake. And it makes me wonder about their French, too…
I’ve been taking MOOCs for years, watching sites like Coursera and EdX develop from a small handful offerings into something decidedly and globally on-trend in the higher education sector. At first, in 2012, the motivation for many of the courses that sprang up seemed to be love of learning, and providers seemed to offer liberal arts education at the far reaches of the word ‘liberal’, a utopia of free access to knowledge that could democratise education across the globe. However, MOOCs have so-far proved a bit of an echo chamber.
Although it only covered EdX, a recent MIT-Harvard study found that 40% of MOOC participants are teachers, an astonishing statistic. 70% of all participants already have BAs. An earlier study, which focused on UPenn Coursera students, found that students tended to be young, well-educated, and employed. MOOC participants are well-educated people who value learning and education. Those without access to tertiary education, particularly in developing countries, are under-represented. Meanwhile, philomaths with relatively high levels of privilege flock to subjects that can bolster their CVs and enhance their careers, choosing computer science over the humanities at a ratio of nearly 4:1, and MOOC sites are developing ways to monetise their offerings: verified certificates, ‘nanodegrees’, and ‘specialisations’.
This suggests that, without further efforts to deliver on the oft-quoted democratising aims, MOOCs will become a new tool in the increasingly frenetic CV arms race, often starting at undergrad level, which already sees students throwing thousands at professional qualifications (the UK legal profession is a prime example and has been for years…), and those with masters degrees taking entry-level jobs.
At the moment, MOOCs’ pay-off for participants is still unproven. Whether they will prove valuable on CVs will depend on how employers across industries respond to verified certificates, ‘nano degrees’, and ‘specialisations’. However, the increasingly professionalised offerings (a course on Public-Private Partnerships starts imminently on Coursera) suggest a wholesale divergence from what many had initially hoped would be the result of the MOOC explosion. Capitalising on the insecure labour market with career promises is the clear intention of some sites. Udacity’s front page recommends “pick which programming language to learn first based on salary, geography, application types and recent trends”. There is no particular love of learning here. Even the suggestion that the decision is based around the “lifestyle you want” is suspect. Salary comes first. It’s all about the ££.
To me, one of the most worrying elements of the MOOCs-in-an-arms-race is the gender disparity, in developing countries, between male and female participants in MOOCs (30%) versus in traditional education (10%). We already know women often have to appear more qualified than male competitors in order to land a job. Taking a MOOC in one’s spare time to boost one’s CV, particularly a paid one one leading to a verifiable certificate or the completion of a particular ‘track’, might become another hurdle to women participating on equal terms with men in the labour market. Advantages and disadvantages will continue to accumulate on either side of a MOOC-divide, and those with more free time and free cash will push even further ahead.
So it is with a rather heavy heart that I must confess to having succumbed to the lure of Coursera’s ‘signature track’. I could say that it was all because of the allure of the Leadership specialisation that might be coming soon, which course announcements have taken care to mention. I could point out that I’ve taken a few leadership-related MOOCs before, and I’m particularly passionate about women’s leadership roles. I could claim to be investing in MOOCs as a whole (or Coursera, at least). All of these things played a part in the decision. However, what tipped me over the edge was something incredibly petty: the ‘signature track’ badge in the Coursera forums.
I don’t even particularly like the forums. They’re badly designed, leading to many repetitive discussions/comments because submitting something is more valued than contributing to a good conversation. But it was the marketing of the ‘signature track’ within them, seeing the little badge repeatedly, that reminded me of the reasons one might pay for the signature track, proving effective on me in a way that the countdown for signing up had never been.
The first time I posted in the forum after I’d paid up, the badge came up next to my name, and I felt immediately suspect. I looked again at the badge, one of the few on display on that particular page. And it occurred to me, rather too late, that in fact those little badges are more questionable than the direct positioning of MOOCs as weapons in a CV arms race, because they make inequality tangible in the day-to-day space of the course. Why should fellow students know that I am on the ‘signature track’? That information is imposed on my fellow students because I have chosen to pay up. Within a course, signature track students might have access to additional resources, and will have a different certificate at the end of it, but the forums, where posting is often mandatory, are a digital space that now explicitly privilege some participants over others. Coursera’s marketing proves more effective by virtue of creating a hierarchy of students. If an arms race between MOOC participants starts within the pedagogic space, then the education on offer is ‘liberal’ in only the shallowest sense of the word.
I’m really rather ashamed of myself for signing up to it.
I posted a few days ago about the decrease in the number of book reviews that I’ve been posting recently, focusing instead on recipes, TV and film reviews, and other things that come under the ‘personal’ tag. In thinking more about this decrease in my emotional drive to read fiction, I realised that it began around two months ago when – surprisingly – I finally submitted my PhD applications.
For quite a while I’ve been slowly circling a prospective PhD topic. There were a few candidates at the start of this year, but I’ve whittled it down to one now, and I have been pulling out books from the wonderful London Library on it for a while (sidebar: that place is aces, and I recommend all London/England-based folks to consider a membership). It could still go in two directions, though: English Lit or Comp Lit. I’ve not decided which, yet, and I might even consider applying to both.
The difficulty is that, in general, I am more attracted to Comp Lit programmes in the States than those in the UK, perhaps because they are longer, allowing for greater opportunities for language learning and exploring literature in two-plus languages. However, I’m disinclined to go to the States, in part because I have a fair amount of student debt in the UK already, and in order to pay it off I really need to stay full-time employed (or get good funding) for at least part of my PhD work. In the grand scheme of things, I think it is preferable to do PhD work full-time, not least because it allows for greater involvement with journals, conferences and activities like undergrad teaching that can be really important for pursuing an academic career afterwards. I’m not sure I’m quite committed to that yet either, though! There are plenty of good reasons to avoid academia, at least right now, with the state of higher education as it is (in both the UK and the US), but it does still call to me…. For example, I once turned down a pretty darn good graduate school deal because I wasn’t sure academia was a good bet, but it didn’t take very long for me to be drawn into the part-time MA that I’m doing now.
There are plenty of great bloggers out there with useful tips for graduate students and those hoping to do graduate work (Justin O’Hearn, for example), but the decision to embark upon a research degree is always difficult, and as much as advice as there is out there, it’s always a personal and (I think) irrational choice.
I think I’m going to have to bite the bullet and at least email programme directors about how they structure part-time work. There’s no reason not to anymore, and it’s October (tomorrow)! Deadlines are looming, really. Unless I wait until next October when I will have my final MA result, but it will be that little bit harder to solicit references (the part I hate most of applications).
Oh, it’s a dilemma alright!
So, occasionally I get emails from Experience.com. I don’t know when this started happening—I think at the end of my first year I got home and found that they had sent me some junky mail, and happened to think it might be interesting, so it’s probably my own fault. I generally don’t read their emails, but occasionally they suggest an article or whathaveyou that might look interesting, so I read it. Often for the mocks. Sometimes they’re so simplistic, I have to assume my cohort is comprised mainly of idiots. Other times, they’re just funny in and of themselves.
Take this one by Rands Pantelones (you can find his own blog here), entitled A Glimpse and a Hook: Confessions of a Hiring Manager. It has some good advice: people are reading your resume fast; everyone knows buzzwords are going to be fudged, so don’t be an idiot and put down something you can’t talk about; etc. It’s also full of hypocrisy.
Take this paragraph:
Sound like a human. Here’s a doozy, this intern says he “planned, designed, and coordinated engineers efforts for the development of a mission critical system”. ZzzzzzzzzzZzz. What did this guy actually do? I honestly don’t know. Let’s call this type of writing style resume mumbo jumbo and let’s agree that usage of this style is tantamount to saying nothing at all.
Okay, probably not bad advice, right? Indeed, rather good advice, as not only is this lacking in concrete information, but it sounds down-right suspicious, doesn’t it? This is an intern, after all. I would be very inclined to take Mr. Pantelones seriously if only for one thing. He can’t take his own advice. The entire essay begins thus:
While hiring phenomenal teams is the most important thing I do, I’m balancing that task with the fact that I need to build product and manage the endless stream of people walking into my office.
Product? Product? What product, sir? Mumbo jumbo much? “Product” probably tops quite a few of those lists about office mumbo jumbo that people despise (I just can’t be bothered to find them right now).
Oh, and “hiring phenomenal teams” sounds like something that comes out of every recruiters’ and employers’ brochure to make themselves better and more important than they really are, so they will get our attention (ditto “endless stream”).
Rands suggests that he’s made some pretty bad hiring choices, and he does seem to love his mumbo jumbo, as much as he claims otherwise. So, if someone were treating his resume the way he argues all hiring managers do, would he get a job? I think all Experience.com readers should think about that when they’re wondering how much credence to give to his depiction of resume consideration. What a shame there’s no comments section on that site…
That being said, I think Mr. Pantelones is probably good at his job. He just goes to show how prevalent all the ‘mistakes’ (embellishment, mumbo jumbo, etc.) really are in the job market-place these days, and you sort of have to laugh a bit at the irony, don’t you?