diff --git a/_posts/2015-07-05-open-source-licenses.md b/_posts/2015-07-05-open-source-licenses.md
index 7433482..97e99c5 100644
--- a/_posts/2015-07-05-open-source-licenses.md
+++ b/_posts/2015-07-05-open-source-licenses.md
@@ -10,7 +10,7 @@ More and more mobile app developers are embracing the idea of [open source by de
 
 As programmers, we tend to wrap up a lot of ego in our code. Taking something you've written and putting it out in the world for others to do with what they like is a terrifying proposition; figuring out what rights you do and do not want to give others can be a very sensitive subject.
 
-Let's look at some of the considerations you might want to take into account while figuring out what open source license to release your iOS app under.
+I recently open-sourced [Cortado](http://blog.lazerwalker.com/2015/06/25/location-as-intent-introducing-cortado.html), my caffeine-tracking app, and in the past I've worked on another open-source personal tracking app called [Theseus](https://github.com/lazerwalker/theseus). Even as someone who was already moderately familiar with open-source licenses, I found myself having to do a fair bit of research to figure out what my options were for releasing a full-on consumer-facing iOS app. I figured I'd share some of what I learned with you; let's take a look at some of the considerations to take into account while deciding what open source license to release your iOS app under.
 
 **Keep in mind**: I'm not a lawyer, and this does not constitute legal advice. If you're debating licensing terms for your app and have the means to do so, consider consulting an actual lawyer.