## New Violin

I’ve been playing violin since I was 7. I went to music school in my hometown, Skierniewice, and spent six years there, finishing what is called a 1st stage music school in Poland. I did not continue to a 2nd stage school and never became a professionally trained musician, but I’ve spent many years playing in different orchestras, first in Skierniewice, later in Warsaw. I enjoyed improvising jazz with my friends in high school, but that ended when I moved out from Skierniewice. Ever since then my only contact with the instrument was through weekly orchestral rehearsals, some practice in between those, and occasional concerts. And when I moved out from Poland in 2008, I left my violin there and did not play since then.

Having an electric instrument was always a dream. I enjoyed listening to Jean-Luc Ponty’s old albums, I was a big fan of Mat Maneri’s avant-garde free jazz, and of course I loved (and still love) the very best jazz violinist of all time, Stéphane Grappelli. At some point a very good friend of mine (whom I spent many years in a couple of orchestras with) bought herself a Fender electric violin, I even had a chance to play them, but did not think of buying an electric instrument for myself back then.

Why have I stopped playing violin after so many years of practice? I guess the main reason was I did not have much time, and I no longer had an orchestra or any other kind of band I could play with. Also, at some point playing violin became a very frustrating experience. Not necessarily because my technical abilities worsened, I feel I’m more or less at the same level of playing technique as I was a couple of years ago, but because my expectations significantly outgrew what I was able to play. I kept listening to a lot of records, and each time I tried playing a piece, I was so disappointed by how bad my performance is that I simply hid the instrument back in the case and played some CDs instead. ‘I am not a professional musician’, I would tell myself, ‘it’s not my job, I shouldn’t be wasting my time on this.’

Then during one of my visits to Groningen, I met Karolina’s friend Tim. Karolina is a cello player, and Tim sometimes plays oboe. Every second weekend or so, they meet at one’s apartment and play music. (Karolina, Tim, if you’re reading this, please skip this paragraph.) Neither is a professional musician, and, seriously speaking, neither plays good. They’re often out of tune, they miss some bars every now and then, and they make a number of other mistakes. Still, their performances are what I’d call decent, or what my friend Erik would probably call adequate. While listening to them I realized it doesn’t really matter if they don’t play like pros, because playing music together and having live music at home is simply an enormous joy. I also realized I miss that. I wanted to go back in the game, wanted to go back to playing music.

There was a problem with an instrument though. Of course I had my old violin back at my parents’ house in Poland, but the instrument was in bad shape (years of neglect) and it actually never was particularly good. One could say that you don’t really need a great instrument if you’re a crappy musician, and that’s one way of looking at it, but then again a bad instrument doesn’t really help if you’re having difficulties playing harmonics or double stops. And then I also recalled that I always dreamed of having an electric violin. I checked the balance of my savings account, looked at how cheap the euro is, went on to http://thomann.de, ordered a Yamaha SV-200 silent electric violin, a carbon bow, a good rosin, a decent (or adequate) shoulder rest, and a lightweight case, pressed ‘buy’ and waited.

Before I tell you how the whole setup feels and sounds, let my give a few words of justification: why this violin and not other?

1. First off, a silent violin allows me to practice technically whenever I want. While unplugged from an amplifier the instrument produces a hardly audible sound, unnoticeable to anyone in another room, allowing me to play late at night using headphones.
2. Secondly, this instrument has a line-out socket, which makes recording multiple parts of a string quartet possible without the need of an expensive microphone (cheap mics + violin = the sound of slaughtering a cat). I always wanted to play Shostakovich’s 1st string quartet, but never had a quartet to play it with. This is no longer a problem.
3. The SV-200 can sound any way I want. If I’m practicing Wieniawski’s caprices, I can make it sound like an ordinary acoustic violin. If I want to imitate Ponty, it produces a full-blown 70s fusion sound.
4. And finally, some practical considerations. It seems it’s much more difficult to damage this instrument than an acoustic violin. It’s less fragile and less sensitive to temperature or humidity.

So now, how does it feel? A bit weird. The fingerboard seems to be a tad shorter than on my acoustic violin. The strings (D’Addario Zyex) seem to be easier to press (the difference is not as big as between an acoustic guitar and an electric one, but still), and of course the sound highly depends on the amplifier. The instrument doesn’t feel at all heavier than an acoustic violin, although according to technical specs it is ~100 grams heavier. I haven’t used a Kun shoulder rest before, but it seems to be better than my old Wolf Forte Secondo. The strings I’ll probably need to replace, I don’t like the sound. In fact I plan on buying a set of Dominants and some Pirastro, and compare which one sounds better. Also, I’ve tested recording a couple of minutes into Garage Band, and it sounded pretty good.

But most important of all, I played some parts of The Four Seasons together with Karolina today. We played together for the first time in many years. It was by all measures musically terrible. But it was an awful lot of fun, too.

## The world is a funny place

So there I was having a lunch at ‘Shanghai Dumpling’ at Taipei 101, when suddenly one of the girls sitting at the table next to mine said: ‘Hey, you’re welcome to eat our dumplings if you want to, because they’re too sweet for us, and we’re quite full anyways’. ‘Thanks!’, I quickly replied, because no one needs to sell me on eating more dumplings, especially if they’re sweet. We started talking about what I’m doing in Taipei, and then it turned out they were Japanese. But there’s noting unusual in meeting two Japanese girls in Taiwan. What’s unusual is to discover one of them speaks a bit of Polish, because she used to study some bit of contemporary European literature, particularly Gombrowicz, and that made her sign up for a Polish language course (of course she didn’t last long, but still).

The world really is a funny place.

## Macbook Pro After 6 Months

Some readers of this blog probably know that for a very long time (ca. 1998– 2010) I’ve been a devout linux user. I’ve been using this system exclusively on all the computers until the Fall last year, when I decided to give Macbook Pro a try (mainly for hardware-related reasons). I’ve written about it a couple of timesalready, but it’s still a subject I keep thinking about, and about which I’m being asked by my friends constantly. ‘Why have you bought a Mac?’, they ask, ‘how is it any better? Don’t you miss freedom? Don’t you miss Gnome?’

Yes and no. But let me elaborate on that.

Continue reading “Macbook Pro After 6 Months”

## In Defense Of The PhD

Recently there’s been a lively discussion on why do people pursue PhD studies, is it good (for them and for the society), is it optimal (for the society and for the universities), and so on. The whole topic is by no means new, but since The Economist’s recent publication, other people expressed their opinions.

I’m 25, I’m a full-time PhD student, and I’d like to put in my oar now.

First off, while The Economist’s article has a number of valid points, it’s very US- and UK-centric. Even though the author refers to some case-studies outside the Anglo-Saxon world, like Germany, Slovakia or Belgium, some of its arguments do not apply at all to most European countries. For example:

One thing many PhD students have in common is dissatisfaction. Some describe their work as “slave labour”. Seven-day weeks, ten-hour days, low pay and uncertain prospects are widespread. You know you are a graduate student, goes one quip, when your office is better decorated than your home and you have a favourite flavour of instant noodle. “It isn’t graduate school itself that is discouraging,” says one student, who confesses to rather enjoying the hunt for free pizza. “What’s discouraging is realising the end point has been yanked out of reach.”

We all read the PhD Comics and we all hear about how many hours of coursework or admin-duties a typical US grad student has. I don’t know how does it look like in other countries, but in Norway, Denmark, Holland and Belgium this is definitely not the case. At some Dutch universities, even if PhD students want to teach, they can’t do that (e.g. because there’s too many of them, or because they are considered underqualified, or whatever). My contract clearly states that I have to spend 25% of my time on teaching, and that’s exactly what I do. One quarter of my overall work time is not much, yet I still gain valuable teaching experience, so it’s a win-win. I know many of my friends who are PhD-students work as TAs for courses taught by their promoters, and that’s usually also not too much work. Apart from all that, a little bit of teaching looks good in your CV, especially if you want to apply for post-doc or other academic positions after finishing a PhD.

There is an oversupply of PhDs. Although a doctorate is designed as training for a job in academia, the number of PhD positions is unrelated to the number of job openings.

There probably is an oversupply of PhDs in the US and in the UK, fair point, but there isn’t one in Norway, and as far as I know not in any of the Nordic countries. Maybe it’s a peculiar situation here, but then again I hear that there’s too many PhD students in The Netherlands, yet all of my friends who recently graduated managed to get post-doc positions in the same country (yes, in some cases it took a while, but still). So let’s talk about the subject that generates most controversy: money.

But universities have discovered that PhD students are cheap, highly motivated and disposable labour. With more PhD students they can do more research, and in some countries more teaching, with less money. A graduate assistant at Yale might earn $20,000 a year for nine months of teaching. The average pay of full professors in America was$109,000 in 2009—higher than the average for judges and magistrates.

Again: US is not the whole world. I’m not going to quote numbers here, but a PhD student in Norway gets a very decent salary, even compared to industry salaries in technology sector. I’m not saying I earn more than a senior programmer at Google, but the money is more than good enough to rent a nice flat (not shared with anyone), eat out from time to time, travel virtually wherever I want and still being able to save some of my monthly pay. The article fails to understand a basic thing behind PhD students’ motivations, though: we’re not after the money. If we were, we wouldn’t be studying philosophy, logic, theoretical computer science or quantum physics. We’d go for an MBA, law or something similar, only to end up working our asses off for McKinsey, Boston Consulting, E&Y or PWC. That is simply not our goal, and while many PhD candidates like to whine about how little cash they have, they either lie, or they simply shouldn’t be doing a PhD at all.

One OECD study shows that five years after receiving their degrees, more than 60% of PhDs in Slovakia and more than 45% in Belgium, the Czech Republic, Germany and Spain were still on temporary contracts. Many were postdocs. About one-third of Austria’s PhD graduates take jobs unrelated to their degrees. In Germany 13% of all PhD graduates end up in lowly occupations. In the Netherlands the proportion is 21%.

Right, but the OECD study doesn’t show how many people without a PhD are on temporary contracts in Slovakia five years after receiving their degrees, be it bachelor or master’s.

A major thing the article fails to understand is that most PhD students pursue an academic career for two reasons: because it’s their passion, and because they don’t seem to be able/willing to do anything else. Take a philosophy graduate for example, with a master’s thesis on German, late 18th century idealism. This person has two choices: either he goes for a lowly occupation, as the OECD study puts it, or enroll in a PhD program. Statistics suggests that our poor philosopher might still end up working for the man, somewhere in a call center selling insurance to people who don’t want to buy it, but going for a PhD is still better, because he can have 3-4 years of joyful academic life and then try his luck getting a tenure track job after a couple of years. Even if he fails, at least he tried.

PhD students/graduates are usually lousy at finding jobs outside the universities not because they have a PhD degree, but because they’re different. Normal people don’t study philosophy, and if they’re into computer science, they don’t care whether P≠NP — they just learn Java, Objective-C, Python or whatever else they find useful for becoming a successful software engineer.

And then finally, there’s one last thing everyone seems not to understand: once you finish your PhD, get done with the damn post-doc contract, and become a tenure-track researcher, you’re in the best job there is. You’re doing what you love, you have most of the time a flexible schedule, you supervise master’s and/or PhD students, you go to conferences all over the world. You write papers others comment on, and at some point you might even write a book (or co-author one). How amazingly cool is that? Oh you’re saying I’m a dreamer, and that simply never happens? Well what about those thousands of internet start-up companies? They waste their time as well, trying to become another Facebook or another Google. Yet they still do it, because it’s their dream to pursue.

And so is academic career ours.

Discussion on HackerNews.

## Continuous list enumeration throughout the document with LaTeX

Karolina asked me today to create a macro for having a continuous list enumeration throughout the whole document, i.e.

This is the first list:

1. Item;
2. Another item;

And here goes the second list:

3. Third item;
4. And yet another item.

You can obtain an effect like that by using LaTeX counters and a custom definition of your own enumerate environment. First, we need to \usepackage{enumerate}, and then define the following counter and an environment in the preamble:

\newcounter{enumi_saved}
\newenvironment{myenumerate}
{ \begin{enumerate}\setcounter{enumi}{\value{enumi_saved}}}
{\setcounter{enumi_saved}{\value{enumi}}\end{enumerate}}

After that, you can use myenumerate and you’ll have a continuous enumeration in the whole document.

Oh and some credits: I wouldn’t come up with a solution if I haven’t read this post, and this website. Huge thanks to the authors for their tips!

update: There’s a much simpler solution, thanks Jakub.

Here’s a pro-tip on enabling auto-fill-mode for all org-mode files that I couldn’t find anywhere online. Add this to your $HOME/.emacs file: (add-hook 'org-mode-hook 'turn-on-auto-fill) And auto-fill will be enabled anytime you’re editing an org-file. ## Emacs as the Ultimate LaTeX Editor Everyone knows, that GNU Emacs is THE Best Programmer’s Editor. Not everyone knows, though, that when you combine it with AUCTeX macros, it also becomes THE Best Editor for LaTeX. The biggest problem with Emacs is that it’s not a particularly intuitive piece of software, to say the least, hence many users flee after their first encounter with it. Emacs has its complicated keyboard shortcuts, enormous documentation and config files written in a Lisp dialect (called Emacs lisp), so at first it might seem very unpleasant using it. However, once tamed, it becomes your best friend. I’d like to present some tips that customize Emacs making it a perfect and very sophisticated editor for LaTeX. Most of these ideas are taken from various config files, howtos and other resources found on the web. Some of them are mine, but I can no longer tell which. First things first: you need to get Emacs and AUCTeX, and get it running. Every major linux distro comes with both Emacs and AUCTeX available via package systems. In Ubuntu, you just type sudo apt-get install emacs23 auctex and you’re laughing. Emacs is also available for Windows, and AUCTeX website has instructions on how to set it up with Windows systems. Mac users have a choice of setting up either Carbon Emacs (a version closer to original GNU Emacs) or Aquamacs (an Emacs variant supporting tabs and other nice tweaks; preferred Emacs package by all Mac users I know, Karolina included). Full comparison of Mac Emacs variants is available here, so you can make your own choice. Both Carbon Emacs and Aquamacs come with AUCTeX bundled, so there’s no need to download additional packages. After running Emacs and loading a TeX file (C-x C-f file_name.tex), AUCTeX should load itself automatically. If it doesn’t happen, you can invoke it with M-x tex-mode, or you can put the following into your $HOME/.emacs file:

(setq TeX-auto-save t)
(setq TeX-parse-self t)
(setq TeX-save-query nil)
;(setq TeX-PDF-mode t)

(all the code snippets from this post are available as a Github Gist)

The options above will make sure, that AUCTeX macros are loaded every time a TeX file is opened. The last option, ;(setq TeX-PDF-mode t), is commented (all lines beginning with ; are a comment in Emacs Lisp), but you can uncomment it if you want to have PDFLaTeX mode enabled by default for all documents.

AUCTeX has a number of nice features, the two I use most often are:

• automatic formatting of a section: C-c C-q C-s;
• section preview: C-c C-p C-s; (see the screenshot on the right)

Preview function is very nice, because you can see the commands that are behind preview images, edit the code, apply preview again and see the results — no need to parse the whole file too often, and most importantly no need to switch to a PDF/PS viewer to see if your math formula/xypic tree is formatted correctly. Trust me, this saves a lot of time.

(update 27.12.2012: there’s another way of previewing LaTeX symbols inside an Emacs buffer, take a look here)

AUCTeX has many many more features, and you can always consult its documentation if you want to learn more. It’s a little bit overwhelming, but learning it is a very good investment, especially if you work with TeX a lot. But there are more packages that provide features which make your life easier.

Flymake is one of those packages. It enables Emacs to check the syntax of your TeX file on-the-fly. To turn it on, put the following code in your $HOME/.emacs: (require 'flymake) (defun flymake-get-tex-args (file-name) (list "pdflatex" (list "-file-line-error" "-draftmode" "-interaction=nonstopmode" file-name))) (add-hook 'LaTeX-mode-hook 'flymake-mode) Beware, though — flymake consumes quite a lot of CPU power, especially when used with large files (and paradoxically large files make it most useful). On the other hand, spell-checking while you type isn’t so cpu consuming, and you can turn it on with: (setq ispell-program-name "aspell") ; could be ispell as well, depending on your preferences (setq ispell-dictionary "english") ; this can obviously be set to any language your spell-checking program supports (add-hook 'LaTeX-mode-hook 'flyspell-mode) (add-hook 'LaTeX-mode-hook 'flyspell-buffer) Another nice package is the Outline Mode. It allows the user to hide some parts of the text file, which makes working with large files much easier. To enable it, put the following in $HOME/.emacs:

(defun turn-on-outline-minor-mode ()
(outline-minor-mode 1))

(setq outline-minor-mode-prefix "\C-c \C-o") ; Or something else

Now you can fold sections, subsections, chapters, or the whole document. To hide all the contents of your current section, use C-c C-o C-l. You can apply it to a chapter, subsection, etc. You can also move to a next unit of your document with C-c C-o C-n, or to a previous one with C-c C-o C-p. If you’re lost and want to see the whole document again, use C-c C-o C-a.

Folding and unfolding parts of the text might be confusing, though, but there’s another way to navigate through a big TeX file, and you can use Reftex mode for it. Reftex is a mode that helps with managing references (full documentation), but it can also be used to create a table of contents for a TeX file and to navigate using it. Here is my configuration for Reftex from my .emacs file:

(require 'tex-site)
(autoload 'reftex-mode "reftex" "RefTeX Minor Mode" t)
(autoload 'turn-on-reftex "reftex" "RefTeX Minor Mode" nil)
(autoload 'reftex-citation "reftex-cite" "Make citation" nil)
(autoload 'reftex-index-phrase-mode "reftex-index" "Phrase Mode" t)
(add-hook 'latex-mode-hook 'turn-on-reftex) ; with Emacs latex mode

(setq LaTeX-eqnarray-label "eq"
LaTeX-equation-label "eq"
LaTeX-figure-label "fig"
LaTeX-table-label "tab"
LaTeX-myChapter-label "chap"
TeX-auto-save t
TeX-newline-function 'reindent-then-newline-and-indent
TeX-parse-self t
TeX-style-path
'("style/" "auto/"
"/usr/share/emacs21/site-lisp/auctex/style/"
"/var/lib/auctex/emacs21/"
"/usr/local/share/emacs/site-lisp/auctex/style/")
LaTeX-section-hook
LaTeX-section-title
LaTeX-section-toc
LaTeX-section-section
LaTeX-section-label))

C-c =

All right, enough. If I mention any more packages, I guess it will scare off those who aren’t already scared. I know that Emacs is a bit peculiar with its complicated keyboard shortcuts, enormous documentation and thousands of modes. It’s not easy to learn, but definitely worth it. I remember that switching from Vim to Emacs for LaTeX editing wasn’t easy, but I never regretted that, and I hope whoever’s going to switch under the influence of this post will not regret it either.

## Norway in the eyes of a foreigner

After a long period of searching for a PhD scholarship I finally got a great offer from Bergen University College, and in the 2nd half of March I’ve joined the staff of Department of Computer Engineering as a member of DISTECH research group. This means a lot has changed in my life, because apart from changing a job/school I’ve also moved to another country. This country happens to be Norway and I have some thoughts about it I’d like to share.

Continue reading “Norway in the eyes of a foreigner”

## On the subjective hi-fi quality

Every now and then different people ask me about an opinion on buying hi-fi components. Be it headphones for their portable mp3 players, amplifiers or mini-systems, I’m a local authority (a proud one, I must add). Perhaps it’s because I’m a nerd obsessed with sound quality, or perhaps I’m judging people by their hi-fi systems, anyways I thought I’d share a few general advices for everyone.

First of all, let me remind everyone one more time, that buying hi-fi is by no means similar to buying computer hardware. There seldom happens a situation, when one can compare e.g. two amplifiers and say that the former is better than the latter in every aspect. Bad components happen, very bad happen as well, but the majority of hi-fi produced nowadays is at least good. Some of them are very good, and few are exceptionally fantastic, but those devices that occupy the last two categories are amongst most controversial, since not everybody likes the same sound.

Continue reading “On the subjective hi-fi quality”

## How I stopped being a desktop linux enthusiast

It’s actually about “how I’m stopping to be a desktop linux enthusiast”, because I’m still using linux on my desktop/laptop, and I still think it’s a much better solution than any Windows OS. It’s just that I’ve been using various linux distributions for many many years (since 1998 I guess) on every computer I’ve owned and thought it is a nearly flawless system. It’s not, and in fact it’s getting on my nerves.

It’s all about hardware, you know. I’ve never had any problems with a desktop computer running linux, but on all the laptops I’ve owned (all two of them), there’s always been some issues. When I was a teenager in high school, I could spend months recompiling the kernel, optimizing, patching, searching for solutions. But I’m an old man now, and I get really mad when something simply doesn’t work.

Continue reading “How I stopped being a desktop linux enthusiast”