Rails Rumble is Over, Back to Code

Rails Rumble is officially over, so I can get back to working on my FML app. Unsurprisingly, I wasn't able to complete it in the ten hours I had to work on it after work each night during the competition. I've given myself until the end of October to finish at least a decent MVP.

Here's where I am right now: https://secret-inlet-5715.herokuapp.com/

I'll keep chugging away and I'll check in from time to time. Soon I will have some posts about the SeaGL conference last weekend, as well as my talk! (It was a first talk, it was a first talk, it was a first talk... ;) ).

And So It Begins

I've finished zizzer-zoofing for the night and it's finally time to start coding for my Rails Rumble submission. My app is the scratch-my-own itch list-compiler/downloader app that I've been thinking about for over a year now. (Aptly enough, it's called Fix My List, or FML for shortsies :D.)

Enough gabbing, time to code. Wish me luck!

A Year Ago Today (Part II)

I suppose I could write 365 of these kind of posts, but I realized today that I've hit something of a milestone:

With the exception of that awful spot during Hell Season for retail workers, I've got a year full of contributions on GitHub. I have some patches here and there, but those are actually from working off the master branch on different projects (or when I crumpled up my paper by deleting repos and started over.)

I don't have much to say right now, but back to work. I'll post some links to my Zombie Floss app once it's live.

So How Was Your Day, Dear?

This whole transportation SNAFU (literally) woke up the Mama Bear. Look out! pic.twitter.com/jg7p1j8xjO
— jaimes (@EduPunkN00b) September 30, 2014

.@LakeWashSchools: That's why no one complains. We know that the drivers are blamed for structural issues they can't control.
— jaimes (@EduPunkN00b) September 30, 2014

.@LakeWashSchools my daughter wait for a 2nd bus once it was dispatched. I'm glad she didn't do that and don't want to see a GREAT driver ..
— jaimes (@EduPunkN00b) September 30, 2014

Just Ship It

Last week was a bit of a whirlwind. I slammed through most of my backlog in Skillcrush's Web Developer Blueprint course and published two (imperfect) sites:

The url for this site is about to be swiped for my Rails Rumble submission. I'm open to ideas for a better (more fitting) name for this brainstorming site. Also on the to-do list is to get set up with asset hosting on AWS so that the images uploaded along with the ideas will be saved! (Image storage on Heroku itself is strictly ephemeral!)

and...

This resume-splash page was for an assignment on Skillcrush. I've got two main to-dos for this site. First, optimize the image better so that the background isn't so slow to render. Second, it looks terrible on a mobile screen in portrait mode.

I need to figure out how to tell the css to drop into a different mode when in a really small screen.

I'd like to continue my streak and ship another page this week. Not sure what yet (likely a starter page for my SeaGL talk this month.) Finally, I'm throwing in my hat for Rails Rumble - registration starts on October 6th and I'm super stoked to be a part of it this year.

Oh, yeah, and I've got my "day" job at [company name retracted due to uber-restrictive social media policy].

It's going to be a great week!

Edited to add:

I completely forgot! I also (finally!) got around to signing up at exercism.io I've just started but it's so much fun! :D

What a Summer it Has Been

This is a difficult post to write. I started this summer excited by my new OPW internship and anxious to get started. It began with a lengthy project map

The following enhancements are needed to allow storing and rendering of time-based information in OpenHistoricalMap.

1. Enhance the iD and The_Rails_Port so that a javascript time/date slider can be added to control the time period that is of interest.

2. Enhance the ID and The_Rails_Port so that meta-data hooks are added to the code that allow for custom deployments of both software. The intent is to support their use as dedicated user interfaces to certain applications (such as medieval walking path editing) while still using a generic data source.

3. Modify the Mapnik tile renderer to handle Key:start_date and Key:end_date.

http://wiki.openstreetmap.org/wiki/ID

and an ambitious proto-developer.

The goal of the project was/is, essentially, to put a time slider on a fork of the Open Street Map to enable users to search for historical maps that have been loaded into the system.

My original OPW proposal was ambitious and reveled my inexperience. As I worked through the first part of the project and then moved on to tackle the tile renderer, I began to understand the reactions of more experienced developers who I shared my work with. Still, I strove on (see logs).

In the end, I suceeded in integrating a timeslider into the OHM and in propagating a time variable throughout the tile renderer. I've also learned a great deal about how real-live applications look and I've picked up some C, as well.

I plan to continue contributing to the project. As my internship time ended, I was still working on building a working test server. I've had some hardware issues but expect to be able to begin working (part-time - I need paid work, too! :) ) soon. After the initial time variable is proven to work, I will then be able to introduce the actual keys to the render.

I would really like to see my code make it into the wild and it's a great mission. I've learned a lot about how real-life Rails applications work (look, Ma, there's business logic in the JavaScript!). I've learned even more about how far off paper time estimates can be from reality. ;)

Postgres and Postgis are a PAIN

The following is from a blog post from 2009. Installing PostgreSQL and PostGIS is still (still!!) incredibly painful. I'm re-blogging this here (I hope the author forgives me!) I'm terrified of losing these instructions. I know I'll need them again:

_______________________________________________________________

Install PostgreSQL 8.4 and PostGIS 1.4.0 in Ubuntu 9.0.4

HTTP://BIODIVERTIDO.BLOGSPOT.COM/2009/10/INSTALL-POSTGRESQL-84-AND-POSTGIS-140.HTML

WEDNESDAY, OCTOBER 21, 2009

Install PostgreSQL 8.4 and PostGIS 1.4.0 in Ubuntu 9.0.4

I am a big fan of the new PostGIS 1.4.0 (and also of Paul Ramsey) . I always have troubles installing PostGIS in ubuntu so I thought that this time I was gonna document it and blog it here. So this is just a log of the steps required to install it on an EC2 instance with Ubuntu 9.04. I hope it can be useful for someone else.

Just for the record. The EC2 instance I used was ami-ccf615 from http://alestic.com .


Once login (totally fresh).

apt-get update
apt-get install vim

#The sources are still not available on the regular package servers... edit the sources 
vim /etc/apt/sources.list
  add deb http://ppa.launchpad.net/pitti/postgresql/ubuntu jaunty main
          deb-src http://ppa.launchpad.net/pitti/postgresql/ubuntu jaunty main

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 8683D8A2
sudo apt-get update
sudo apt-get install postgresql-8.4

#This changes the port from 5433 to 5432
sudo sed -i.bak -e 's/port = 5433/port = 5432/' /etc/postgresql/8.4/main/postgresql.conf

sudo /etc/init.d/postgresql-8.4 stop
sudo /etc/init.d/postgresql-8.4 start
apt-get install postgresql-server-dev-8.4 libpq-dev
apt-get install libgeos-dev
wget http://postgis.refractions.net/download/postgis-1.4.0.tar.gz
apt-get install proj
tar xvfz postgis-1.4.0.tar.gz
cd postgis-1.4.0
./configure
make
make install
sudo su postgres

#change the postgres password to "atlas" so that you can later login
psql -c"ALTER user postgres WITH PASSWORD 'atlas'"

createdb geodb    (with password atlas)
createlang -dgeodb plpgsql
psql -dgeodb -f /usr/share/postgresql/8.4/contrib/postgis.sql
psql -dgeodb -f /usr/share/postgresql/8.4/contrib/spatial_ref_sys.sql
psql -dgeodb -c"select postgis_lib_version();"

#This should return 1.4.0

exit

Good Luck!

What's the Magic Vagrant Word?

The magic Vagrant command is:

sudo /etc/init.d/vboxdrv setup

Get comfy with that command. You keep needing it.

Leaping into the World of APIs and Data

I am taking a flying leap and creating an entry for GitHub's 3rd Annual Data Challenge. My topic: The Six Degrees of Baconjs. Much like the movie-buff parlor game, the premise is simple: in six degrees or fewer, you can connect every user on GitHub (users who have at least one contributions/contributor outside of their own personal repos) with any other.

I have never attempted anything like this before. From the 10,000 feet view, given an input of a user, I will need to query for a list of all contributors to the Baconjs project and work backwards through each of their other repos to find the next degree's list of users. It's going to be recursive and strange but lots of fun!  I'm starting my studies of the first step with the GitHub API docs and the terrific tutorials on Codecademy. They even have one specifically on the GitHub API!

Wish me luck! I'm going to need it!

Time Flies Like an Arrow and Fruit Flies Like a Banana

That's my new little motivational mantra. Someday, I will help create a computer that understands that sentence.

Back in the present, though, here's a run-down of what I've been up to in the Open Historical Map project:

Week 11: July 28 - August 3[edit | edit source]

1. We're jumping into the rendering now. Most of the work will be in ohm_mod_tile, especially renderd and the master daemon program.
2. I posted the IRC log here (tried to strip out the filler /leave, /join, etc)
3. RENDERING
   1. This file is proving vital but elusive: home/tim/ohm-carto/ohm-carto/mapnik 2008.xml (UPDATE: I have the file now, but...)
4. The bulk of the renderer is written in C and C++ (with a lot of Bash and some inline SQL for good measure.)
   1. I am v e r y s l o w l y and carefully modifying the renderer to accept the {t} parameter. It's been many years since I've even looked at C code (and that was in an introductory C class.)
   2. I'm relying heavily upon the 'git grep' command (tracking here).
   3. I'm logging my progress so I can keep track of what I've changed and where: git diff log.
5. I don't want to lose this reference (is this Momento?):
   1. on line 245 in mod_tile.c, ~~bzero~~ recv() (bzero is used to zero out the bits at &resp to prepare it for the map tiles) and sends &resp to get the tiles from the database over a websocket
6. I am really deep in the weeds here in C. I am going to take a little time to read up more in the man pages and go through some more of the tutorial over on Learn Code the Hard Way

Week 12: Aug 4 - Aug 10[edit | edit source]

1. Made some changes to my changes (meta!) to the renderd.py byte packing/unpacking directive.
   1. IRC log on discussion here
   2. updated diff log here
   3. link on languages and urls from Chippy
   4. link on parameterization of mapnik tiles from Chippy
2. The OHM Team had our monthly Google Hangout notes
3. Re-attempting to install dependencies to run test server, instructions here for Mapnik and here for mod_tile
4. After much searching (and an upgrade to gcc, I finally got it all running well enough to attempt to compile.
   1. Sadly, MediaWiki's spam filter is preventing me from posting a link to the very helpful blog that walked me through the task of upgrading my C/C++/Java compiler. If you visit charette.no-ip.com:81/programming/2011-12-24_GCCv47, you'll get to the instructions.
5. I am now working on fixing the massive list of warnings and errors that running make generated for me!

Updating GCC for C++ 11

I will write up a more detailed blog post on this topic soon, but I wanted to share this:

In a blog post from 2011, Stephane Charette detailed how to determine which version of gcc you are using and how to easily update and switch between versions. (The standard version of gcc included in Ubuntu 12.04 does not support C++ 11). After spending two days thrashing following various official wikis, his blog post was a miraculous!

Linux Scholarship, How to End a Freelance Gig and How to Thrive as a Remote Worker

All of the following can be especially helpful for my fellow OPW interns. The first deals with the Linux Foundation offering scholarships for their (rather expensive) training classes. The second is a summary of Kate Hamill's helpful post on how to wrap up a freelance gig. Finally, Brazen Life wrote a post on how to manage remote workers. I'm going to translate that into how to be an awesome remote worker.

Today, the Linux Foundation announced their Linux Training Scholarship Program. Five scholarships will be awarded, one to a winner in each of the following categories: Whiz Kids (high school or college grads 18 years or older, Women in Linux, SysAdmin Super Stars, Developer Do-Gooder ("developers who are using Linux for good") and Linux Kernel Guru (a Linux contributor "who has promise of becoming a Linux kernel developer or maintainer.")

If you're a Linux Lover, check it out! Applications are due by midnight (PDT) on Monday, September, 2nd.

---

Over on the Freelancers' Union website, Kate Hamill has a post on the three things that freelance pros do when they finish a gig. Step one is to make sure you really are finished with the project. Now is the time to check your work and make sure there aren't any loose ends. She also advises freelancers to send out an email to get confirmation (in writing!) from the client to be sure that they believe the project is finished. Step two is to send a thank you email to your client. Why email? Because then your client can easily search their email for you. Very, very few people systematically file away thank you cards. Finally, Hamill recommends connecting with your (now former) client through social media.

---

Finally, Brazen Life describes seven ways for managers to do a better job of managing their remote (or "virtual") workers. It's a great list of tips, especially if you flip it and turn it into seven ways to thrive as a remote worker:

1. Be clear on your role and responsibilities. Being remote means missing out on those micro-moments where you can check in to make sure you and your boss agree you're on the right track. Starting your day with a list of that day's essential tasks (and then sharing that with your manager) can be a useful way to accomplish this.

2. Use some of the great tools out there like Basecamp or GitHub to create shared goals and track them.

3.  Keep communicating! If your manager hasn't already, try to set up a regular scheduled time to catch up and keep your manager informed of your work.

4.  Seek out novel ways to collaborate and create those "water cooler" moments. Scott Hanselman describes one way to do this in his post on "Virtual Camaraderie."

5.  Seek out co-working spaces, local offices or create one. This can give remote workers in your region a place to come together in company nodes and share information, ideas and, yes, collaborate.

6.  If there isn't one already, help create a central place to keep the knowledge of the project. GitHub can be great for this. (That's what we use for the Open Historical Maps project.)

7.  Find ways to tailor your work to you. One danger in being a remote worker is the risk of being seen as a widget that can easily be replaced by the next Gun.io applicant. By tailoring your work to you, you can become an indispensable part of the team, no matter how far away you are.

That's it for now.

Some Bits on Binary Packing and Holding Broken Packages

The first part of my day was spent on binary packing in Python. When using this feature to share objects between languages, you pack the structure/object into binary and deliver it with instructions for how to parse or unpack it. The format of the instructions will look something resembling this:

self.fields = "5i41sxxx"

where the structure is comprised of 5 integers followed by a 41 bit string followed by 3 null bits added for padding to make the structure add up to a total of 64 bits. My current task on the OHM was to add the {t} variable to this binary structure. Misunderstanding, I added the length of the 5 bit string to the existing 41 bit string. However, I learned that, unlike for the 5 integers, 46s would be treated as a single 46-bit string (logical but not obvious to me at the time). Instead, we opted to insert a second 5-bit string before the padding (which was increased to a total of 61 to increase the size of the binary structure to a nice, even 128 bits.)

Later that day, I spent a lot of time searching for solutions to an installation problem I was having. My updater was howling about need to update the firmware. My initial attempts were met with a strange error about having "help broken packages" (which drew up a most disturbing mental image). After lots of searching, I finally found a helpful post on AskUbuntu which described in detail the steps needed to clear this error. After typing:

sudo apt-get install xserver-xorg-lts-precise
hwe-support-status --verbose 
sudo apt-get install linux-generic-lts-trusty \
xserver-xorg-lts-trusty libgl1-mesa-glx-lts-trusty \ 
linux-image-generic-lts-trusty

TBH, though, I kind of wish that I hadn't updated because now Spotify won't run in my browser and the delete key fails on a long press. Google's suggested search when searching straight out of the address bar is malfunctioning as well. Something good will come of it, though. I'll have some fresh learning to write about tomorrow night!

10 Ways to be Smarter

A recent article by Jessica Stillman in Inc. magazine summarizes a recent Quora posting on what can you can do to get smarter. In short:

1.  Be smarter about how you use your time on the Internet. Think more TED talks, Khan Academy and (presumably, Inc. magazine) and much less YouTube, Farmville and Cracked.com.

2.  Write 400 words a day about something you learned that day.

3.  Make an "I did it" list to remind yourself of your accomplishments.

4.  Play games: chess, Connect 4, bridge, (MtG, anyone?).

5.  Surround yourself with friends who are smarter than you.

6.  Read a lot. A lot.

7.  Explain what you've learned. You don't really know it until you can teach it to someone else so they will understand.

8.  Do random new things. You never know how what you learn will help you down the line.

9.  Learn a new language. (I hope programming languages count!)

10.  Take some time to digest what you've learned. Sit and think (or exercise and think.) Spend time thinking.

I'm going to start with #2 tonight.

How to Change Tab Size in Vim and Other Nifty *Nix Tricks

I learned two nifty *nix tricks this week that I'd like to save here both so I can find them again if I manage to lose my notes (or my muscle memory) and in the hopes that I can save another future dev a little bit of time.

To change your tab size in Vim, first at the command line, type:

vim $HOME/.vimrc

This will open the user preferences file for Vim, creating it if the files doesn't already exist. You will then be popped into your Vim editor, where you can enter your preferences. Remember to type the letter a to enter insert mode. Otherwise, anything you type will be interpreted as a Vim command. Ready?

Here's where you can paste all those nifty "yak-shaving" "time-saving" snippets you've been finding online! I used

set tabstop=4
set shiftwidth=4
set expandtab

Press the esc key to re-enter command mode then :wq to save and exit. Re-open Vim and voila! You've just set your tabs to 4 spaces!


My second trick is much shorter, but it's a great little command just the same. When working in Git, before you add any files using git add type

git diff

to see the changes you've made across all of the files in your working repository. If you've already started tracking the files using git add, type

git diff --cached

It gives you lovely output such as:

That's all for now. Happy coding, everyone!

Progress and More to Come

We made some progress over the last two weeks. We've got the time query running through the software, all the way up to the point requesting the tiles. Now we're diving in to the code of the renderer and tile server to get those tiles that we need!

Week 9: July 14 - July 20[edit | edit source]

1. After some discussion and direction from my mentor, I'm tackling the tile rendering server bit. I've added a test layer for "Year" in the leaflet.osm.js file.
2. I've got a first little skeleton in the code but it doesn't lead anywhere yet. I updated the issue tracker in GitHub with my latest and (not so) greatest.
   1. The screenshot is also posted here
   2. As can be seen by the mostly empty layer on the right, I've got most of the plumbing in there but there's no data coming through the pipes.
3. Digging further into Leaflet and how to use it and I also put up a white flag for assistance in the issue thread above

Week 10: July 21 - July 26[edit | edit source]

1. At the beginning of the week, I felt a little discouraged after seeing this postin the mailing list about how nomoregrapes built a working slider over an isolated OHM map during the Hackathon at SoTM-EU. I went through thecode he posted on GitHub and linked to it in the GitHub OHM issues tracker.
2. After a lot of hacking and many false starts (and some help from my mentor), by the end of the week, I found the proper places in the code to add references to the {t} value for searching. My commits and code.

In less positive (and more personal) news, I got word that I was not accepted for the next cohort of the Ada Developers Academy. Keep looking here because after my OPW internship is over, I'll post my progress on my work for the GitHub data challenge!

In the Weeds

I've been spending the last few days in the weeds of Leaflet. For the full play-by-play, you can see the GitHub issue.

My Very Frustrating Day

Fastest Summer of My Life!

Time seems to be moving faster and faster. I can hardly believe it's time for another two-week report! I spent a lot of time chasing bugs but I'm making baby steps forward and learning a lot about how Rails and JavaScript work in live code.

Week 7: June 29 - July 5

• On Monday, the OHM team had our monthly Google Hangout (which I have learned is the first Tuesday of the month). The very sketchy notes are posted online.
• At the Hangout, I was introduced to a new resource: the design prototypes for Wikimaps search. I'm pouring over them today. In fact, I spent an inordinate amount of time reading new material and going through archives to catch up. At every Hangout or meeting, I come across more terms and talking points that leave me confused. I'm filling in the gaps. My reading list has included:
• reports on Zurich Hackathon
• the Wikimaps Search Design page above
• more on vector rendering of tiles in preparation for my next steps
• RfC for How to Deal with Open Datasets
• Overview of Wikimaps
• I am getting most anxious about continuing to work on my own branch of the OHM for so long. I would like to push to Master soon, but I need a better-working demo before I do so.
• I've been spending a lot of time there attempting to craft an appropriate request to get something other than a doctored error message to appear on the site when searching by year.
• The most excellent Frances Hocutt introduced me to the Wikidata API Sandbox. It is proving quite helpful. APIs are a whole new world to me.
• To appease my anxiety, I submitted a pull request with my most up-to-date code. 

Week 8: July 6 - July 13

• And the code I've written was deemed not yet ready for prime time - it only works halfway at this point. I will resubmit after I get the code up to production standard.
• After some useful feedback on the importance of submitting a pull request with only one commit (and some pointers to how-to's on rebasing to make that happen) and the helpfulness of of including *lots* of screenshots showing the software in action, I closed the pull request.
• One (!!) of the aspects of this project that I have found especially challenging is finding my way through the blending of JavaScript and Rails code. I spent an inordinate amount of time this week chasing down what turned out to be a Javascript syntax error that was manifesting as a Rails error.
• I've installed the "better_errors" gem to try to assist with errors like this - it will presumably be triggered if it is a true Rails error
• I've also learned that if I make changes to the JavaScript portions of the code, I have to restart the server in order to see any changes. Most changes to the Ruby code automagically propagates without restarting the server.
• Screenshots of my progress so far are on GitHub. Searching by year (2008 and 2009) will bring up the Burning Man map layers for those years and recenter the map to that area. Searching by any other year brings up with message that this is a work in progress. (It no longer crashes the map and brings up the dreaded Rails error screen, so there's some progress there!)

Hoping to Catch My Breath

I've been so immersed in my internship that I've been neglecting this poor blog. I'm still constantly surprised at how much longer seemingly simple tasks take. I'm very slowly getting familiar with the complexity of the OHM codebase. Here's a rundown of the last two weeks:

Week 5: June 16 - June 22

• I spent far too long this week chasing Heroku errors in an attempt to get a live version of my time_slider2 branch online. After an IRC chat with my mentor, I cut my losses and moved on to the next task:
• Capturing the start_year value entered from the TimeSlider
• I found a new resource: a StackOverflow-style QA page for OSM
• Regrettably, this resource seems focused on map-editing users. It did help me discover when I was headed (meandering?) down the wrong track with the router file in Rails and needed to pivot and work on the router.js file.
• This was a real Edison week. I found a dozen different ways that don't work. Still at it.

Week 6: June 23 - June 29

• Completed and submitted my mid-session evaluation.
• I'm not where I thought I would be at this point in the session. There is a tremendous difference between the code used in tutorials and student-level projects and the real, live code that lives out in the wild.
• It's more than just the complexity (although the huge leap in complexity would be more than enough to stymie me!) There are unfamiliar conventions and blending of platforms that still surprise me. (I'm still getting caught flat-footed and discovering that the code I'm writing in Rails needs to be ripped out and put into the JavaScript portions of the code base.) I will learn.
• I'm having a meeting with my mentor on Tuesday, and hopefully that will give me some grounding.
• I'm making an effort to commit more often and to push up my commits to my branch more regularly. I've been fearful about doing so but last week, I caught myself trying the same failed function twice. Having all of my commits with failures noted well help stop me from doing that in the future.
• I made some baby steps toward success:
• screenshot
• issue tracker

Bi-Weekly Summary of a Rough Two Weeks

It's been a very busy last couple of weeks, unfortunately busy with roadblocks. Progress has been slow but I feel like I've been learning a lot about the OHM codebase and that this will help further down the line.

Week 3: June 2 to June 9[edit | edit source]

1. Snagged TimeSlider code from themusictree.net website
2. Continuing work on getting the slider integrated into the website and I'm learning:
   1. Building consensus can be hard - there are a lot of differing opinions over what the TimeSlider should look like and how it should function.
   2. While I know Rails, finding one's way around a new code base can be tricky, to say the least. I'm using the Rails UI Wiki page and this Guide to Erubis to try to lead the way.
3. I've been very surprised at how much of the logic of the site is in JavaScript. The other Rails projects I've dug into have been mostly Rails with a little JavaScript for buttons and hover effects. This project is a JavaScript project wrapped in a Rails app. I'm still getting a handle of its complexity.
4. I'm still working on getting the slider working but I've got the text fields showing, at least.
   1. They needed a lot of tweaking to fix and flex to the space of the site. My branch is posted on Github.
   2. I have hit a major roadblock with the bottom half of the slider. The divs generated in the JavaScript portions are not rendering on the site. I've used console.logs throughout, testing to be sure that the script is running but I have not yet found the problem. I'm reaching out to my mentor for some assistance for what else to try to find the answer. I've exhausted my ideas. (None thus far have worked.)

Week 4: June 9 - June 15

1. After consultation with my mentor, we were both stumped so we reached out to the author of the slider for tips and toward the end of the week, we finally synced and got the slider working! The slider required a change from rendering a single object to iterating through a group of divs to create the sliders.
2. While I was waiting to work with the slider-creator, I started investigating methods for having a form in Rails have two separate actions, depending on the button clicked. It's apparently a little non-REST-full, but there are some REST-like options:
   1. using the params and embedding if statements into the controller or
   2. capturing the name of the button that is clicked.
3. I also cast about for other options that might be more understandable for me (this was a plan Z option, in case I never was able to connect with the original author.) I found a few nice options including nouislider.
4. Received a last-minute invite to the OHM/OSM Hangout at the @SotMEU Conference on June 13th.
   1. The audio was very difficult to understand, but Susanna Ånäs pointed me to SK53 and Maps Matter Blog I spent a lot of time reading through to get more familiar with the history of the project.

A Quick Bi-Weekly Re-cap

Week 1: May 19 to May 25

1. Researched history of OHM project in the mailing list archives and GitHub issues here and here.
2. First OHM planning meeting on Google Hangouts, synopsis by Robert H. Warren posted at May 22 OHM Hangout Synopsis
3. Added to Github OHM organziation and (scarily) given push access.
4. Assigned and began work on microtask of investigating client side rendering.

Week 2: May 26 to June 1 - DRAFT/WIP

1. Went spelunking through the OHM Rails Port to find where to place the slider (and was later introduced to (and made a small link fix within) the official OHM UI wiki page.
2. Attended #OPW IRC chat for OPW Interns on May 27 3PM UTC.
   1. We had a round of intros and some general questions
   2. Sumana Harihareswara is now the official "so where do we go after this is over" post-internship planning mentor
   3. Sumana also posted a link to a very helpful article on when to ask for help First You Must Try, Then You Must Ask.
3. During this week's Google Hangout meeting with my mentor, we reviewed the task from last week and discussed next steps
   1. find a place for the TimeSlider on the OHM site
   2. start finding a way to make input from the TimeSlider feed into the website and request the tiles needed (this one's a higher level task and will break out into other pieces)
4. I posted mockups of two different ideas for TimeSlider placement:
   
   1. within the header of the site
   2. attached to the search box on the site

Seeking An Alternative to The JQuery UI Slider

I've spent most of the weekend digging around in the Open Streetmap code base on GitHub. If our first goal is to develop a slider that will fit in (over?) that code, I'd like to make sure that whatever we create will mesh nicely with what's already in that repository. If I'm reading this correctly, the code already includes JQuery via the jquery-rails gem. What it doesn't have is the JQuery UI. The initial slider(s) that I've been working with both depend on the JQuery UI module, so I went spelunking in the JQuery UI code.

Wow.

There's got to be a better way.
__________________________________________________________

Update (5/20/15): Yes, there is another way. Your mentor finds someone who enjoys the front end piece to build the slider!

Signed, Sealed, Delivered

I'm yours for the summer, Outreach Project for Women :).

I just successfully (I hope ;) ) uploaded my signed contract for the OPW.

Muggles, Outsiders and Empathy

I was listening to Hanselminutes yesterday. (Yes, yes, I realize that's like Hermione saying she went to the library yesterday.)

And what precisely is that supposed to mean?

The guest on Hanselminutes was David Starr, who's especially known for using Agile methodologies, including at home, as part of managing his family. It was an interesting conversation and definitely worth some time. They got to the part where they needed to come up with a gender-neutral term for their better halves. (As in the person you need to explain Trello to and convince to use GitHub for the family shopping list.) Mr. Hanselman suggested the term "non-technical spouse." It doesn't exactly roll off the tongue.

Muggle is the word I use (in my head, at least.) But not just for technical stuff. In my house, we're all rather technically-inclined, but in different areas. Most of us are gamers, one is not (full disclosure: that's me). We're interfaith with a ratio 4:1. One of us can't watch PG-13 movies. Females outnumber males. The young outnumber the old ;). No matter how you slice it or which grouping you choose, there's always going to be someone who's left out. There's always someone who feels a bit like an outsider. There's always a Muggle in our midst.

That actually makes it a good thing. Because the borders around our various allegiances shift with every different topic, each of us experiences being the Outsider. And because each of us empathizes with that feeling of not knowing what everyone else is so excited about (or even understanding half of what they're saying), we all can have a lot more compassion and patience with each other. (We can, not that we always do. This is a real family, not a PSA or a very special episode of Jesse.)

The whole world is like this, if you look hard enough. We're all the Muggle sometimes. Imagine what could happen if we all took a little more time to remember this.

Today

I've been lurking on the Ada Developers Academy website for months, waiting for this day. The application for the September class is posted.

ZOMG!

There are now two logic puzzles (yeay), the Markdown resume, reading assessment, and still the YouTube video requirement (not so yeay) but I've already dug in. Nothing's going to stop me from applying this time.

Most especially myself.

Ada Developers Academy is a Gift to Seattle

Yesterday, Emily Parkhurst's interview with Geoffrey Moore was making the rounds on Twitter. Moore's basic argument is that public policy (tax breaks, planning, education, etc) should be more focused on the tech sector and the convergence of UX, data and the cloud and less focused on increasingly less relevant companies (cough, Boeing, cough, cough.)

As if on cue, Code for Seattle hosted a round of presentations by the first cohort of Ada Developers Academy. The night was all about civic apps and (although I was egregiously late) it was a peek into the greatness that ADA is releasing into our city(ies). Three apps were demonstrated tonight:

Where Can I Park?
http://wherecanipark.in/seattle­
Conceived, coded and created by Hsing-Hui Hsu and Liz Rush, this app helps drivers in Seattle make sense of the insanity that is finding a place to park.  Sadly, it doesn't work outside of Seattle (but that's where you really need it, anyway!)

What Do I Do With____?
http://www.wdidw.com/
Created by Audrey Carlsen, WDIDW was inspired by the (rather sad) old King County website that attempted to do the same. It's a really cool app. I wish it had been around the last time I moved! :)

Map My Districts
Map My Districts is a special in-house app that was created by Anne Kimsey for the Seattle City Council in order to cope with the new redistricting that just took place.  My head almost exploded when she showed the polygon math that's going on in the background when drawing the maps!

And these are just three of the capstone projects created by the first cohort of the Ada Developers Academy after 24 weeks of studying. Can't you just imagine what scores of ADA graduates are going to be able to do for Seattle?

Let's Do the Time Slide Again!

The official start of my internship with Wikimedia is rapidly approaching, so I've started hacking away at the first listed goal: The TimeSlider.

I've got this as a beginning prototype:

<!doctype html>
<html lang='en'>
<head>
  <meta charset='utf-8'>
  <title>jQuery UI Slider - Range Slider</title>
  <link rel='stylesheet' href='http://code.jquery.com/ui/1.10.4/themes/smoothness/jquery-ui.css'>
  <script src='http://code.jquery.com/jquery-1.10.2.js'></script>
  <script src='http://code.jquery.com/ui/1.10.4/jquery-ui.js'></script>
  <script>
    $(function() {
      $('#slider-range').slider({
        range: true,
        min: 0,
        max: 500,
        values: [75, 300],
        slide: function(event, ui) {
          $('#amount').val('$' + ui.values[0] + ' - $' + ui.values[1]);
        }
      });
      $('#amount').val($('#slider-range').slider('values', 0) + ' - ' + 
         $('#slider-range').slider('values', 1));
    });

I posted a link to a working model on the Open Historical Streetmap mailing list, the Bugzilla report and on the Github issues page. I've been getting some great (if somewhat conflicting ;) ) feedback, which was just what I needed. I will post more soon!

Baby Steps, Indeed

I just earned the Baby Steps badge on Project Euler. (You earn it after solving three problems.) Yes, it's baby steps but I did it! :) (It's been a nice distraction from the confounding errors in my other project. Yes, I'm getting back to it now...)

BTW, 600851475143 is a very large number. My computer doesn't like doing ANYTHING that many times ;).

Bug Hunting

So I'm banging my head against an odd error in an RSpec test. In case you missed the last post:

 1) Posts when the user has authenticated when there are posts can be deleted from link on posts page

     Failure/Error: click_link 'Destroy'

     Capybara::ElementNotFound:

       Unable to find link "Destroy"

     # ./posts_spec.rb:71:in `block (5 levels) in <top (required)>'

     # ./posts_spec.rb:69:in `block (4 levels) in <top (required)>'

I tried modifying the way the Capybara test selects the 'Destroy' link.  Instead of:

         within 'tr:last-child' do

            page.driver.accept_js_confirms!

            click_link 'Destroy'

         end

I tried:

    within 'tr:last' do

            page.driver.accept_js_confirms!

            click_link 'Destroy'

         end

That delivered a new kind of error:

     Failure/Error: within 'tr:last' do

     Capybara::Webkit::InvalidResponseError:

       SYNTAX_ERR: DOM Exception 12

     # ./posts_spec.rb:69:in `block (4 levels) in <top (required)>'

So, that didn't work. There are two other places in the spec where the tutorial I'm using said to use "tr:last" instead of "tr:last-child" because of a Capybara bug. I see now why the tutorial didn't have us change the middle describe block.

So I went back and took a shot in the dark and tried giving an id of "destroy-link" to the <td> containing the 'Destroy' link. Capybara didn't like that:

     Failure/Error: within '#destroy_link' do

     Capybara::ElementNotFound:

       Unable to find css "#destroy_link"

     # ./posts_spec.rb:69:in `block (4 levels) in <top (required)>'

The 'Destroy' link is actually in a child of the td, so in hindsight I'm not too surprised that it didn't work. Looking at the code a second (fourth? fifth?) time, though, I had an idea. Can I select the td>tr ? 

Apparently not.

     Failure/Error: within 'tr>td' do

     Capybara::ElementNotFound:

       Unable to find css "tr>td"

     # ./posts_spec.rb:69:in `block (4 levels) in <top (required)>'

I tried it with and without the spaces on either side of the child '>'. No dice. Time for more digging through StackOverflow ;). 'Night, all!