Skip to main content

Codemotion Milan 2016: thoughts

I have never written a review on a conference and this isn't one: this is a brain dump (hence the lack of form and structure) that I quite simply needed to get out here. It might be incomplete, biased or what else: if there is anything that I should know then let me know in the comments. If you think I'm wrong then let me know that too, but please elaborate :-).

Last week I was, for the first time, at Codemotion in Milan. A first time doubly so: I had never been to a generalist conference before. Being I a generalist person I appreciated the format, even though I found some of the technical talks too light on actual details.

The talks that I liked the most were those of the inspirational track. I went to these two among others and I heartly recommend that you watch them (heck, have all your team watch them!). Maybe because I'm old and I have recently realized that people matter more than tools or technologies?
Overall I would rate the conference an 8 out of 10 just for those two.

Codemotion is a BIG conference, I think there were around 2000 attendees so rooms get crowded quickly, especially for keynotes or popular talks. Sometimes you might not even make into the room if you're just a minute late because, you know, you might want to talk someone or the speaker.

Food pretty much sucked in a big way. Coffee was not great and my suggestion is that they do without the human pouring it in the small plastic espresso cup next time.
Only nice thing was the fruit salad in the afternoon. Other than that, I pretty much recommend you consider bringing your own food.

Another thing that I did not like was the VIP room for speakers. Seriously? This is a conference and at conferences you meet people, not split them in two groups. On this theme a big shoutout to the awesome lastminute.com team that went to great lengths to answer all my technical questions at their booth. Tip of the hat, boys!

There was a small panel dedicated to job offers, but it was not exciting at all, to the point that it was discussed (or mocked, your call) on reddit.

Things I wish I'd asked

Perhaps I'll get a reply here :-)

To Alaina Percival: any advice for (worried) fathers that wish their daughter played with Legos (and pursued a career in Engineering) rather than Barbies?

To Leo: in his talk he mentioned a slide showing a declining rate of innovation since the 1950s. What do you think is the role of patents in this decline.

To Sven Peters: I know what's culture! (raised hand) It's what's left after you forget all the rules.

Thanks for reading.

Comments

Popular posts from this blog

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive. Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

How to automatically import a ZFS pool built on top of iSCSI devices with systemd

When using ZFS on top of iSCSI devices one needs to deal with the fact that iSCSI devices usually appear late in the boot process. ZFS on the other hand is loaded early and the iSCSI devices are not present at the time ZFS scans available devices for pools to import. This means that not all ZFS pools might be imported after the system has completed boot, even if the underlying devices are present and functional. A quick and dirty solution would be to run  zpool import <poolname> after boot, either manually or from cron. A better, more elegant solution is instead to hook into systemd events and trigger zpool import as soon as the devices are created.