There are many, many guides to successfully completing a post grad degree, so I am not going to add to them. Instead, this is a list of things, based on personal experience, that you can do to make it somewhere between very difficult and impossible to complete that Masters or Doctorate degree.<\/p>\n
To be clear, I\u2019m talking about the degrees which are mostly, if not entirely, based on research and a dissertation, not coursework.<\/p>\n
Initially this looks like it\u2019ll work out fine. Work Monday to Friday, work on the degree on Saturday and Sunday. For the first few months it does work fine.<\/p>\n
But there\u2019s one thing that a dissertation requires and that\u2019s a large amount of dedicated time. Time to read the literature. Time to come up with the hypothesis or research questions. Time to design an experiment. Time to conduct that experiment. Time to revise the experiment, conduct it again, revise again, conduct again\u2026 Time to analyse the results. Time to write up the results. Time to edit, rewrite, edit, rewrite, edit\u2026<\/p>\n
As the months pass, and as the initial enthusiasm and fun fades, so it becomes harder and harder to spend most of the weekend on the research, weekend after weekend after weekend, for a couple of years<\/p>\n
Sure, it\u2019s possible to complete a Masters degree while working full time, but it\u2019s like playing a game on Insane difficulty level.<\/p>\n
The SQL community are a great bunch of people and there\u2019s a lot of encouragement to jump in and get involved, for many good reasons<\/p>\n
Posting on forums is great in many ways, it boosts your confidence, it gets you recognitions and it\u2019s a good way to get to know features you\u2019ll never use in your regular job.<\/p>\n
Blogging and writing are a great way to share knowledge, and there\u2019s a thrill from watching the page hit count go up, from the first comment, from the complements, especially when your blog post gets referenced by others as the authoritative article on a subject.<\/p>\n
But it takes time. Lots of time. Articles can take days of work, blog posts can take anything from a few minutes to many hours depending on the subject and the depth of the post. Presenting takes lots and lots of prep time. An hour-long presentation can easily require a day of prep, and that\u2019s once you\u2019ve done several presentations. The first one can take many days of writing slides, rewriting slides, writing demos and rehearsing the presentation several times. Forums will take every minute you\u2019re willing to give to them and more, and there\u2019s the constant temptation of \u2018just one more post\u2026\u2019<\/p>\n
And where\u2019s that time going to come from? The time that would otherwise have been spent on the research and dissertation.<\/p>\n
I\u2019m probably going to get flak for this, but it has to be said.<\/p>\n
As an industry in general, we are too reluctant to ask for help. I don\u2019t mean technical help (though that too in many cases).<\/p>\n
We are too eager to put on a pedestal the person who works 12 hours a day, 6 days a week, the person who pulls all-nighters on a regular basis, the person who never takes vacation because he \u2018doesn\u2019t have time\u2019. We\u2019re conditioned to see extreme hours worked as a sign of dedication, of what is needed to get ahead.<\/p>\n
It\u2019s not heroic. It\u2019s not required. It\u2019s not something to be admired.<\/p>\n
It\u2019s stupid.<\/p>\n
Long days are sometimes required, weekend work is sometimes necessary, but they both should be the exception, not the norm. Excessive overtime, if needed to meet deadlines, should be followed with a discussion on what went wrong such that the overtime was required. Was the estimation inadequate? Was the project analysis flawed? Did the scope creep (or gallop)? Were people working on multiple projects at the same time while the project plan expected them to be dedicated? Were assumptions not met or essential infrastructure delayed?<\/p>\n
If overtime is frequently required, then management has failed at their job. A developer working 12 hours a day, 6 days a week for months on end is not a sign of dedication or heroics, it\u2019s a sign that someone, somewhere in management is not doing their job properly.<\/p>\n
This kind of workload and times are not sustainable. They lead to mistakes and buggy code, they lead to burnout and they lead to people, top people, walking away and never coming back.<\/p>\n