Oddly enough, one of my greatest fears as we approached the end of the Master's was that I wouldn't know what to do with all the free time I was about to have. This was a strange fear, but, having worked harder on average for the preceding ten months at Berkeley than I remember working for the four years since my undergraduate, it was somewhat rational.
This fear was ungrounded, as it happens. While the first couple of weeks of work were fairly quiet - most of my colleagues being busy with an office move and/or conference, the work quickly came through, in quantity. An impending product launch and some very real ownership over part of that product has meant that while I'm now working hard - I'm enjoying it thoroughly and this is probably, so far, the best job I've had since my internship on the trading floor.
Most of my graduated colleagues seem to be enjoying work and learning plenty, although I was disheartened by the response of one who I ran into on the train. Me, "how's the new job?", him, "well, it's okay, I guess". Not what you should be saying a month into a new job, in my opinion!
Having an income now is rather nice. I've restocked on clothing - having persevered with multiple pairs of ripped jeans for the best part of the year and undergarments that had seen better days.
Sadly, I managed to rip one of my new pairs of jeans within two weeks of owning it. A couple of weeks ago, it rained in Berkeley for possibly the first or second time since February. Having not practiced my wet weather bike handling skills for some time, I managed to wash out on the corner on the way to the BART station. It must have been at some speed because my knee is still very slightly sore, a few weeks later and I had a surprisingly deep graze on both my right knee and elbow. Still, having to host a work day (essentially a day long interview where we work with a candidate), I limped to work and continued as normal.
On the way home that evening, some clown decided to disrupt the legion of Jay-zed fans who were on their way to his concert in the city by calling in a bomb threat at the West Oakland BART station. Since this is the last station before the under-bay tunnel (I do not know what the actual name of this crossing is), the train services across the bay were shut entirely for a few hours. While I admire the lengths this Jay-zed hater went to antagonise fans, I cursed his timing since I was in no state to cycle anywhere in comfort. Not wanting to drop my bike back to the office, I recruited a couple of bemused BART travellers who were also travelling to Berkeley to share (not split, since I obviously had the extra bike) the cost of an Uber back. Being peak hours (i.e. surge pricing) and requiring an Uber XL to carry my bike, the overall cost was near to $80 - even with the 30% summer discount. More pain.
Getting home at about 9:30, after a long day in the office, I then had to tackle the still notably large list of tasks to complete before leaving. While packing itself was fairly straightforward, I spent some time curating music for the plane journey. However, Cowon J3s (mp3 players) have this rather unique bug where if you remove them without ejecting cleanly from a Mac, they effectively temporarily brick themselves. The amusing thing is that the reason I was curating music was my Cowon had previously been bricked in the same fashion. Still, not remembering to test this before leaving home, I ended up discovering this as I boarded the BART to work the next day and spent the 11 hour flight musicless.
Over the weeks since, I've had great fun working remotely from such exotic locations as the coffee shop in San Francisco International Airport to the coffee shop in Vilnius Airport to the coffee shop in Google's Campus London co-working space. Working from home has been fun too, mainly since the discovery of my grandmother's Oreo stash. Lacking a bicycle, with a recovering knee injury and with plentiful delicious food, I'm definitely returning to the US fatter on Monday.
London has been a flood of nostalgia. This is not entirely unexpected since some of my favourite memories are from the times I've spent roaming around this city, whether on bicycle, foot or Tube. This time, like my last visit back at Christmas, I've added to the list of things I miss about the city - at the moment it's largely practical, including but not limited to: the superior hot chocolate, the expansive public transport network, readily available healthcare and lack of obvious social wealth inequality on every street corner.
Sadly, I realise that many of my closest friends here have now moved on, either physically or with their personal lives (marriages, etc.). This is to be expected, of course, but my social life isn't as rich as it once was. Not to say there's nothing attracting me back, but it certainly feels slightly emptier than it used to. Many of my friends are also working extremely hard now, having moved into positions of responsibility and just generally being successful in their careers. There's nothing different here, although it's worrying that I have a steady base of friends who work too much and are hence single. It's not clear what the solution is here, besides work a little less and get out a little more. That's not to say that I haven't fallen into the same trap.
A funny thing happens when I move between the US and the UK now. I refer to the other place as "home". Perhaps I now truly live between the two countries. Over time, the balance will shift more to the US I suspect, as I become more established there. It's surprising how natural a fit it was to live in California, at least given my interests - this is perhaps the reason most people flock to the Bay Area. That said, London (or Watford) will always remain home for me too, so perhaps home isn't one place but many.
Searched for
- Posts tagged 'berkeley'
No comments yet
No comments yet!
As a data collection (and, often, analysis) nerd, I've collected reasonably accurate data on the cost of the whole process of applying to and attending graduate school. Please don't take any of the below as a recommendation for what to do - it is merely an attempt to rationalise and explain my decision from a PURELY FINANCIAL point of view for others who may be considering a similar career move. Note that my motivation was not solely financial and yours probably shouldn't be - if you don't want to be completely miserable for a year or more! The numbers below are all deliberately imprecise - so make your own calculations if you need to. Note also that these figures are for software engineering jobs!
Let's start off with my salary in London before I started my Master's degree. My last position, at Last.fm, paid £37,000 a year. At Last.fm (a subsidiary of CBS Corporation), there was no salary progression and no bonus because they like employees to be dissatisfied with both leadership and their compensation ;-).
I lived with my parents and commuted into work - this meant my monthly disposable income, after taxes, healthcare, commute, food and student loan repayment costs was approximately £1,000. (Note that if I had been living in London and paying rent, my disposable income would have been considerably closer to 0. Also note that if I didn't have so much stuff wrong with me, I would have saved a fair chunk on healthcare.) For two years this money went straight into savings which I have since depleted to pay for tuition.
The overall year cost of the degree was approximately $70,000. Less if you live frugally, more if you don't. I managed to save money on the estimated graduate student budget provided by the university which is excessive if you know how to cook a little and don't eat out all the time. (Prepare your own caffeine too - coffee shops are expensive and you WILL develop a coffee habit as a graduate student here!)
My burn rate here is approximately $2,000 a month - including rent at $800 a month, food, travel and a modest amount of social. I expect that as I start to have free time when starting to work, I'll be spending more a month - closer to $2,500 a month.
Typical salaries for new software engineers with a Master's degree in the Bay Area range between $100K and $125K, depending on your level of experience and the location. Factor in the cost of owning a car if you live in the South Bay, as well as higher rents. If you work in San Francisco, you can quite easily commute in from Berkeley and pay the same rent. If you wish to move to San Francisco though, expect to pay at least $2K a month in rent. Rents in the South Bay (i.e. Silicon Valley) are about $1500. Rent inflation is high though, so I'd advise checking the market rate closer to when you make your decision.
(A side note: Amazon's offer was comparable for the first year - they offer a $90K base salary with a $20K bonus. This is amusing because the immediate cash bonus is a huge incentive for hapless graduates to sign. While rent and tax is lower in Seattle than California, I feel that pegging your base salary at $20K lower than employers in this area is likely to have repercussions in the future if you do choose to move.)
(Another side note: I'm beginning to wonder if international students/hires are offered lower starting salaries than applicants with permanent residency (i.e. a green card) or citizenship. I have very little data to confirm this but it's a growing hunch.)
Assuming the worst case, which is a $100K starting salary and living in San Francisco and approximating tax to 40%, this works out to a rough monthly income of $5,000. Assuming $1,500 worth of living expenses plus $2,000 in rent, this leaves a disposable income of $1,500 a month. This is considerably better than the situation in London where disposable income was close to 0 when renting your own accommodation. However, there's the obvious $70K that has been spent. Assuming no interest rate, a constant income, constant expenses and a diligent saving regime, this will take 46.6 months, or about 4 years to pay off.
Taking the best case, which is a $125K starting salary and commuting in, that gives us a rough monthly income of $6,250. Expenses, as previously mentioned, of about $2,500 - which leaves a disposable income of $3,750. Again, under the same assumptions, we should be able to pay off the $70K in 18.6 months, or about a year and a half.
This figures are based on the assumption that you'll be attending a year long program and do not get any sort of financial aid. I appreciate that many Master's courses are longer - but the actual increase in cost isn't directly proportional to the length of the program since students often get well paid summer internships which offset the extra semester or quarter well. In addition, there's opportunity in courses greater than a year long to get research or teaching assistantships which offset the tuition cost significantly.
Finally, the obvious question is - why not apply for a job in the US directly and save yourself the $70K cost? The answer is: access to employers. The obvious geographic advantage of being able to interview with employers aside, the immigration situation is notoriously tight and, as a non-US citizen, getting work authorization is difficult. As a Master's student, you have the ability to work legally here for a year post-graduation under 'Optional Practical Training'. If you study a STEM subject, there is an optional 17 month extension which helps too. During this period, students can apply for a H1B visa under a separate category reserved for applicants with a Master's or higher level degree from a US university. (They may also apply under the normal category, I hear that it is variable whether this category is over or undersubscribed relative to the normal category.)
I firmly believe that moving to this area has been one of the best things I can do for my career, earning potential aside. Just about every large technology company in the world has an office or their headquarters within 60 miles of where I live. This element of choice means that I can acquire work experience in highly attractive technologies and don't need to compromise on employer. (This compromise happens all too often in London for computer science graduates who have to make the trade off between a high salary in financial services or interesting work in a pure technology company. Here, I think it's possible to have both.)
Let's start off with my salary in London before I started my Master's degree. My last position, at Last.fm, paid £37,000 a year. At Last.fm (a subsidiary of CBS Corporation), there was no salary progression and no bonus because they like employees to be dissatisfied with both leadership and their compensation ;-).
I lived with my parents and commuted into work - this meant my monthly disposable income, after taxes, healthcare, commute, food and student loan repayment costs was approximately £1,000. (Note that if I had been living in London and paying rent, my disposable income would have been considerably closer to 0. Also note that if I didn't have so much stuff wrong with me, I would have saved a fair chunk on healthcare.) For two years this money went straight into savings which I have since depleted to pay for tuition.
The overall year cost of the degree was approximately $70,000. Less if you live frugally, more if you don't. I managed to save money on the estimated graduate student budget provided by the university which is excessive if you know how to cook a little and don't eat out all the time. (Prepare your own caffeine too - coffee shops are expensive and you WILL develop a coffee habit as a graduate student here!)
My burn rate here is approximately $2,000 a month - including rent at $800 a month, food, travel and a modest amount of social. I expect that as I start to have free time when starting to work, I'll be spending more a month - closer to $2,500 a month.
Typical salaries for new software engineers with a Master's degree in the Bay Area range between $100K and $125K, depending on your level of experience and the location. Factor in the cost of owning a car if you live in the South Bay, as well as higher rents. If you work in San Francisco, you can quite easily commute in from Berkeley and pay the same rent. If you wish to move to San Francisco though, expect to pay at least $2K a month in rent. Rents in the South Bay (i.e. Silicon Valley) are about $1500. Rent inflation is high though, so I'd advise checking the market rate closer to when you make your decision.
(A side note: Amazon's offer was comparable for the first year - they offer a $90K base salary with a $20K bonus. This is amusing because the immediate cash bonus is a huge incentive for hapless graduates to sign. While rent and tax is lower in Seattle than California, I feel that pegging your base salary at $20K lower than employers in this area is likely to have repercussions in the future if you do choose to move.)
(Another side note: I'm beginning to wonder if international students/hires are offered lower starting salaries than applicants with permanent residency (i.e. a green card) or citizenship. I have very little data to confirm this but it's a growing hunch.)
Assuming the worst case, which is a $100K starting salary and living in San Francisco and approximating tax to 40%, this works out to a rough monthly income of $5,000. Assuming $1,500 worth of living expenses plus $2,000 in rent, this leaves a disposable income of $1,500 a month. This is considerably better than the situation in London where disposable income was close to 0 when renting your own accommodation. However, there's the obvious $70K that has been spent. Assuming no interest rate, a constant income, constant expenses and a diligent saving regime, this will take 46.6 months, or about 4 years to pay off.
Taking the best case, which is a $125K starting salary and commuting in, that gives us a rough monthly income of $6,250. Expenses, as previously mentioned, of about $2,500 - which leaves a disposable income of $3,750. Again, under the same assumptions, we should be able to pay off the $70K in 18.6 months, or about a year and a half.
This figures are based on the assumption that you'll be attending a year long program and do not get any sort of financial aid. I appreciate that many Master's courses are longer - but the actual increase in cost isn't directly proportional to the length of the program since students often get well paid summer internships which offset the extra semester or quarter well. In addition, there's opportunity in courses greater than a year long to get research or teaching assistantships which offset the tuition cost significantly.
Finally, the obvious question is - why not apply for a job in the US directly and save yourself the $70K cost? The answer is: access to employers. The obvious geographic advantage of being able to interview with employers aside, the immigration situation is notoriously tight and, as a non-US citizen, getting work authorization is difficult. As a Master's student, you have the ability to work legally here for a year post-graduation under 'Optional Practical Training'. If you study a STEM subject, there is an optional 17 month extension which helps too. During this period, students can apply for a H1B visa under a separate category reserved for applicants with a Master's or higher level degree from a US university. (They may also apply under the normal category, I hear that it is variable whether this category is over or undersubscribed relative to the normal category.)
I firmly believe that moving to this area has been one of the best things I can do for my career, earning potential aside. Just about every large technology company in the world has an office or their headquarters within 60 miles of where I live. This element of choice means that I can acquire work experience in highly attractive technologies and don't need to compromise on employer. (This compromise happens all too often in London for computer science graduates who have to make the trade off between a high salary in financial services or interesting work in a pure technology company. Here, I think it's possible to have both.)
No comments yet
No comments yet!
I came to the MEng program having worked for three years and travelled for a year before then - essentially four years out of my undergraduate degree in Computer Science. Even then, the last time I studied maths seriously was in the first year of my undergraduate degree, so about seven years before starting the MEng. That being the case, there were a number of subjects I'd wish I'd brushed up on before starting my coursework at UC Berkeley.
The courses I took were Advanced Robotics, Computer Vision, Introduction to Machine Learning and Applications of Parallel Computing. I'll start with general advice and talk about specific tips for each course at the end. These are roughly in order of how important I think they are.
1) Linear Algebra: This is by far the most important area of maths to cover if you study any sort of graphics or AI course. It was heavily used in all four of my courses. There's a great tutorial online here which is actually written by a UC Berkeley professor. Know this well and you'll spend much less time looking up the basics.
2) Statistics: Know your basic probability and distribution rules. Most of AI is heavily statistics based - in particular, Machine Learning is a lot of statistics and most popular successful AI techniques now tend to be probabilistic. Sebastian Thrun has a great overview paper and is the author of the main text on this area.
3) Optimisation: Optimisation is heavily used in the Advanced Robotics course and appears to be crucial for a lot of cutting edge computer science. I had NO idea what this was before starting and this put me at a significant disadvantage. Learn how to formulate basic optimisation problems at the very least. This book by Stephen Boyd is the definitive text on the subject.
4) Matlab: Matlab is a programming language / development environment that is heavily used by academics. As a software engineer, I particularly dislike programming in it - however, most homeworks assume you will be using it and so most examples and starter code is written in Matlab. While you can submit assignments in Python or other languages, the path of least resistance is to use Matlab. Matlab offers a student license but the department should pay for a license for MEng students. In the meantime, you can use the open source Octave software, which is syntactically very similar.
5) C++: If you intend on taking the Applications of Parallel Computing class (highly recommended - it is excellent) or implementing any actual robotics code, you would do well to become familiar with writing and running C++ programs.
6) Linux: It's useful to have some basic ability with the Linux shell and to have a Linux virtual machine set up. You may or may not use this - depending on whether you take systems level classes or not. I recommend installing Linux Mint in Virtualbox.
7) Git / GitHub: Source control will make your life a lot easier. Learn this well and it will make collaborating with peers on homeworks and your capstone project much, much better. Try the brief interactive tutorial on GitHub.
8) Advanced Robotics: Regardless of what it might imply, this course does not rely on the Introduction to Robotics course. Introduction to Robotics is more about robotic manipulators and 'traditional' robotics. Advanced Robotics is more about the theoretical underpinnings of the algorithms to allow planning, localisation and state estimation. It is not practical at all (much to my disappointment) and is very state of the art. I often struggled to understand the motivation for several techniques until the end of the course. However, you'll find that you know most cutting edge techniques by the end of the semester. It also assumes prior coursework similar to the undergraduate Introduction to AI course at UC Berkeley - so I advise taking Sebastian Thrun's Introduction to AI course on Udacity if you haven't taken anything similar before. This is a hard class but thoroughly satisfying once you complete it!
9) Computer Vision: This is a great course taught by a pair of very energetic, enthusiastic professors (Malik and Efros). Highly recommended.
10) Introduction to Machine Learning: Taught by the same professors as Computer Vision, this class suffers from it's large size - being primarily and undergraduate class. The work load is high but the skills learned are very practical. I'd recommend it but it requires a strong stats background.
11) Applications of Parallel Computing: While the course content itself focusses heavily on scientific computing, the homeworks assignments are very practical and very fun. One of my favourite courses so far.
12) Collaborating: Something I realised quickly was that it was very useful to work together on homeworks with my peer group. You'll often find that you can work together to fill in gaps in each other's background - which is essential when you're coming from another country with a different educational background and sometimes lacking pre-requisite coursework. I wasn't able to work with many people for the Advanced Robotics course and this made the experience almost intolerably difficult. On the other hand, working with motivated peers who were also taking Computer Vision made that class much more enjoyable.
I hope this advice helps - feel free to chime in in the comments below!
The courses I took were Advanced Robotics, Computer Vision, Introduction to Machine Learning and Applications of Parallel Computing. I'll start with general advice and talk about specific tips for each course at the end. These are roughly in order of how important I think they are.
1) Linear Algebra: This is by far the most important area of maths to cover if you study any sort of graphics or AI course. It was heavily used in all four of my courses. There's a great tutorial online here which is actually written by a UC Berkeley professor. Know this well and you'll spend much less time looking up the basics.
2) Statistics: Know your basic probability and distribution rules. Most of AI is heavily statistics based - in particular, Machine Learning is a lot of statistics and most popular successful AI techniques now tend to be probabilistic. Sebastian Thrun has a great overview paper and is the author of the main text on this area.
3) Optimisation: Optimisation is heavily used in the Advanced Robotics course and appears to be crucial for a lot of cutting edge computer science. I had NO idea what this was before starting and this put me at a significant disadvantage. Learn how to formulate basic optimisation problems at the very least. This book by Stephen Boyd is the definitive text on the subject.
4) Matlab: Matlab is a programming language / development environment that is heavily used by academics. As a software engineer, I particularly dislike programming in it - however, most homeworks assume you will be using it and so most examples and starter code is written in Matlab. While you can submit assignments in Python or other languages, the path of least resistance is to use Matlab. Matlab offers a student license but the department should pay for a license for MEng students. In the meantime, you can use the open source Octave software, which is syntactically very similar.
5) C++: If you intend on taking the Applications of Parallel Computing class (highly recommended - it is excellent) or implementing any actual robotics code, you would do well to become familiar with writing and running C++ programs.
6) Linux: It's useful to have some basic ability with the Linux shell and to have a Linux virtual machine set up. You may or may not use this - depending on whether you take systems level classes or not. I recommend installing Linux Mint in Virtualbox.
7) Git / GitHub: Source control will make your life a lot easier. Learn this well and it will make collaborating with peers on homeworks and your capstone project much, much better. Try the brief interactive tutorial on GitHub.
8) Advanced Robotics: Regardless of what it might imply, this course does not rely on the Introduction to Robotics course. Introduction to Robotics is more about robotic manipulators and 'traditional' robotics. Advanced Robotics is more about the theoretical underpinnings of the algorithms to allow planning, localisation and state estimation. It is not practical at all (much to my disappointment) and is very state of the art. I often struggled to understand the motivation for several techniques until the end of the course. However, you'll find that you know most cutting edge techniques by the end of the semester. It also assumes prior coursework similar to the undergraduate Introduction to AI course at UC Berkeley - so I advise taking Sebastian Thrun's Introduction to AI course on Udacity if you haven't taken anything similar before. This is a hard class but thoroughly satisfying once you complete it!
9) Computer Vision: This is a great course taught by a pair of very energetic, enthusiastic professors (Malik and Efros). Highly recommended.
10) Introduction to Machine Learning: Taught by the same professors as Computer Vision, this class suffers from it's large size - being primarily and undergraduate class. The work load is high but the skills learned are very practical. I'd recommend it but it requires a strong stats background.
11) Applications of Parallel Computing: While the course content itself focusses heavily on scientific computing, the homeworks assignments are very practical and very fun. One of my favourite courses so far.
12) Collaborating: Something I realised quickly was that it was very useful to work together on homeworks with my peer group. You'll often find that you can work together to fill in gaps in each other's background - which is essential when you're coming from another country with a different educational background and sometimes lacking pre-requisite coursework. I wasn't able to work with many people for the Advanced Robotics course and this made the experience almost intolerably difficult. On the other hand, working with motivated peers who were also taking Computer Vision made that class much more enjoyable.
I hope this advice helps - feel free to chime in in the comments below!
No comments yet
No comments yet!
A number of the incoming MEng students have asked for advice when making their decision to come to Berkeley and one question appeared repeatedly - is the MEng degree regarded any differently by employers to a conventional MS?
From my personal experience interviewing at ~ 14 tech. companies in the Bay Area and having spoken to recruiters and so on - no, it is not.
Generally the Master's degree will get you a slight hike in starting salary but the rest of the process will usually be the same as graduate applicants with a Bachelor's degree. Employers typically hire university graduates into the same entry level software engineer positions (unless you have prior experience - and even then, this will account for a neglible salary hike, since they'll anchor your salary to a 'new grad' salary).
To an employer, a Master's degree is a Master's degree - regardless of whether it is a Master of Engineering or a Master of Science. They may question why it is shorter than normal but the retort to this is that it is a professional program - and not intended to be preparation for a PhD.
The main caveat with getting the MEng degree appears to be its lack of preparation for a PhD program. It isn't the case that having a MEng from Berkeley will make it any easier to get into a PhD program since, aside from some graduate level coursework, you won't have additional research experience. (Although it may slightly upgrade your resume if you went to an unheard of school previously.)
I would also advise prospective applicants to take with a pinch of salt the claims that employers covet the 'Engineering Leadership' aspect of the courses. While these courses are valuable in their own right and may help alumni to advance up the management ladder faster, most employers aren't aware of this aspect of the program and look more for engineering talent than management promise in their new graduate hires.
At some point I will follow up this post with a more detailed one outlining my interview experience and suggestions for how to approach your job hunt. (Be warned, it involves creating a spreadsheet, so get rid of any prejudice against spreadsheets now.) Generally though, in the Bay Area, it is extremely easy to get interviews for CS positions and I don't see any reason why, with adequate preparation, any MEng graduate should be forced to accept an offer they aren't completely enthusiastic for. Indeed, I was able to get my role of choice at a very exciting startup.
(Note I mention CS positions. Product management positions are much harder to come by. Also, other majors sometimes struggle to find jobs.)
From my personal experience interviewing at ~ 14 tech. companies in the Bay Area and having spoken to recruiters and so on - no, it is not.
Generally the Master's degree will get you a slight hike in starting salary but the rest of the process will usually be the same as graduate applicants with a Bachelor's degree. Employers typically hire university graduates into the same entry level software engineer positions (unless you have prior experience - and even then, this will account for a neglible salary hike, since they'll anchor your salary to a 'new grad' salary).
To an employer, a Master's degree is a Master's degree - regardless of whether it is a Master of Engineering or a Master of Science. They may question why it is shorter than normal but the retort to this is that it is a professional program - and not intended to be preparation for a PhD.
The main caveat with getting the MEng degree appears to be its lack of preparation for a PhD program. It isn't the case that having a MEng from Berkeley will make it any easier to get into a PhD program since, aside from some graduate level coursework, you won't have additional research experience. (Although it may slightly upgrade your resume if you went to an unheard of school previously.)
I would also advise prospective applicants to take with a pinch of salt the claims that employers covet the 'Engineering Leadership' aspect of the courses. While these courses are valuable in their own right and may help alumni to advance up the management ladder faster, most employers aren't aware of this aspect of the program and look more for engineering talent than management promise in their new graduate hires.
At some point I will follow up this post with a more detailed one outlining my interview experience and suggestions for how to approach your job hunt. (Be warned, it involves creating a spreadsheet, so get rid of any prejudice against spreadsheets now.) Generally though, in the Bay Area, it is extremely easy to get interviews for CS positions and I don't see any reason why, with adequate preparation, any MEng graduate should be forced to accept an offer they aren't completely enthusiastic for. Indeed, I was able to get my role of choice at a very exciting startup.
(Note I mention CS positions. Product management positions are much harder to come by. Also, other majors sometimes struggle to find jobs.)
1 comment posted so far
wrote at 11:48 am on Sat 8th Aug -
Is the situation really that bad for operations research graduates in M eng as suggested by your text in the parenthesis at the end
The end is quite clearly in sight. Although I wasn't looking out for it, it's come straight at us, like a hapless raft approaching Victoria Falls. Well, not quite like that, but whatever, I'm not great at analogies.
Another thing I recently didn't see approaching was the pothole just outside our flat's carport on Panoramic Hill. In a somewhat sleep deprived and annoyed state, I cycled up the hill and veered rapidly to the right as a careless SUV driver careened down the hill towards me. As it turns out, he decided to stop somewhere up the hill and I didn't need to evacuate my road position as quickly as I thought. It also turns out that the dark, water-marked road surface was hiding a rather unpleasant occupant - a small pothole about the depth of an American cup. (For my British readers, this is about 250% the height of a typical English tea cup.) Luckily, I fared better than my last brush with potholes - electing to fall comically to my side into a puddle rather than somersaulting multiple times over my handlebars at 60 kmph.
Either way, the point is - this Master's program is very nearly over. If last semester flew past at great speed, this semester has somehow flown past at an even greater speed. We have just under 4 weeks until graduation and the deadline for submitting my Master's thesis has since passed. Luckily it turns out the professors who have kindly agreed to read it don't need 4 weeks to read 15 pages of double spaced text. Phew. What this means though, is that while my colleagues are beginning to wind down (just a little), I still have this cloud hanging over me. Soon though, it will be gone!
The last 5 weeks of so have given me a rather interesting taste of life in the Bay Area. On the BART into San Francisco, I struck up conversation with a chap sitting next to me. He seemed normal enough - at least for this area, working as a freelance graphic designer and having tattoos on his hands, arms and a rather disturbing bandage on his neck. He mentioned he had been mugged earlier in Oakland and was struggling to figoure out how to get home to north of San Francisco - having lost his laptop, wallet and phone and having been unable to get hold of his friends using the numbers he knew. Long story short, I decided to give him some money to get home and he promised to PayPal it back to me. I didn't hear back from him.
A couple of days later, Gita and I performed some actual work in Oakland using our unmanned aerial vehicles. While I was waiting for Gita to arrive, I noticed a guy walking away on the pavement with a unique bandage on his neck. Looking closer, I realised it was the same chap who I'd lent money too. I didn't manage to catch him up but at least I know the Oakland part of his story was probably true. Oh well, there's a small chance my act of charitable giving might have made someone's day a little better and I'll take what I can get.
Gita and I spent most of the rest of the day performing an aerial survey for a local architecture firm who are designing an extension to the Bay Trail that will connect it to Lake Merritt, a lake in Oakland. This is a bicycle and walking/running trail that will eventually encircle the entire Bay Area. Details of safely operating a robot in public aside, the photographs taken by the borrowed GoPro we used were somewhat unique and I'm somewhat proud of them. You can see a sample of these here on our lab's webpage.
That weekend, in San Francisco, I wandered out to pick up some takeaway food. 15 minutes after I reached my friend's apartment there was a drive-by shooting just a block away. I found this somewhat fascinating but my more rational friend was visibly shaken by the incident.
The final, more amusing incident, was that in the course of organising a singing telegram for my friend's birthday (a gift that my friend had apparently wanted for years: Americans are odd), I submitted a quote request online. This quote request was miscategorised as a request for a clown and over two days I received about 15 phone calls from local Bay Area clowns soliciting for business. In the end a singing gorilla was actually organised and was received very well.
While there's still a steady pipeline of work to finish, I can already taste the sweet freedom that I'm sure to get bored of eventually. (The grass is always greener, right?) I'm looking forward to being able to sleep consistently, exercise consistently and to having time to cook for myself. I'm also looking forward to having an income and feeling less anxious everytime I pay for food and drink! See you on the warmer, greener other side.
Another thing I recently didn't see approaching was the pothole just outside our flat's carport on Panoramic Hill. In a somewhat sleep deprived and annoyed state, I cycled up the hill and veered rapidly to the right as a careless SUV driver careened down the hill towards me. As it turns out, he decided to stop somewhere up the hill and I didn't need to evacuate my road position as quickly as I thought. It also turns out that the dark, water-marked road surface was hiding a rather unpleasant occupant - a small pothole about the depth of an American cup. (For my British readers, this is about 250% the height of a typical English tea cup.) Luckily, I fared better than my last brush with potholes - electing to fall comically to my side into a puddle rather than somersaulting multiple times over my handlebars at 60 kmph.
Either way, the point is - this Master's program is very nearly over. If last semester flew past at great speed, this semester has somehow flown past at an even greater speed. We have just under 4 weeks until graduation and the deadline for submitting my Master's thesis has since passed. Luckily it turns out the professors who have kindly agreed to read it don't need 4 weeks to read 15 pages of double spaced text. Phew. What this means though, is that while my colleagues are beginning to wind down (just a little), I still have this cloud hanging over me. Soon though, it will be gone!
The last 5 weeks of so have given me a rather interesting taste of life in the Bay Area. On the BART into San Francisco, I struck up conversation with a chap sitting next to me. He seemed normal enough - at least for this area, working as a freelance graphic designer and having tattoos on his hands, arms and a rather disturbing bandage on his neck. He mentioned he had been mugged earlier in Oakland and was struggling to figoure out how to get home to north of San Francisco - having lost his laptop, wallet and phone and having been unable to get hold of his friends using the numbers he knew. Long story short, I decided to give him some money to get home and he promised to PayPal it back to me. I didn't hear back from him.
A couple of days later, Gita and I performed some actual work in Oakland using our unmanned aerial vehicles. While I was waiting for Gita to arrive, I noticed a guy walking away on the pavement with a unique bandage on his neck. Looking closer, I realised it was the same chap who I'd lent money too. I didn't manage to catch him up but at least I know the Oakland part of his story was probably true. Oh well, there's a small chance my act of charitable giving might have made someone's day a little better and I'll take what I can get.
Gita and I spent most of the rest of the day performing an aerial survey for a local architecture firm who are designing an extension to the Bay Trail that will connect it to Lake Merritt, a lake in Oakland. This is a bicycle and walking/running trail that will eventually encircle the entire Bay Area. Details of safely operating a robot in public aside, the photographs taken by the borrowed GoPro we used were somewhat unique and I'm somewhat proud of them. You can see a sample of these here on our lab's webpage.
That weekend, in San Francisco, I wandered out to pick up some takeaway food. 15 minutes after I reached my friend's apartment there was a drive-by shooting just a block away. I found this somewhat fascinating but my more rational friend was visibly shaken by the incident.
The final, more amusing incident, was that in the course of organising a singing telegram for my friend's birthday (a gift that my friend had apparently wanted for years: Americans are odd), I submitted a quote request online. This quote request was miscategorised as a request for a clown and over two days I received about 15 phone calls from local Bay Area clowns soliciting for business. In the end a singing gorilla was actually organised and was received very well.
While there's still a steady pipeline of work to finish, I can already taste the sweet freedom that I'm sure to get bored of eventually. (The grass is always greener, right?) I'm looking forward to being able to sleep consistently, exercise consistently and to having time to cook for myself. I'm also looking forward to having an income and feeling less anxious everytime I pay for food and drink! See you on the warmer, greener other side.
No comments yet
No comments yet!
Posts