New Year’s Resolution – start an MSc

New Year! New Me! I’m crap at sticking to my multiple resolutions. I think I did okay on last year’s resolutions. So this year, I’m just making a single one. At the start of the G…

Terence Eden’s Blog

Two years later and I'm *so* close to finishing my #MSc.

Tomorrow I have my penultimate meeting with my supervisor to discuss my dissertation.

In two weeks, we'll go through the final *final* draft (v1.final.final.docx)

A month from today I had it in.

Then, at some point in January, I do the viva.

And then done?? Finally done???

My #MSc meeting went well! I've got a few tweaks to make and have to reduce the wordcount.

Then it is all the lovely formatting. I currently use Google Docs for ease of editing on multiple machines, but I'm thinking of moving to #Markdown & #PanDoc to produce the final product.

Less than a month to do go until the deadline. I should probably stop mucking about on Mastodon!

Looks like the easiest* way of formatting my MSc #Dissertation will be exporting it from Google Docs as ePub.
Then unzipping it.
Extracting the HTML.
Tidying it up.
Then formatting it into Markdown (for storing in Git), ePub (for distribution), and PDF (for weirdos).

* Well, I like a good challenge!

Argh! I can see my academic advisor making notes on my #MSc dissertation's Google Doc!

I'm sure they'll be helpful. But all I want her to say is "Job done, go to the pub."

Gonna have to wait until Wednesday to dig into them.

ARGH!

Notes were pretty positive. A few typos and formatting issues. One section needs an extra bit of analysis, one needs a few more details.
Hopefully have this #MSc submitted next week!

Final meeting with my #MSc supervisor and…

Really positive! Direct quote "any other changes I suggest would just be nitpicks."

So, this weekend, formatting this bad boy into PDF (🤮) and submitting to the evils of #TurnItIn.

Got bored of reading my #MSc dissertation back to myself so…

I've finally made use of my AWS credits and am forcing a robot to read it aloud to me.

Thanks Polly!

I know it is an old hack, but using #TTS to listen back to what you've written is a *great* way to find typos, grammar mistakes, and weird phrasing.

I swear, every time I export my #MSc dissertation, I find another formatting error.

Still, 10,901 words DONE! Will be submitted this weekend come hell or highwater.

😻
OK! Today's task, reformat my #MSc into Markdown.

Then export to HTML, ePub, PDF, TTS, etc.

Going to sleep on it and submit tomorrow.

@Edent

I've been using Quarto recently, and have been amazed at how easy it is to build up a good looking book / website. You likely already have a plan, but I didn't and got something medium-sized stood up in less than half a day 🤯

This docs site:
https://quarto.org/

Is driven by this Quarto markdown & yaml:
https://github.com/quarto-dev/quarto-web

Quarto

An open source technical publishing system for creating beautiful articles, websites, blogs, books, slides, and more. Supports Python, R, Julia, and JavaScript.

Quarto
@analyst42 I'll give it a go. I'm finding pandoc a bit of a pain.

@Edent I think they're closely related, but Quarto seems to have very few rough edges to get caught on.

I was sceptical when it was released, but have become a convert in the last couple of weeks. I edit in RStudio, but I think there are options for VScode, etc too

@analyst42 @Edent I've heard good things about the documentation for #Quarto which can only be a good thing!
@analyst42 @Edent also we discovered in an #NHSRconf2022 workshop that if you use RStudio in Visual mode and copy across something like Wikipedia with links it automatically converts to markdown in both #Quarto and #RMarkdown incl hyperlink formats.
@analyst42 @Edent Quarto is a nice wrapper around pandoc and absolutely has a VSCode (or Codium) plug-in available if that’s your jam.
@sellorm @analyst42 Yup - I'm using Codium.
Thanks for the tip.
@analyst42 where's your website?

@chrisbeeley you've got me (again)! It's the "Body of Knowledge" site which I'm setting up for our divisional analysts on internal gitlab. Org charts, systems, access requests, domain info and context that analysts need, onboarding todos, etc. A work in progress that should never be complete...

I'm planning for it to be a low barrier of entry for people to start gaining confidence with git too (only 2 of 5 of us can use git right now).

@analyst42 cool! @Letxuga007 built something similar for us in bookdown. It's a great approach which I must remember to export when we go
@chrisbeeley @analyst42 I got Chris to create a template as I like having blank sites to work from 😃
@Letxuga007 @analyst42 Hugo is my favouritest but looks like Quarto can be good to be quick and simple