I finally pushed Jaxen 1.1.2 out the door, and my resolution (singular) for 2008 is to finally finish XOM 1.2 as well. Then maybe, just maybe, I’ll have a little room to take on one more hobby project this year, but what should it be? They’re a few ideas I’m kicking around, and I’m wondering which would b the most interesting\/lucrative\/fun. Here are a few ideas:<\/p>\n
The screen on my Garmin handheld unit cracked two days after I got an unlocked Android phone to play with. Coincidence or fate? Some folks are already working on Android GPS apps. Maybe I could contribute to their efforts.<\/p>\n
In fact, far and away the major feature I use on my Garmin eTrex is simple measurement of how far I’ve walked, along with occasional downloads of paths. I wouldn’t have to reimplement the entire Garmin stack for the Android, just the one or two pieces I actually use.
\n<\/p>\n
Disadvantages: Would have to learn a new programming environment. High risk. Might fail.
\nAdvantages: Obvious market need. Would learn a new programming environment.<\/p>\n
Rather than taking 3×5 notebooks into the field, maybe I could just take my Android? Observations could be entered directly into the phone, tagged with GPS coordinates, summed and uploaded to eBird when done. The user interface design would be a challenge, but done right this could be really hot.<\/p>\n
Disadvantages: Would have to learn a new programming environment. Low risk. Almost certainly could be done.
\nAdvantages: Limited market need. Very useful personally (scratches an itch) but unclear if anyone else would use this. Would learn a new programming environment.<\/p>\n
Something I toyed with a year or two ago<\/a>: I’d like to reimplement the now defunct NYC Bird Report<\/a> on top of a portable, maintainable framework and then generalize it to other locations. Possibly it could be integrated with eBird.<\/p>\n This is not especially cutting edge, but I know there’s an audience. If I do it, I should probably use the technologies I already know: MySQL and PHP. <\/p>\n Medium risk, medium impact. Large contribution to birding community. Negligible contribution to software development community. Might require significant amounts of time.<\/p>\n Boring, but straight-forward, simple, and doable. Probably the easiest suggestion here. It would finally<\/em> add comments to these sites. In some ways it would make them easier to edit, but in other ways it would make them harder to maintain.<\/p>\n Disadvantages: Limited impact. Almost no effect beyond the two sites. Screw the easy way. Instead I could build my own bog system from scratch based on eXist or maybe DBXML. This is likely the largest project I could take on, and would take the longest, but might have the largest impact. Ultimate goal: world domination (or at least kicking WordPress’s ass.)<\/p>\n Disadvantages: High risk. Might flop. Large amounts of time required. Would likely delay updates on at least one site as work progressed in dogfood mode. Firefox is great, but there are some bugs that just don’t seem to be going anywhere. Why, oh why, can’t the page up and page down keys scroll the main window instead of the location bar? Why does Firefox 3.0 have no AppleScript support?<\/p>\n Disadvantages: Would have to learn a new language and programming environment. Requires committer’s approval.4. Convert Cafe au Lait and Cafe con Leche to WordPress<\/h3>\n
\nAdvantages: Low cost. Almost guaranteed to work. Might enable me to farm out more work on these sites to contributors.<\/p>\n5. Convert Cafe au Lait and Cafe con Leche to XQuery<\/h3>\n
\nAdvantages: High reward. Could be colossally important. Uses technology I already know pretty damn well. User interface design would be negligible. (That is, I could just copy what already works.) Could likely implement in small pieces, one feature at a time.<\/p>\n6. Fix Firefox<\/h3>\n
\nAdvantages: small, separable tasks; large impact when integrated across many users. Would learn a new programming language and environment.<\/p>\n7. Fix Ciphsafe<\/h3>\n