As some of you might know, I have written about my Twitter bots on this blog a number of times. Now I decided to shut them all down and wanted to give at least a short explanation of why that was. TLDR: It got unexpectedly expensive and I reasoned the benefit wasn’t really worth the price. Off-topic note on posting schedule: As my devoted readers have probably noticed by now, we’re down to a bi-weekly posting schedule at the most. I have been thinking about it and I’m aiming for two posts per month for now. Actually that’s less than every second week. The point is, I have been reflecting about what makes this blog what it is and I think that’s the good posts I come up with every once in a while. When those add up, that makes the blog a useful resource for time to come. It’s these posts that I want to focus on. And frankly,
read more Why I stopped my Twitter bots
Actually I wanted to write about something different today and had a post already prepared. But then I came across yet another instance of people making negative comments about LaTeX (for apparently no reason and without explaining why they think so) and I guess that made me angry, so here’s today’s post about today’s topic: Why is it so normalized to make snarky side comments about LaTeX? Both in the DH community and otherwise. What is people’s problem with LaTeX? So the offending post, in this case, was this – but I really don’t mean to shit on it because it’s a great post otherwise (I have actually written something similar in Where can I *actually learn* programming? (as DH and otherwise). I guess that’s part of the reason why it makes me so angry. It’s an overall great post by people who are influential in the DH, with a considerable audience and otherwise doing great work. And then a
read more Why is it so normalized to make snarky side comments about LaTeX?
Today’s post is called “The Adventures of the Ninja” which really means sorry for the radio silence and here’s what happend in the meantime. And I think I’m not exaggerating when I say “It has been quite a ride!”. Let’s start at the beginning. The story of me not really being able to blog regularly due to third-year PhD sprint stress has been slowly starting back in Mainz in 2020 (where I was a DH fellow at IEG). However, the general PhD-related stress level only got worse on my subsequent Innsbruck fellowship (Ludwig-Boltzmann-Institute for Neo-Latin Studies) and the weeks leading up to both the submission of my PhD thesis in late May 2021 and me leaving for my fellowhip at the Science History Institute in Philadelphia in early June (the visa process was quite something, to say the least…). Anyway, I ultimately arrived in Philadelphia and was feeling pretty burnt out to be honest. (I have written down some of
read more The Adventures of the Ninja
Today’s post is something at the interface of rant and rambling. While I love being interdisciplinary, it’s also quite the hassle at times which is why I guess most interdisciplinary scholars sometimes wished they weren’t doing interdisciplinary work. There are so many negative stereotypes, like… “You have it easier being interdisciplinary” vs it’s actually twice the work So do you really think that we have it easier? I hate how we always get this reproach that we’re taking the easy route. Can somebody please explain to me what’s “easy” about having to follow the state of the art in multiple fields at the same time? And then not even knowing where to get published because scholars from discipline A don’t understand half of your research and the same in the other direction. I tend to be somewhat “too historical” for the Digital Humanities but then waaaay to technical for the “normal Humanities”. I think being in the DH and doing
read more Navigating interdisciplinarity (as a DH scholar)
I’m not sure if anybody even realized I haven’t been posting lately but this is the longest hiatus we’ve ever had on this blog thus far. It was my normal practice to post pre-scheduled posts only every other week when on fellowships but now I totally went off the (WordPress) grid and I wanted to reconnect with you all. (And also, Easter greetings – if that’s something you care about!) As you might have imagined, I’m quite busy at the moment. I have some typesetting going on (my god, I’m not sure I will ever agree again to typeset a book that I’m also responsible for as an editor, it’s a crazy amount of work!), then I should finish my PhD thesis, I’m on a fellowship where I should finish a translation before heading off to the next fellowship which I hope I can actually get to because it’s in the US. So yeah, busy times. Although I have to
read more Is the Ninja dead? No. But you deserve an update!
Today I wanted to address a common issue I see in troubleshooting LaTeX errors, on StackOverflow and in personal questions. It usually stems from newbies who aren’t yet aware of all the functionality provided by standard packages and thus, try to reinvent the wheel when something doesn’t work the way they expect. Why reinventing the wheel is a problem In my experience, even from me helping people with packages that I’m not all that familiar with myself, it’s always best not to reinvent the wheel (even if you succeed, the result is likely sub-par unless you’re actually really good at what you’re doing). Ask yourself if the functionality you want is something that’s likely to be a common problem. Then maybe somebody has already solved it in a comprehensive way! That’s what packages are for and that’s why they’re (hopefully) maintained by people who have given the problem at hand a good bit of thought. It is very likely that
read more The most important tip for confident LaTeX newbies: Don’t reinvent the wheel! (and try a Minimal Working Example instead)
Since some common objections why some people think learning LaTeX is not worth it or why the oppose LaTeX generally came up again in the Twitter discussion surrounding the recent post LaTeX for Philosophers? Logic and other Shenannigans, I quickly wanted to discuss the three most common objections agains LaTeX (in my experience) and why I think they’re not necessarily valid. Let’s get straight to it! 1) The “I can’t both be a good [insert job title/area of expertise here] AND spend time learning to code” aka the “LaTeX is hard to learn” objection A common argument used against LaTeX, not only in the Humanities, is “I already need all my energy being good at my job and now you want me to learn a new technology to distract me from it?”, like expressed in the following Tweet. But it’s really an extremely common one. The argument is interesting to me because you also had to learn how to use
read more “Learning LaTeX – Why should you care?” Series Part 1: Common Objections against learning LaTeX
For the last two years, I had the responsibility to mentor master’s degree students in the Digital Humanities or to advise those interested in a DH degree. Today I wanted to discuss the most frequently asked question and that is: “Am I ‘techie’ enough for (a) Digital Humanities (degree)?” and partly also “How much math is there in a DH degree?”. This is my Christmas present to you. I’m hoping to do something LaTeX-related again soon but LaTeX templates are currently a go-to relax thing for times when I really need relaxing. And feeling obliged to write about that takes the fun out of it for me at the moment, so sorry, yet another DH post for now. Let’s get straight to it. Part of this post consists of the text of an informational video I made in my responsibility as a mentor for the DH degree programm in Graz. You can watch the video instead, if you like. However,
read more The question of questions: Am I ‘techie’ enough for (a) Digital Humanities (degree)?
To my great surprise, lots of people regularly ask me where I learned to program. I have lots of posts on the subject and even multiple categories on the blog concerning the topic but maybe they’re “too disguised” under obscure titles for willing learners to actually find them. So I decided to give you a short summary with the key takeaways of what I’ve written on the topic so far and the most important links – boths to my other detailled blogposts and also on the resoures I would recommend as of now. However, before the “short summary” of takeaways and suggestions for willing learners, let me start with a deep dive into the very personal side of the question “Where did you actually learn to program?”. Now where did I actually learn to code? A Disclaimer To answer the question “Where did I actually learn to program?”, we need to talk about my journey first. And.. Well, in order
read more Where can I *actually learn* programming? (as DH and otherwise)
Like the title says, I finally finished my own #100DaysofDH challenge. And I haven’t kept my promise to you guys. I (think I) said I would continue blogging every second week but now I’ve left you hanging for a whole month! I’m so sorry. I will try to get back into a regular posting schedule (still reduced until the dissertation is done but I’ll try to at least post every once in a while). Anyways, as I’m nearing the end of my #100DaysofDH challenge (and having declared myself as the worst challenge founder ever in history), I’m starting to get philosophical and the wisdom is coming in. Since I couldn’t deprive you of that, here it comes. (It really isn’t that bad, actually!) Wisdom 1: Read error messages, it works! This one is kind of self-explanatory but once you’re in those long coding sessions, you sometimes forget to do the most obvious stuff. I just recently coded on some stuff
read more I finally finished my own #100DaysofDH – Here’s the wisdom!
Machine Learning is one of those hot topics at the moment. It’s even starting to become a really hot topic in the Humanities and, of course, also in the DH. But Humanities and Machine Learning are not the most obvious combination for many reasons. Tutorials on how to run machine learning algorithms on your data are starting to pop up in large quantities, even for the DH. But I find it problematic that they often just use those methods, just show you those few lines of code to type in and that’s it. Frameworks have made sure that ML algorithms are easy to use. They actually have a super-low entry level programming-wise thanks to all those libraries. But the actual thing about ML is that you need to understand it or it’s good for nothing. (Ok, I admit there are some uses which are pretty straightforward and don’t need to be fully understood by users, such as Deep Learning powered
read more Machine Learning for the Humanities: A very short introduction and a not-so-short reflection
Dear friends, today I want to illustrate some trans-disciplinary crossovers (into the DH) gone wrong. In earlier posts, I have already explained some of the dos (Looking at data with the eyes of a Humanist: How to apply digital skills to your Humanities research questions and Formulating Research Questions For Using DH Methods and What are ‘real’ Digital Humanities and how to get started?), so I assume I have you covered in that area. This is all very happy and positive – but I think I also owe it to you guys to give you an honest opinion of where you probably fucked up. It always hurts to learn these things and it’s more butterflies and rainbow-sprinkles to list all the empowering things you can do. But there are some traps as well and we don’t want you to fall into them. And if you already have, at least now you’ll have the closure to understand why you maybe have gotten rejected
read more Transdisciplinary crossovers into the DH – The Don’ts and what can go wrong
Today I wanted to talk about a common question I come across: Does LaTeX count as programming? Many people dismiss this question directly with a no. But I say the answer is not that simple and depending on how you practice LaTeX can definitely be ‘yes’ much more than you might think! Also, something I really don’t appreciate is people meaning to degrade LaTeX when saying using LaTeX has nothing to do with programming (because it does and most people who think that way have just never seen LaTeX being used more like programming). LaTeX is, strictly speaking, a programming language and Turing-complete. Or rather, LaTeX is a macro package for TeX which is the actual Turing complete programming language. The typesetting-specific tools LaTeX provides probably can’t, however, be considered a full programming language on their own anymore. You could theoretically do anything with it, though it might just not be the easiest possible way to accomplish your ends (unless
read more Does LaTeX count as “programming”?
Today, I want to talk about the Computational Humanities discussion from last year and finally say something with regard to the gender issues in it. I called this post ‘Toxic Masculinity?’ and maybe that’s provocative to you. But maybe it also correctly describes a situation which could come to pass in the DH – a discipline which considers itself so forward-thinking – if we don’t take lurking issues seriously. So this is my reaction. Some disclaimers and considerations I wanted to respond to this discussion when it originally came up. Then I didn’t dare to post it because I was kind of afraid there would be a bad reaction, especially as the slightly-shitstorm-like situation was still fresh and I didn’t want to offend anyone. So I didn’t and now it’s all kind of too late and not up-to-date anymore. But since the general subject is still relevant to me, I decided to use this Corona situation to write up this
read more The Computational Humanities and Toxic Masculinity? A (long) reflection
I don’t usually do self-promotional posts, but today I’ll make an exception: The LaTeX Ninja blog’s DH category was nominated for the DH Awards 2019. So I warmly encourage you to vote for the Ninja and share this – because, as the site’s 2019 FAQ state quite clearly – in the end, the DH awards are a popularity contest. So this is the reason for some shameless self-promotion today. I’ll be back with useful content soon. But this also serves me well in terms of my own blog time management since I’m currently too busy with conference organization to able to provide an insightful thoughtful blog entry. Generally, anyone can vote – you don’t even need to be in the DH yourself! So please do vote and get your grandma to vote too 😉 Am I allowed to vote? Everyone is allowed to vote, voting is entirely open to the public. You do not even have to view yourself as
read more The LaTeX Ninja is nominated for the DH Awards for 2019! Please vote!
Today, I wanted to share a little book review: Scott Young, Ultralearning: Master Hard Skills, Outsmart the Competition, and Accelerate Your Career, Harper Business 2019. (Book website) It won’t be an exhaustive review, but mostly about my one key insight and some reflection on it. If you want a summary, there are countless ones readily available out there already. The following quote sums up the spirit (and main claims) of the book quite well, but it’s really a book packed with solid methods, not just promises: Is it really possible to get an MIT-level education without attending MIT? Or to learn a new language to the point of becoming fluent and conversant in just three months? Or to develop your own video game from scratch and make it a commercial success without being a professional game developer working for a big studio? (source) Apart from the fact that the whole philosophy of ‘Ultralearning’ can be seen as somewhat problematic (see
read more A Book Review of ‘Ultralearning’
In this post, I will explain how you can use the filecontents package to create an ‘inline’ .bib file inside your main document.tex . This can, for example, be useful if your LaTeX gets compiled on a server and your method only allows you to pass one single document. If you wanted to pass a .bib file with it, this wouldn’t work out. Also, for LaTeX releases past fall 2019, the package is no longer required for this functionality, you can use it directly as an environment. I’ll still keep this the way I wrote it. See the documentation here. Premlinaries: How I ended up writing this That’s what I initially wrote this little method for: Our publication system archives data following the single source principle: This means that all representations you want, such as a web site or an output PDF, will be generated from one single document. In our content management system, my data are encoded in TEI
read more An ‘Inline’ bib. file using filecontents
Many people make New Year’s resolutions. Whether they are to lose weight, exercise more or learn a new skill, they often fail. In this post I want to show what pitfalls can be and suggest some good ways of making resolutions stick. Problem: Not having clear actionable goals If you’re not following through on your goals, that might simply be due to a lack of clarity about what they are. For example, “Learn X” is a bad goal because it doesn’t state what exactly you’ll do to learn X, which methods you use, how long you’ll practice or when and where. Swap unclear goals like these with something very concrete and plan when you’ll do it. Is it supposed to become a habit part of your pre-existing daily routine (recommened) or do you see it like an appointment? Then put it in your calender (on auto-repeat so it gets scheduled every week). (You can read some more about this here.)
read more Tracking your progress to make New Year’s Resolutions stick