Archive for the ‘technology’ Category

django girls den haag 2016 welcome speech

March 5th, 2016

Given on March 5, 2016 at Django Girls Den Haag 2016 in Den Haag.

Welcome, everyone!

We are thrilled that you're all here. Some of you have come far to be here today with us and we really appreciate it. We have people from all over the Netherlands!

I also wish to thank our sponsors. Without the sponsors this event just wouldn't be possible. Thank you: Amazon, Elastic, KPMG and GingerPayments!


Today is all about learning. You're about to learn programming, which is a completely new skill for most of you. It's going to be exciting. And some of it will be difficult. Learning *is* about pushing your boundaries, and it takes effort to learn anything.

I know it will seem as though your coaches know everything. Later today you might be asking yourself: "how am I supposed to master all this? There is so much new information here!" You may feel overwhelmed. But I promise you that every programmer in this room, myself included, has been through that. It's completely normal, and you're on the right track. So don't feel bad about that!

I want you to make mistakes today. Making mistakes is a good thing - whenever you make a mistake you learn something.

And don't hesitate to ask questions. If you get an answer that you don't fully understand, keep asking! Don't settle for answers you don't understand.

Finally, don't work so hard that you forget to take a break and get to know the people around you!


I will now introduce the organizing team. Raise your hand when you hear your name.

So I'm Martin, you've been getting my emails. We also have Chris. Robbie. Alexandra. And Tom.

So we are the organizers and you might think this means we know what we're doing. But no. We're just a bunch of software developers. We've never tried to organize an event for 100 people before.

Speaking for myself I had many moments of self doubt. How are we going to find a space big enough to host the workshop? How are we going to find enough volunteers to be coaches? How are we going to find all of you?

We made a lot of mistakes. And we learned from them.

We did it together as a team. It took effort, but it was also a pleasure.


I hope all of you have met your coach by now. We have 26 coaches with us today. They are nice enough to spend their Saturday to make Django Girls possible, isn't that awesome? They've *also* come from all over the country.

Please raise your hand when you hear your name.

Could we have a round of applause for the coaches?


Django Girls is a global initiative. It all started two years ago at a technical conference in Berlin. It was a big international conference with people from all over Europe. Now you should know that IT conferences are very male dominated. Two of the participants of that conference, the founders of Django Girls - Ola and Ola, had a simple idea: what if we organize a workshop for beginners - and for women! So they organized the very first Django Girls in 2014.

Since then it has spread to 57 countries. There have been over 100 events already. This is the sixth one in the Netherlands.

More than 3,500 women have participated! Many have gone on to become coaches. And you remember that very first Django Girls workshop? 80% of the participants there have organized their own Django Girls events since then in their country.


Now for some practical information.

Today's workshop lasts from 9 to 5pm. You can find the schedule for today on the posters.

The bathrooms are right around the corner, out that door and to the right.

We have coffee, tea and snacks available now. We have a limited number of cups, so please try to reuse your cup!

We have lunch coming in later on. It will be served in the lobby.

We have a mystery event in the afternoon.

We're a bit unsure of the wifi capacity with so many people using it all at once. So try to be gentle with the wifi connection. In case of problems it's possible to do big parts of the tutorial offline. Your coaches also have a copy of all the files on usb sticks you need today so you don't have to download them.

Last but not least we have a code of conduct. The code of conduct is in place to ensure that everyone can feel safe at our event. You can find the full text on one of the posters. If you see anyone breaking the code of conduct, please talk to one the organizers!


what django girls is

February 24th, 2016

Given on Feb 23, 2016 at the Dutch Django Meetup in Amsterdam.

Today I want to tell you about a part of the Django community that you may not even know about.


This is how I think most of us see the Python community. A comfortable couch. Nice people. Right? Just a nice place to be.

It's easy to make an analogy with software. Almost every developer has had the experience of working on a codebase that they inherited from someone else. The dreaded *legacy project*. And it wasn't the most fun project to work on. Spaghetti code, no tests, no documentation, really hard to make changes without breaking something.

So after working on this day in and day out after a while you start to get a little sick of it. I start thinking to myself "I've had it with this code. It expend so much energy on this and I have so little to show for it. Jeez, give me a codebase that's in good shape for a change. One that is modular, and has clean code. With good test coverage. If I had that I could *really* make it fly!"

I want to submit to you that the Python community is that nice codebase. It's when your code is in good shape and is easy to work on, that it's a great starting point to make it even better. To take the next step.

I'm sure you've heard this expression before: Came for the language, stayed for the community. People come to Python for the language, or for the libraries, or for the frameworks (like Django). Right? Just because they need to get some work done. And then they realize: hey there are conferences, there are meetups, and there are great people to hang out with. So they stay with Python not necessarily because it's the best programming language in the world, but rather because the community is a great place to be. It makes them feel at home.

So I'm saying: let's take the next step. Let's make it even more welcoming, even more inclusive!


Let me tell you about what we do. Since you're programmers I will explain this as a program. Django Girls is a one day programming workshop for women. Our mission is to bring in women who are new to IT and get them hooked on programming. Now the workshop is the box you see in the middle.

Then as input we take non-programmers. Most people who attend Django Girls have never written a program before. During the workshop they build a blog, from scratch. So they come in, never written a program before, and they go home, they've built a blog. Amazing, right? They do this following a tutorial which is very beginner friendly, so it explains everything they need to know.

Also as input we take developers. These are the programming coaches. They don't have to be professional developers, just have enough experience with programming to help someone else through the tutorial.

As output, we get programmers. They are beginners, of course, but they are programmers. We've given them the first step on a path that could potentially lead them to this room. Some percentage of Django Girls participants land junior developer jobs a few months down the road. But not everyone wants to be a developer, and that's fine. Some people are academics, and they want to learn how to automate parts of their work. Some work in marketing, and work with developers and want to understand what their colleagues do. And some people are just curious about programming and want to try it. We encourage all different demographics.

And also output, we get the same developers, and you may think all they did was volunteer a day of their time and that's it. But they've just spent a whole day coaching people in programming. If you're already a mentor to people at your job, that's excellent! But if you're not, coach at Django Girls for a day and you get really good practice that will come in very useful in your career, believe me.


So Django Girls is coming to Den Haag Saturday next week. We're going to be on the top floor of this office building. If you're familiar with Den Haag it's right next to the station Hollands Spoor.

We received applications to participate from more than 100 women. We're also lucky enough to have found more than 30 coaches to help us.

Unfortunately we only have space to host 60 participants, so we had to turn down a lot of people.

But the level of interest has been really impressive. We have people coming from cities all over the country, like Groningen and Leuwwarden, Nijmegen and Deventer. We have people coming from Belgium, where Django Girls hasn't taken root yet.

And then there's the 5 of us, the organizers. A few of us went to a Django Girls event as coaches and we loved it. We decided we wanted to organize one of these ourselves, in our city. Now we're just a bunch of software developers, we've never organized an event like this before. But we somehow pulled it off.

If we can do it, you can do it. Think about it.


Now, Django Girls has been organized before in the Netherlands. There is a group of organizers in Groningen who are the pioneers in our country - and they're planning another even this year. It's also been organized in Amsterdam before. And then there's our event, which is the upcoming one.

But like I said there is a lot of interest from people out there for a workshop like this. I would love to see more cities on this list in the future. So you could organize one. And you can be a coach! Most organizers have trouble finding enough coaches, and if they had more coaches they could accept more participants!

Thank you!


You can find the slides on Slideshare.

why you should coach at django girls

February 22nd, 2016

Given on Dec 10, 2015 at PyLadies Amsterdam.

Dear PyLadies,

My name is Martin and I'm one of the organizers of Django Girls The Hague. Which will take place next year in the beginning of March.

Django Girls is a non-profit organization that aims to give women a really positive first experience with programming. I'm not going to explain why we think this is important, because I think if you're a member of PyLadies you already know that.

I will explain how we do it. We invite a room full of women to participate. We seat a group of 3 women around a table. And we give them a programming coach. What they will be doing is building a web application from scratch. Using a tutorial special made for Django Girls. Now, the programming coach is there to help them, to explain things, and to give moral support.

Now, the coaches are integral to the event. We as organizers can provide a nice room in a nice location, a good tutorial, and food etc, but the coach is the human factor.

We are currently trying to find these coaches. That's why I'm here today. I would really like to encourage you to sign up to be a coach.

I've been a coach at two Django Girls events in the past. And in fact tomorrow morning I'm flying to Italy to be a coach at Django Girls in Rome on Saturday. It's a really fun thing to do.

The people who come to Django Girls aren't the kind of people who say alright, so what is this programming thing all about? If it doesn't take more than 5 minutes I'm willing to give it a try and then I'll be on my way. These are people who decide to spend 8-9 hours learning something new, that they've never done before. I mean can you imagine? It takes little courage to do that. So they're really interested and motivated to learn programming. And as a coach you see programming happen for the first time, through their eyes. It's really exciting. It's a really fun way to spend a day.

In terms of what it takes to be a coach. I want to make this very clear: You don't have to an expert on Python or Django. I would recommend that you work through the tutorial that we use yourself. Ask yourself if you understand everything. Ask yourself if you think you can help someone complete it. If so then you can be a coach. Ultimately if you encounter a problem at the workshop we will have some more experienced coaches to help you.

So if you think this sounds awesome and you want to help us make this possible then sign up to be a coach. You can sign up on our website, just google for Django Girls and find our chapter for The Hague, Den Haag. We also have a twitter feed where you can follow our updates.

We would love to have you there! Thank you very much!!

two weeks of rust

January 10th, 2016

Disclaimer: I'm digging Rust. I lost my hunger for programming from doing too many sad commercial projects. And now it's back. You rock, Rust!

I spent about two weeks over the Christmas/New Year break hacking on emcache, a memcached clone in Rust. Why a memcached clone? Because it's a simple protocol that I understand and is not too much work to implement. It turns out I was in for a really fun time.


The build system and the package manager is one of the best parts of Rust. How often do you hear that about a language? In Python I try to avoid even having dependencies if I can, and only use the standard library. I don't want my users to have to deal with virtualenv and pip if they don't have to (especially if they're not pythonistas). In Rust you "cargo build". One step, all your dependencies are fetched, built, and your application with it. No special cases, no build scripts, no surprising behavior *whatsoever*. That's it. You "cargo test". And you "cargo build --release" which makes your program 2x faster (did I mention that llvm is pretty cool?)

Rust *feels* ergonomic. That's the best word I can think of. With every other statically compiled language I've ever used too much of my focus was being constantly diverted from what I was trying to accomplish to annoying little busy work the compiler kept bugging me about. For me Rust is the first statically typed language I enjoy using. Indeed, ergonomics is a feature in Rust - RFCs talk about it a lot. And that's important, since no matter how cool your ideas for language features are you want to make sure people can use them without having to jump through a lot of hoops.

Rust aims to be concise. Function is fn, public is pub, vector is vec, you can figure it out. You can never win a discussion about conciseness because something will always be too long for someone while being too short for someone else. Do you want u64 or do you want WholeNumberWithoutPlusOrMinusSignThatFitsIn64Bits? The point is Rust is concise and typeable, it doesn't require so much code that you need an IDE to help you type some of it.

Furthermore, it feels very composable. As in: the things you make seem to fit together well. That's a rare quality in languages, and almost never happens to me on a first project in a new language. The design of emcache is actually nicely decoupled, and it just got that way on the first try. All of the components are fully unit tested, even the transport that reads/writes bytes to/from a socket. All I had to do for that is implement a TestStream that implements the traits Read and Write (basically one method each) and swap it in for a TcpStream. How come? Because the components provided by the stdlib *do* compose that well.

But there is no object system! Well, structs and impls basically give you something close enough that you can do OO modeling anyway. It turns out you can even do a certain amount of dynamic dispatch with trait objects, but that's something I read up on after the fact. The one thing that is incredibly strict in Rust, though, is ownership, so when you design your objects (let's just call them them that, I don't know what else to call them) you need to decide right away whether an object that stores another object will own or borrow that object. If you borrow you need to use lifetimes and it gets a bit complicated.

Parallelism in emcache is achieved using threads and channels. Think one very fast storage and multiple slow transports. Channels are async, which is exactly what I want in this scenario. Like in Scala, when you send a value over a channel you don't actually "send" anything, it's one big shared memory space and you just transfer ownership of an immutable value in memory while invalidating the pointer on the "sending" side (which probably can be optimized away completely). In practice, channels require a little typedefing overhead so you can keep things clear, especially when you're sending channels over channels. Otherwise I tend to get lost in what goes where. (If you've done Erlang/OTP you know that whole dance of a tuple in a tuple in a tuple, like that Inception movie.) But this case stands out as atypical in a language where boilerplate is rarely needed.

Macros. I bet you expected these to be on the list. To be honest, I don't have strong feelings about Rust's macros. I don't think of them as a unit of design (Rust is not a lisp), that's what traits are for. Macros are more like an escape hatch for unpleasant situations. They are powerful and mostly nice, but they have some weird effects too in terms of module/crate visibility and how they make compiler error messages look (slightly more confusing I find).

The learning resources have become very good. The Rust book is very well written, but I found it a tough read at first. Start with Rust by example, it's great. Then do some hacking and come back to "the book", it makes total sense to me now.

No segfaults, no uninitialized memory, no coercion bugs, no data races, no null pointers, no header files, no makefiles, no autoconf, no cmake, no gdb. What if all the problems of c/c++ were fixed with one swing of a magic wand? The future is here, people.

Finally, Rust *feels* productive. In every statically compiled language I feel I would go way faster in Python. In Rust I'm not so sure. It's concise, it's typeable and it's composable. It doesn't force me to make irrelevant nit picky decisions that I will later have to spend tons of time refactoring to recover from. And productivity is a sure way to happiness.


The standard library is rather small, and you will need to go elsewhere even for certain pretty simple things like random numbers or a buffered stream. The good news is that Rust's crates ecosystem has already grown quite large and there seem to be crates for many of these things, some even being incubated to join the standard library later on.

While trying to be concise, Rust is still a bit wordy and syntax heavy with all the pointer types and explicit casts that you see in typical code. So it's not *that easy* to read, but I feel once you grasp the concepts it does begin to feel very logical. I sure wouldn't mind my tests looking a bit simpler - maybe it's just my lack of Rust foo still.

The borrow checker is tough, everyone's saying this. I keep running into cases where I need to load a value, do a check on it, and then make a decision to modify or not. Problem is the load requires a borrow, and then another borrow is used in the check, which is enough to break the rules. So far I haven't come across a case I absolutely couldn't work around with scopes and shuffling code around, but I wouldn't call it fun - nor is the resulting code very nice.

Closures are difficult. In your run-of-the-mill language I would say "put these lines in a closure, I'll run them later and don't worry your pretty little head about it". Not so in Rust because of move semantics and borrowing. I was trying to solve this problem: how do I wrap (in a minimally intrusive way) an arbitrary set of statements so that I can time their execution (in Python this would be a context manager)? This would be code that might mutate self, refers to local vars (which could be used again after the closure), returns a value and so on. It appears tricky to solve in the general case, still haven't cracked it.

*mut T is tricky. I was trying to build my own LRU map (before I knew there was a crate for it), and given Rust's lifetime rules you can't do circular references in normal safe Rust. One thing *has to* outlive another in Rust's lifetime model. So I started hacking together a linked list using *mut T (as you would) and I realized things weren't pointing to where I thought they were at all. I still don't know what happened.

The builder pattern. This is an ugly corner of Rust. Yeah, I get that things like varargs and keyword arguments have a runtime overhead. But the builder pattern, which is to say writing a completely separate struct just for the sake of constructing another struct, is pure boilerplate, it's so un-Rust. Maybe we can derive these someday?

Code coverage. There will probably be a native solution for this at some point. For now people use a workaround with kcov, which just didn't work at all on my code. Maybe it's because I'm on nightly? Fixed!


So there you have it. Rust is a fun language to use, and it feels like an incredibly well designed language. Language design is really hard, and sometimes you succeed.

django girls 2015 summary

December 16th, 2015

I've never been too far removed from Django Girls. I was present at EuroPython 2014 where the very first Django Girls workshop was held. But at the time I had no idea what that even was. It wasn't until a few months later that the story of Django Girls started reverberating through the Python web.

I decided to take the plunge in September and attend my first Django Girls in Groningen. It was a great experience and I knew right away that I wanted to do more of these. I kept checking the event calendar every few weeks and eventually I settled on Bordeaux in November and Rome in December.


Groningen: 60 participants, 20 coaches

Bordeaux: 27 participants, 10 coaches

Rome: 35 participants, 11 coaches

Our combined group of 40 coaches has taught programming for a day to 120 women! And globally Django Girls is nearing 3000 participants with multiple events happening pretty much every single weekend.

What about 2016?

The big news is that we are organizing our own event in Den Haag in March!

Beyond that I'm sure I will be present at other Django Girls events too - I just don't know which ones yet.