Quick & Dirty: MarkDown to PDF

Writing from a developers point of view and writing from a PBA studies examinators point of view are very different things. Developers want to write code and slam documentation into MarkDown files they can track with git (assumption). PBA examinators want a footnote drenched, printable document, that belongs back in the 1970s (fact).

For my last hand-in I’ve created a quick & dirty script, that does just that to your MarkDown files. Continue reading “Quick & Dirty: MarkDown to PDF”

Why I believe in MarkDown

When I first learned of MarkDown I was torn between having to write academical papers in software like Microsoft Word or Apple’s Pages. Both are surely functional Programs, even though I’d always preferred Open or Libre Office, for the sake of standards and an open world.

In my studies as a Multimedia Designer in Denmark I even handed in some papers that were written in HTML and compiled to PDF.

That clearly was not the most practical, but for me the most bearable of these alternatives. Plain text is just great, especially for people who write a lot or the ones that code on a somewhat daily basis. Continue reading “Why I believe in MarkDown”

git every day

I’ve previously mentioned, that I installed GitLab 5.0 and it’s been pretty cool since. Today I just want to write about what I use git for in my everyday life.

If you want a quick recap of what git is, visit their official site or read my previous post Why you should start using git now

What I’ve been doing so far

About 1.5-2 years ago I started getting into git, because I wanted to take part in developing software smartly, in teams and take part in global open source projects.

I keep my WordPress plugins on github, parallel to the WordPress plugin repository and a couple of months ago I started fixing minor mistakes in other projects. Continue reading “git every day”