Prologue
There are several articles, for example , or . They all share one drawback: the authors shared their early learning experiences or their preparation experiences. This is certainly useful, but it leaves room for speculation.
I will discuss how to obtain a master's degree in Software Engineering at the University of Liverpool (UoL), how beneficial it is, and whether it's worth studying when you're 30 and feel that everything is going well professionally.
This article may be useful for both young individuals just starting their journey in the industry and seasoned developers who, for some reason, missed out on getting a degree or have a degree from an institution that is not well-regarded globally.
Distance learning
Choosing a university
Ranking
Ranking is certainly a rather manipulative concept, but the numbers indicate that the university isn't all that bad (). This university is also recognized in the UAE, and those guys can be picky about diplomas. If you are considering relocating to one of the countries where your experience doesn’t count towards obtaining a residence permit, UoL could be a good option.
Price
Price is a subjective matter, but for me, Stanford's prices are prohibitive. UoL allows you to obtain a degree for around 20,000 euros, divided into three payments: before the course, in the first third, and before the dissertation. Perhaps you can negotiate a lower price.
Language
This may not be relevant for you, but I have a preference for British English. This is likely due to fond memories of .
Time
Based on the reviews, I couldn't determine how much time I would need for studying. Some people reported losing touch with their families and studying from morning till night, while others announced a manageable workload. In the end, I trusted the information on the university's website. At the time of writing, I couldn't find that landing page, but it mentioned 12-20 hours per week.
Admission
The admission process was surprisingly simple. I called a representative from UoL, we discussed my interest, and agreed to continue the conversation via email.
The university did not request confirmation of language proficiency; the commissions were quite satisfied with my level of spoken and written English. This was pleasant, as it saved time on the courses I had already started, and did not require confirming my obviously existing 6.5-7 IELTS scores.
Next, I was asked for a description of my entire work experience and a letter of recommendation from my supervisor. This was also not a problem — I have been working in software for over ten years.
An important factor was that I have a degree in management, which the committee recognized as a BSc; thus, my experience and bachelor's degree allowed me to apply for an MSc.
Training
Modules
Everything is quite logical: eight modules, a dissertation, obtaining a diploma, and throwing a cap.
You can find information about the modules and study materials . In my case, these are:
- The Global Technology Environment;
- Software Engineering and Systems Architecture;
- Software Testing and Quality Assurance;
- Professional Issues in Computing;
- Advanced Database Systems;
- Software Modelling and Design;
- Managing Software Projects;
- .
As you can see, nothing supernatural or unrelated to software development. Since for the last five years, I have been organizing development more than writing code (although I still write some), each of the modules was relevant for me. If you feel that Managing isn't beneficial for you, then an alternative to Software Engineering could be .
Preparation
There is no need to purchase physical books. I have a Kindle Paperwhite from the time when the ruble was doing fine. If necessary, I upload articles or books downloaded from or another hub. Fortunately, my student status allows me to authenticate on most foreign portals related to academic articles.
In fact, this is a treat because I no longer want to read subjective experiences about, for example, the usefulness of certain practices , but rather want a comprehensive study conducted using the described methodology.
Process
On the day the module starts, its structure becomes available. Learning at UoL consists of the following cycle:
- Thursday: the module starts
- Sunday: deadline for the discussion post
- Between the discussion post and Wednesday, you need to write at least three comments on the posts of your classmates or instructor. You cannot write all three in one day.
- Wednesday: deadline for individual or group work
You receive an instructor, a PhD, ready to answer any questions, learning materials (videos, articles, chapters from books), requirements for individual assignments and posts.
The discussions are truly fascinating, and the academic requirements for them are the same as for the assignments: use of citations, critical analysis, and respectful communication. Overall, the principles of academic integrity are upheld.
If we put this into words, it amounts to: 750-1000 for individual work, 500 for a post, and 350 for each response. In total, you will write about two thousand words a week at a minimum. In the beginning, it was challenging to generate such volumes, but by the second module, I got used to it. There's no room for filler; the evaluation criteria are quite strict, and in some assignments, it can be difficult to fit within the required volume without exceeding it.
On the Sunday following Wednesday, grades become available according to .
Workload
I spend about 10-12 hours a week on studying. This is catastrophically low because I know for sure that many of my classmates, who have more experience, spend significantly more time. I think it's very subjective. You might spend more time and feel less tired, or perhaps much less time and not feel tired at all. By nature, I think quickly, but I need a significant amount of time to rest.
Helpers
I use , which is free for students, and I also pay for a and . Quote management can also be done in RefWorks, but it seemed too complicated and inconvenient for me. I use proofreading out of habit; it helps less and less. I'm not sure if they are the cheapest on the market, but I haven't found better in terms of price/speed/quality.
Relevance
I can definitely say that despite my efforts to keep up with industry trends, UoL gave me a great push. First of all, I was forced to remember/learn the basics necessary for managing both development and the development itself. The individual work requirements do not allow outdated materials and encourage the latest verified research, while the instructors love to ask tricky questions in discussions.
So, from the perspective of knowledge being provided from the frontlines — yes, it is.
Interest
I doubt I would have enjoyed studying at UoL if it resembled a typical course on Coursera, where you essentially find yourself alone. Group work, connecting students from different corners of the globe towards a common goal, really livens up the process. Just like discussions. For instance, I had a considerable debate with a classmate from Canada, who works in the banking sector, regarding the concept of anti-patterns and where to classify Singleton.
It was extremely engaging to write 1000 words on the topic 'Analysis of benefits and limitations of distributed systems', as well as working with my partners on the group project 'Enterprise Database System Architecture' in the previous database module. In it, we played a bit with Hadoop and even analyzed something. Of course, at work, I have Clickhouse, but I changed my attitude towards Hadoop after I was compelled to defend and analyze it from all angles.
Some assignments included, for example, a week on 'Transaction analysis, evaluation and comparison' that involved simple tasks related to the 2PL protocol.
Is it worth it?
Yes! I don’t think I would have delved so deeply into IEEE standards or modern approaches to risk management in IT. Now I have a system of reference points and I know where I can turn if necessary, and what exactly exists. this exists. Definitely, the program and the necessity of knowledge beyond it (considered in assessments) push boundaries and throw you out of your comfort zone.
An indirect benefit
The necessity to write and read a lot of text in English ultimately allows:
To write in English
- To think in English
- To write and speak almost without mistakes
- Of course, there are many English courses cheaper than 20,000 euros, but you would hardly turn down something like Lingualeo on discount.
Конечно, существует множество курсов английского дешевле 20-и тысяч евро, но от этого вы врядли откажитесь как от lingualeo по-скидке.
Epilogue
I am confident that investing in knowledge always yields the greatest return. I've seen many developers in interviews who once stagnated in their comfort zone and became obsolete.
When you’re 30 and have been helping businesses develop technological projects for several years, there’s a significant risk of stagnation. I am sure there’s some law or paradox that describes this.
I try to supplement my learning through Coursera and the literature I read as needed for work, but I still feel that I would like to do more. I hope my experience can help someone. Feel free to ask questions — I’ll be happy to answer.
Source: habr.com
