Learning from ‘Computer Books’

I just uncovered this book review on William E. Shotts Jr., The Linux Command Line: A Complete Introduction (No Starch Press 2012) I left as a half-done draft months ago. In it, I found a long collection of thoughts on learning programming from books and what common problems are. The book review will still follow at some point, but these are some of the examples of common problems with ‘computer books’. The typical computer book: a long detail-rich, reference-like read I like the Intro to the Linux commandline a lot, but also found that it was very long in pages but the content isn’t super dense. So it was a very long read and I’m always ambivalent about books which are reference-like and super-long. I am a person who likes to read and even I put off reading this book for a long time. I read a chapter every morning while having breakfast. Some chapters I just skimmed because they didn’t contain

read more Learning from ‘Computer Books’

The LaTeX Ninja: Topics and the pseudonym

Since starting this blog about a year ago, I am at a point where I think my choice of typical topics is more or less stable. I also have used the WordPress “categories” to add many of these topics and also hope to develop some of them into some sort of series. What these ‘series’ are for, is explained in the category descriptions now. The Ninja: A pseudonym Also, I wanted to quickly address another thing: My pseudonym. I have already talked about why I started this blog multiple times before. There is a basic mission statement in the about section. Long story short, the ‘LaTeX Ninja’ was a goal, not a label I put on myself. It doesn’t describe ultimate LaTeX wisdom (for that, I have sometimes used the term ‘LaTeX Guru’). If the LaTeX journey you can join on this blog were a computer game, you you start out as a ‘LaTeX Noob’. As you gain experience, you

read more The LaTeX Ninja: Topics and the pseudonym

Algorithms, Variables, Debugging? Intro to Programming Concepts

Since I am about to prepare a workshop on natural language processing and a pre-workshop-workshop where I need to quickly/crashcourse introduce my (non-digital) Classicist friends to some basics on programming, let me share a list of programming concepts I compiled with you. I would be happy for your suggestions and comments regarding mistakes. I will probably publish this together with some key concepts of quantitative text analysis (blogpost to come) on a cheatsheet or as slides for you later 😉 Intro to key concepts of programming This list of concepts is not super-structured and meant to work as a ‘reference tool’ as well as a text to be read, so I tried to give it a more or less useful ‘chronology’, meaning that later parts kind of build on earlier ones. I start off with what a computer program or algorithm actually is and how we translate between source code (the code we write) and the code which gets fed

read more Algorithms, Variables, Debugging? Intro to Programming Concepts

Three typical conflicts between DH and ‘Normal Humanities’

In this post, I wanted to name the three most important sources of conflict between DH and non-DH people, according to me. There would probably be many more things one could mention, but I wanted to discuss those three to show one thing: The first one is (almost) completely avoidable and the second and third ones nicely show the contradictory nature of thoughts which cause conflicts between Digital and ‘Normal’ Humanists. Disclaimer: Since they are written up by someone in the DH, it could sound to you like I’m saying it’s the NH’s (Normal Humanist’s) fault but that’s not at all what I’m trying to say. (Remember I feel like I’m half-NH myself anyway. And see the Epigrammetry discussion of the D and the H.) I’m just starting from the arguments I get thrown at me (thus from the Normal Humanists’ perspective) and respond why I think they’re not universally valid (DH perspective). However, it would work just the same

read more Three typical conflicts between DH and ‘Normal Humanities’

Is learning how to program like learning a foreign language?

Is learning how to program like learning a foreign language? Well, it’s a definite “yes and no” from me. I think many people oversimplify this. And then they say that their programmer friends think the same way to ‘prove the point’. Mostly I bite back the question of how many ‘real languages’ the programmer friends have learned or even learned to a native-like level. Because I think that there are some quite important differences. Since I just read this brilliant article The Ancient Case Against Programming “Languages” by Patrick J. Burns on Eidolon (Apr 24, 2017), I thought I could contribute some of my thoughts on the topic as well. They stem less from the interest in not losing funding for second language education, but rather from some of my own experiences in “second language programming education” or whatever one might call it – the act of learning programming (in your 20ies at earliest) after having learned multiple natural languages as

read more Is learning how to program like learning a foreign language?

A systematic training progression for programming?

As some of you might know, I am currently a fellow, aka at my personal writing retreat at Wolfenbüttel. And I decided to combine this with some sort of a training camp for my bouldering progress because you do need to have some breaks from writing during the day anyway and I can’t always watch Bones or create CV templates. You might have been following some of my bouldering on epigrammetry, the blog, or epigrammetry, the Twitter.   Training progressions in sports Also very few of you might know as well, I used to train a lot for long-distance running (10k) during my teens. So I know what training progressions are. I used to have detailled training plans, eating regimes, supplements to take and all that jazz. I stopped at some point because my immune system kept bullshitting me and as an ambitious person, I couldn’t take the idea of having to start from scratch after a half-year of being

read more A systematic training progression for programming?

Don’t call it a database!

When I started this blog, one of my promises and goals, apart from LaTeX-Ninja’ing, was to demystify the Digital Humanities for non-DH people. For a long time I have watched and I think one of the big mysteries of the DH still persists in Normal Humanists’ heads and thus, really needs demystifying. You might have guessed it, I want to explain why DH people will cringe if you call digital resources ‘databases’ which are not, technically speaking, databases. Is it ok to call any digital resource / corpus a ‘database’? We know, that’s what you tend to call a digital corpus. But in most cases it’s not correct, it’s a pars pro toto. A database is just one possible technical implementation, but the term is used more broadly for any ‘digital base of data’. By laypeople, at least. A pars pro toto stylistic device is a Humanities’ thing, right? You do get stilistic devices. So you can also understand why

read more Don’t call it a database!

How to improve at programming when your current position doesn’t require it & Online Learning Resources

Have you ever felt like you would like to get better at programming, maybe even get a position involving more programming some day but the fact that you currently don’t really need it at your current position seems to hold you back? This post is for you. Daily practice is key for improvement You need daily practice if you actually want to improve. You already need daily practice just to keep your skills sharp during a time where you don’t need to use them. Also, if you don’t even have programming skills yet, you probably are too tired after work to sit down and work on a private programming project. But you should. Programming is a skill which takes a long time to learn. That is, if you want to reach a decent skill level. This means that you have to start regular practice long before you actually need that skill or need to apply for a job, if possible.

read more How to improve at programming when your current position doesn’t require it & Online Learning Resources

Your 24 hours. Time management or How to get to know yourself while organizing your life. Part II

Today, I am yet again happy to present the second part of the latest LaTeX Noob guest post:   Last time, I told you about four important steps to organizing your life. They were: Know your priorities. Learn to say “no”. Leave your comfort zone. Never back down. If you want to re-read the last post, you can find it here! So, time management. You will need a calendar, let’s start with that. Take your phone, open your Google calendar. Start. It is actually that easy. You have to know the most important basics. When do I work, what are my main working hours? Do I like a silent or slightly more lively environment for my work? Am I a morning person or a night owl? When will I need a break, when do I want to go to sleep? When am I meeting my friends, when do I spend time with my partner or my family? What do I

read more Your 24 hours. Time management or How to get to know yourself while organizing your life. Part II