Skip to main content

Dublin GTUG

So last night I spoke at the Dublin Google Development Group, which is held in the Google Offices in Barrow Street. For all the times I've passed those offices, either by foot or train, I've never actually been in there and usually looked enviously upon their facilities (I believe they've now got a 25m pool, which for me would be, well, awesome). I was invited by Eoin Bailey (from Trinity), who up until last night (I believe), has been running the group and interestingly, the "head" of the group cannot be a Google employee. Apart from the slick, professional set-up there's also food and non-alcoholic drinks beforehand with a potential retirement to the Schoolhouse afterwards.

The facilities were obviously excellent, sweet theatre ("What's up Doc" was the name I believe) with excellent seating, screens etc as you'd expect. The group were seemed interested in my talk but I think I lost most folk when I began talking about sharding, possibly my fault :( Working the bank holiday as the only person in EMEA and having a crazy day on Tuesday, due to the effects of Hurricane Sandy on my NYC colleagues, meant that I turned up knackered and with essentially little prep done. Far from ideal and a big no-no for me usually but as the invite had been agreed a long time ago, plus it's always good to spread the word of "MongoDB" and challenge oneself (I think). I think one of the great challenges is to stand up and try to explain technical stuff that you think you know, the trick is not to do it tired but all the same, I definitely learnt a lot last night from standing up there. My slides can be found here (bear in mind, that many of these slides were actually cut from the deck that I presented, due to time constraints and the difficulty of deciding "what constitutes an introduction").

The presentation seemed to have gone done well, there were some questions (whilst the books, mugs and stickers SWAG went pretty fast) and people said nice things, though they could have been being just polite :)

The second talk of the night was by Chris Woods. I've previously chatted and worked a little with Chris on MongoDB so it was good to see a familiar face. Chris is a very clever guy, totally gets "MongoDB" and had a really interesting presentation with some funny war stories. His web app is called Voczie, can be visited here and in his words -

VocZie combines RSS feeds with Twitter to let you see and participate in the conversations which happen around the news stories we all read every day... 

Chris isactively looking for more traffic to his site so that he has to deal with "scaling out" and is very excited about "sharding" so I strongly encourage you to visit his site :) Chris has a short write-up here on the perils of standing up to talk in front of random strangers and his slide can be found here.

I really enjoyed my visit to the GTUG and I think it's easily one of the cooler and more technical user groups I've seen in Dublin. I went home knackered but it was good evening, meeting new folk and seeing Chris's cool use case.

I hope to come back as an attendee, if I'm allowed back in :)

Thanks to Eoin, Raphael and Jean (hopefully I haven't forgotten anyone) for their hospitality, Chris for talking eloquently about MongoDB and Gianfranco for his moral support!!!!
Labels:

Comments

  1. Anonymous1 November 2012 at 03:16

    Thanks heaps for doing this, Mark -- appreciate your work and your passion for the community, even when you are under as much pressure as this week! It sounds like a great event, and hopefully Chris Woods will present at a Dublin MongoDB User Group in the future

    ReplyDelete

Post a Comment

Popular posts from this blog

Being a Support Engineer @ 10gen - Part 1

There's a mis-conception around the role of a "Support Engineer".  As a clue, it's not what Urban Dictionary   says   - A person whose job is to answer calls from customers of a small- to large-sized company...... They are teathered to a their desk all day via phone headset........ phone jockeys usually hate their jobs.......they are are paid well enough..........until they completely burn out, and hate everyone.   and doesn't always involve this - Image Source: http://half-bakedbaker.blogspot.ie/2009/11/cannoli-and-broken-computer.html As you can see  here , there's lots of open roles in  10gen  and more specifically with 10gen, in  Dublin . I thought I'd write this quick blog to explain what Support Engineers actually do and why I joined 10gen as a "Support Engineer". I could be wrong but didn't Google come up with term " Site Reliability Engineer " to do away with the stigma associated with being a
Post a Comment
Read more

MongoDB Authori(s|z)ation

Introduction Having answered numerous questions on the new and old authori(s|z)ation within MongoDB, I thought I'd write a short blog post explaining how things work as there seems to be some confusion. What's New Prior to version 2.4 , there was a very basic sense of "Role Based Access Controls" (RBAC) within MongoDB as there were only two roles - read readWrite which is quite limited. For example, if the user has "readWrite", that user is essentially "root" and the user can add/remove users as well as inserting data into the database, i.e. there is no role segregation. Version 2.4 added in the following 3 core roles - userAdmin dbAdmin clusterAdmin with a notable extension such that there are now 4 roles that apply across all databases - readAnyDatabase readWriteAnyDatabase userAdminAnyDatabase dbAdminAnyDatabase This increased RBAC is a significant improvement from a security perspective in MongoDB. It is imp
Post a Comment
Read more

Start-Up Security

After many years in Security @ Riot Games and eventually putting the "s' out there, I recently decided to jump out of my comfort circle for a new challenge and joined a   start-up   (yes, I left a comfortable, stable job in a pandemic, lunacy lol). Now that I've been here almost 6 months, I wanted to share some findings because security at a start-up is significantly different.  When you join a start-up, there's going to be so much that you can do and it will be incredibly easy to "boil the ocean", and try to fix everything. At best, this guarantees failure for the Security team, at worst, alienation from the engineering and product teams. There are some obvious quick wins that a Security team can make without slowing down iteration and innovation speed, while also reducing risk: Auth  Partner with Engineering/IT/CTO such that there's alignment on Security owning all things "auth(n|z)".  As part of this ownership, you need to be prepared to resp
Post a Comment
Read more