Makai's Blog

My New Blog

Mon, 09 Jan 2012 18:59:01 -0500

I’m blogging over at http://www.mattmakai.com/ now. Tumblr’s been great over the past two years but I wanted more flexibility to revamp my web presence. My latest posts since January 1, 2012 are all over on my new site.

Link: Matt Makai’s Blog

Django 1.4 Alpha Release 1

Fri, 23 Dec 2011 13:00:25 -0500

At last, a version of Django that isn’t a maintenance release is out, albeit in alpha form (not for production use):

https://www.djangoproject.com/weblog/2011/dec/22/14-alpha-1/

Building and Testing with Gradle

Thu, 15 Dec 2011 10:07:49 -0500

I’m currently researching build tools. I need a build and configure tool for a iOS/Android/BlackBerry mobile app with a single set of core components but many configurations for different app deployments. I could hack something together with Python or Bash shell scripts, but there’s a reason why build tools exist. Options:

Ant/Ivy - doable, but loads of XML to write
Maven - my project structure does not lend itself to Maven’s rigid conventions
Gradle - I’ve never used it before, so let’s take a look

Building and Testing with Gradle by Tim Berglund and Matthew McCullough is an O'Reilly book was the logical pick. I saw Matt speak on Hadoop & Git at No Fluff Just Stuff last year and really enjoyed his clear, concise explanations. This book is also clear, concise, and only took a few hours to read and work through the examples.

My notes for the book are on my programming notes Github repository. The notes won’t make as much sense without reading the book, so I suggest picking up the eBook copy over at O'Reilly.

Over the next couple of days I’ll be working through producing a Gradle build for the mobile app I’m working on for Excella. I’ll post my full impressions of Gradle after I’ve had more time with the tool.

Structuring a Combined Android & BlackBerry PhoneGap Project

Thu, 08 Dec 2011 11:04:00 -0500

Android and BlackBerry expect two different folder locations for resources. Android has its assets/www folder while BlackBerry expects just a www folder under the project root directory. Since the BlackBerry .cod file is opaque after compilation, it makes it difficult to understand how resources are structured in the file.

I found that putting the BlackBerry config.xml file under assets/www and referencing my HTML file within the assets/www folder worked fine as long as there is a www folder in the root of the project which contains plugins.xml, the ext folder with the phonegap.1.2.0.jar file, and a resources directory with my icons and splash screen image.

Make sure to modify the BlackBerry build.xml file to reference the config.xml file in the assets/www folder and to include both the assets/www folder as well as the www under the project’s root directory.

With this folder set up, I was able to successfully deploy to both Android and BlackBerry without duplicating any files within the project structure.

Once I integrate iOS into the project structure I’ll post the code on Github.

JQuery Mobile 1.0, PhoneGap 1.2, and BlackBerry Simulator 9930

Wed, 07 Dec 2011 12:01:24 -0500

I spent a couple of hours yesterday evening trying to figure out why I only got a blank white screen after the app splash screen on the BlackBerry 9930 with a JQM 1.0 and PhoneGap 1.2 app that worked fine on the 9550 simulator.

Apparently this problem has been duplicated and the “recommended” fix is to use JQM Alpha 4 (not an option for me in this case). See this post on Google Groups.

I’ve opened an outstanding Github issue ticket for the problem and hopefully can extract the code for analysis.

Dear BlackBerry

Wed, 07 Dec 2011 11:23:33 -0500

Dear BlackBerry,

I’m going out of my way to develop a cross-platform app that will work on your devices. Don’t inconvenience me by making me download some “Akamai Net Session” software which I have no idea what it does before I can even download your simulator or SDK files.

Thanks,

Matt

Upgrading from PhoneGap 1.1 to PhoneGap 1.2 for Android Applications

Tue, 06 Dec 2011 13:16:26 -0500

I upgraded from PhoneGap (Apache Callback) 1.1 to version 1.2 today. Unfortunately, I encountered the following cryptic stacktrace:

ERROR/AndroidRuntime(9469): FATAL EXCEPTION: Thread-9

java.lang.RuntimeException: Can’t create handler inside thread that has not called Looper.prepare()

at android.os.Handler.(Handler.java:121)

at android.webkit.WebView$PrivateHandler.(WebView.java:7341)

at android.webkit.WebView.(WebView.java:416)

at android.webkit.WebView.(WebView.java:967)

at android.webkit.WebView.(WebView.java:957)

at android.webkit.WebView.(WebView.java:948)

at com.phonegap.DroidGap.init(DroidGap.java:268)

at com.phonegap.DroidGap.loadUrlIntoView(DroidGap.java:381)

at com.phonegap.DroidGap.access$300(DroidGap.java:159)

at com.phonegap.DroidGap$3.run(DroidGap.java:537)

at java.lang.Thread.run(Thread.java:1102)

The same stacktrace is found under issue #23 for PhoneGap.

Unfortunately PhoneGap 1.2 isn’t patched yet to accomodate the issue. So there’s 2 options if you hit this snag:

Disable the splash screen on Android
Download the latest nightly PhoneGap build on Github until PhoneGap 1.3 is released

Hopefully this issue will be resolved soon with a new PhoneGap release (maybe a 1.2.1 release)?

You've Got 5-10 Years

Thu, 01 Dec 2011 17:39:00 -0500

Recent college grads and young professionals, listen up: you’ve got 5-10 years. The labor market has been changing for a couple of decades and will continue in its trajectory. Today’s reality is that large companies are willing to pay you a decent wage for your first 5-10 years worth of work. After that, the gig is up.

Depending on your industry, after your first 5-10 years, you need to prove you’re worth real money. You can do that in one of two ways, depending on your personal strengths and weaknesses (be honest with yourself about them). The two choices are:

Start your own firm
Join an existing small firm where you can make a dramatic direct impact on the growth of the organization

There will be no other reliable options. There will always be other options, but they won’t be reliable. They are mirages held out by large companies to trick you into continuing to work for them until they lay you off. For example, you could try to get into mid-management and “climb the ladder.” Chances are high you will be laid off in that position long before you ever reach the executive ranks. There’s simply not enough “executive” positions to go around.

So knowing you have 5-10 years, you need to prepare today for that inevitable future. Whether you work for a non-profit, a law firm, a tech firm, or even in government, you need to figure out how you can successfully start your own firm or join an existing firm and be directly responsible for its growth. That’s the reality for our generation. If we embrace it, we can make it work for us.

The Python Ecosystem - Great Read

Tue, 29 Nov 2011 13:00:26 -0500

I came across this blog post on the Python Ecosystem while reading Hacker News yesterday. What a fantastic post. Highly recommended reading for aspiring Python developers.

Link: Python Ecosystem

A Brief History of Django Revisions

Fri, 18 Nov 2011 18:27:06 -0500

To understand Django, it helps to know its origins and how the framework has evolved. Django’s developers have added many features since the framework’s 1.0 release back in September 2008. Some of the major additions include aggregation support in the ORM, multi-database support, CSRF protection, a messaging framework, and many improvements to the models framework. This post outlines the major framework changes Django has gone through from 1.0 through the current stable 1.3 release. The intention for 1.x releases is that only minor code changes are necessary to transition Django projects from one version to another.

Django 1.0

(1.0 SVN Revision 8961, 1.0.4 SVN Revision 11613) [1]

Django 1.0 was released September 3, 2008 after a three year public incubation period and a total of five years of development [2]. Release 1.0 included features that are still core to the framework today, including the Model-Template-View (MTV) architecture, Object-Relational Mapper (ORM) models, explicit URL resolution with regular expression support, and a lightweight template system.

Django 1.1

(1.1 SVN Revision 11366, 1.1.4 SVN Revision 15477)

Django 1.1 was released Jul 29, 2009, just shy of 11 months after the official 1.0 release [3]. Version 1.1 included the following new features:

Aggregate query support in the built-in object relational mapper
Improvements to models
Better support for unit testing through client object’s support functions
URL namespaces

Django 1.2

(1.2 SVN Revision 13285, 1.2.5 SVN Revision 15476)

Django 1.2 was released May 17, 2010, approximately 10 months after the 1.1 release [4]. Major features added to Django in this release:

Mandatory Cross Site Request Forgery protection for POSTs
Support for more than one database in a single Django project
Model validation based on the existing Forms validation mechanism
User messages support through sessions and cookies
Configurable email backends

Django 1.3

(1.3 SVN Revision 15906, 1.3.1 SVN Revision 16771)

Django 1.3 was released on March 23, 2011 [5]. New features in Django 1.3 included:

Class-based views
Support for Python’s standard logging mechanisms
A new contrib app for serving static files

Django 1.4 and Beyond

There is currently no release date set for Django 1.4 although work continues in the public development branch. Django 1.4 will drop support for Python 2.4. The motivation behind the change is to use more context managers, a creation from Python 2.5, and make the internal Django code better. I wrote a post on Django 1.4 and how one of the Django core committers, Alex Gaynor, sees Django 1.4.

[1] Django SVN Revision 8961

[2] Django 1.0 Release Announcement

[3] Django 1.1 Release Announcement

[4] Django 1.2 Release Announcement

[5] Django 1.3 Release Announcement

Hello JQuery Mobile 1.0!

Thu, 17 Nov 2011 11:55:55 -0500

JQuery Mobile 1.0 has been released! A big part of the release is the maturity of the project and speed up in page rendering time (a big previous complaint especially when creating mobile native apps wrapped with PhoneGap).

A note of caution: JQuery Mobile 1.0 is only compatible with JQuery 1.6.4. JQuery 1.7 will be supported by JQuery Mobile 1.1.

Link: JQuery Mobile 1.0 Release Announcement

5 Great Django Deployment Links

Tue, 15 Nov 2011 15:39:54 -0500

I’m currently working on moving from my traditional Apache/mod_wsgi set up on Ubuntu to the new Django-serving community favorite, Gunicorn/Nginx.

I found the following links very beneficial for getting an initial set up going locally then moving over my production servers to the new configuration:

Run Django apps using Gunicorn and nginx (Easy set up)
Lessons Learned From The Dash: Easy Django Deployment (Another easy set up post)
Deploying Django (more detailed post on Django deployments and the stages heavily trafficked sites go through)
Preferred Django Stacks (Hacker News comments on what tools to use for a preferred stack)
How Yipit Deploys Django (this was really helpful for figuring out how Chef fits into Django deployment and it gave me another excuse to spend some time learning Ruby even though most of my work is done in Django)

Python Weekly - A Great Python/Django Resource

Thu, 10 Nov 2011 14:11:08 -0500

Python Weekly has provided me a lot of value over the past couple of weeks. I originally found out about the newsletter on Hacker News. I thought, “I’ll try one newsletter then unsubscribe if it’s not worth my time.”

Boy have I been pleasantly surprised. There are loads of great articles on Django deployments, best practices for settings.py configurations, interesting pip packages, and tips on Python programming best practices.

Thanks to the curator for putting together what has quickly become a must-read for Python developers.

You can check out an example newsletter and sign up at http://www.pythonweekly.com/.

My Advice to Computer Science Majors

Wed, 09 Nov 2011 11:16:30 -0500

My primary piece of advice to college students who are computer science majors is this: double major.

Computer science is great for understanding how computers work, programming, and learning the theory of computation. But where it really matters is how you apply those principles to real world problems that exist outside the computer science field.

If you double major, you’ll be exposed to a different discipline and begin to understand its problems. Hopefully down the road you can use your computer science knowledge to create solutions to those problems and produce real value in that field.

That’s my 2 cents for college computer science majors coming from someone who’s far enough outside of school to have some perspective on how you can produce value.

Accessing a Django Server on a VirtualBox Ubuntu Instance

Tue, 08 Nov 2011 15:18:00 -0500

I do the majority of my development work on virtualized Ubuntu instances to closely mimic my production deployment environment. Today I needed to access a Django server running on the VirtualBox instance from my host operating system (Windows 7).

I was simply using the built-in Django server (manage.py runserver) running on a high-level port instead of deploying to Apache or gunicorn. To do a pass through with this set up, use the following 3 steps:

Change the VirtualBox network adapter (Devices -> Network Adapter -> Adapter 1) to “Bridged Adapter” instead of NAT.
Inside the virtualized OS, run ifconfig -a to see the new inet addr (mine happened to be http://10.38.1.119.
Use the python manage.py runserver 10.38.1.119:8000 command (with your new IP address and the port above 1024 you want to run on) to run the Django server and allow external access

Now you should be able to access the Django server from your host OS through the browser at 10.38.1.119:8000 (again, replace with your specific IP and port number).

References:

[1] How to connect from Windows 7 to localhost on Ubuntu VirtualBox

[2] VirtualBox accessing ubuntu localhost thread

Urban Airship Android C2DM Push Notifications in the Python API

Mon, 07 Nov 2011 18:35:00 -0500

I needed push notification support for the Android C2DM platform for a Django project, but Urban Airship’s Python libraries only supported iOS push notifications.

So I forked the code on Github, modified it to incorporate support for C2DM APIDs. There’s an outstanding pull request (just issued) so hopefully it gets integrated back into Urban Airship’s official original master branch.

Thanks to Excella Consulting for allowing me to contribute this code back to the community!

MongoDB's Path to Maturity

Sun, 06 Nov 2011 08:42:05 -0500

There’s been a spat of links on Hacker News lately about the failings of MongoDB and 10gen (see links at the end). I see this as a very good thing, not because I want NoSQL in general and MongoDB in particular to fail, but because it is a sign of maturation. Developers are doing really interesting work with MongoDB and they are hitting the limits of the technology. There’s criticism of 10gen’s working process and concern over implementation choices.

If these concerns are addressed, MongoDB will be a much better, more mature product in the long run. We can only hope that CouchDB, Riak, and other document-oriented data stores receive the same amount of attention and feedback to address their unique sets of issues.

[1] Failing with MongoDB

[2] Don’t Use MongoDB

[3] We’re Back! …so long MongoDB

Flow Junkie?

Fri, 04 Nov 2011 19:18:31 -0400

I recently realized I’m constantly looking for a fix. Not from an external drug or chemical substance, but from flow. I get flow most commonly from programming, although I’ve felt it before while writing and working out.

It’s scary though because I am constantly hungry for flow. If I haven’t had it in awhile I go looking for it. I browse Hacker News and Reddit Programming looking for new languages and libraries to learn. Recently I picked up Stripe and it provided a fix for awhile, just like Clojure, Hadoop, and other tools and languages before them.

But on some level I feel like an addict. Wikipedia describes addiction as

… a continued involvement with a substance or activity despite the negative consequences associated with it.

Does the lack of (obvious) negative consequences make what feels like an addiction okay? Is the fact that I am constantly learning to try to get into flow make it alright since it makes me better at my software development job? On the surface these seem like good things to do, but maybe there’s something out of balance when you’re constantly looking for the fix.

What Happened to CouchDB?

Tue, 01 Nov 2011 16:20:44 -0400

What Happened to CouchDB?:

There’s a great discussion going on over at Hacker News about people’s opinions on what happened to CouchDB’s popularity as compared to MongoDB (and other NoSQL data stores).

My guess is that MongoDB took off lately as 10gen really gained traction with their outreach to developers while CouchDB is still fragmented despite the backing of Cloudant and Couchbase. I also found MongoDB easier to get started with than CouchDB. It is possible developers who recently learned about NoSQL considered MongoDB to be a better starting point to learn than CouchDB.

Also, here’s my introduction to MongoDB. Here’s my installation guide to CouchDB on Ubuntu (introduction to functionality coming soon).

Link: What Happened to CouchDB’s Popularity?

Great Post on MongoDB versus CouchDB

Sat, 29 Oct 2011 10:00:06 -0400

Great Post on MongoDB versus CouchDB:

I found this blog post really insightful for understanding the differences between MongoDB and CouchDB. The key takeaways for me were in understanding the difference between the way querying works (views in CouchDB versus find queries in MongoDB) and availability versus replication (continuous availability during network partitions in CouchDB versus one master plus replication in MongoDB). This post is worth reading in its entirety.

Link: A MongoDB Guy Learns CouchDB