This year’s PyCon Sweden, held on the 12-13th of May at Hilton Slussen in Stockholm, looks to be a spectacular follow-up to last years success.
I’m immensely happy that we got two great keynotes - Kate Heddleston and Ian Ozsvald are both amazing speakers - and I’m delighted that we got even more proposals for talks than last year, even though it did increase the amount of work to select the cream of the crop.
Since PyCon Sweden was a success last year, we’re doing it again this year, only slightly bigger, hopefully even better! We’ll move in to a prime venue at Hilton Slussen on the waterfront in central Stockholm, and keep aiming for the fantastic Swedish spring weather we had last year, with the conference running on the 12-13th of May.
We are accepting proposals until the 16th of February - go ahead and submit your proposal today!
That’s right, PyCon Sweden 2014 will take place in Stockholm on May 20-21, and you should be there!
Even better, you should propose a talk on anything related to Python, and/or see if your company would not like to sponsor the event - this is a chance to reach 250 developers over two days you don’t want to miss.
This event will be the first national Python conference in Sweden - a country that has hosted two Europython and has vibrant user groups and meetups, but for some reason has not been able to pull together a national PyCon until now.
Next year, in March, I will be at PyCon. It will be the third time I attend PyCon - ever since I attended my first, not going has not really been an option.
There are lots of good things about PyCon - meeting interesting people, seeing San Francisco, beating off recruiters with a stick, hanging out in the hotel bar and chill in the evenings - but the best part is that the talks are so many, and so good.
I had a blast at Europython - I made new friends, went to a couple of talks that gave me some ideas for the future, and my own talks seemed to go down well.
All in all, the EP2012 organization was great, the food was way beyond ‘normal’ conference fare, and the venue was good - although finding a place to sit down during lunch was hard.
I would have liked some kind of feedback mechanism in place for the talks - had I known there would be none I’d have arranged one for my own talks and especially the training session I held.
I believe that Python is important for software development. While there are more powerful languages (e.g. Lisp), faster languages (e.g. C), more used languages (e.g. Java), and weirder languages (e.g. Haskell), Python gets a lot of different things right, and right in a combination that no other language I know of has done so far.
It recognises that you’ll spend a lot more time reading code than writing it, and focuses on guiding developers to write readable code.
A few days ago I was asked by a collegaue what the point of properties in Python is. After all, writing properties is as much text as writing getters and setters, and they don’t really add any functionality except from not having to write ‘()’ on access.
On the surface, this argument holds as we can see by comparing a simple class implemented with getters and setters, and with properties.
All testing is not valuable. There. I said it.
If you take a look at the source of Blaag, you might notice a certain lack of tests. No unit test, no tests at all in fact. Does this mean I do not believe in unit tests, TDD and testing in general? No! If you take a look at hgapi, for example, I wrote almost all code using TDD since that was the only way to know I got it right.
After almost more than four hours of grueling work, my blogging platform codenamed “blaag” works.
I created blaag since I’ve been thinking about blogging, but didn’t like the blogging platforms I found, because they were made of bloat with a little functionality hidden deep within. I did, however, like the idea behind hgblog - especially that it’s based around generating the blog from rst using Mercurial hooks, allowing blogging from the comfort of Emacs.