New Job Opportunities at Ona

Posted:

We are looking to add three important new members to our team. We are actively looking to fill these positions in early January. So if one of these positions looks like the dream job for you (or you know someone who might be a great fit) please apply now!

Operations Manager, Nairobi

We are looking for someone to help build the systems required for our company to continue to grow. We are particularly interested in people with strong accounting experience and who know how to setup and run organizations in Kenya.

View full job posting

Support Specialist

We are looking to add a dedicated support person to our product team. We’re seeking someone with great attention to detail, passionate about support an ideally a bit of a data geek. French speakers are encouraged to apply.
View full job posting

Software Test Engineer

We are looking for an engineer to help lead our software quality assurance processes. The ideal peson will be a great software engineer, extremely detail oriented and passionate about the critical role QA plays in modern software development.

View full job posting


Map Your World and Ona at Geo for Good 2015

Posted:

Ona Collect

This past October I spoke on behalf of Map Your World at the 2015 Geo for Good User Summit.

Map Your World empowers youth to explore issues and ideas that matter - like clean drinking water, or food justice – then write surveys, collect data, and create maps to make change in their communities. This amazing project is powered by the Ona API.

Below is a video of the talk I gave, which includes a clip from the film The Revolutionary Optimists.


Clojure Destructuring Gotcha!

Posted:

Given the following function definition, what would you expect to happen if you ran (hello :person nil)?

(defn hello
      [& {:keys [person]
          :or {person "Rich"}}]
      (str "Hello, " person))

(hello) => "Hello, Rich"
(hello :person "Hickey") => "Hello, Hickey"
(hello :person nil) => "Hello, "

I’d have expected (hello :person nil) to have the same result as calling (hello), but as it turns out, Clojure seems to make a distinction between nothing and nil when it comes to destructuring.

A real world situation where this might occur would be where you, for instance, rely on the result of a destructuring operation to provide parameters for a function similar to hello. e.g.

(defn spam
      [& {:keys [person]}]
      (str (hello :person person)
            "Give me all your money."))

Calling (spam) would result in (hello :person nil) being called, which would have the - probably - unintended effect of returning "Hello, ". You may choose to add an :or when destructuring the argument to spam, but then you’ll have the same code appearing twice. A more localised solution would be changing the hello definition to be something like this.

(defn hello
      [& {:keys [person]}]
      (str "Hello, " (or person "Rich")))

This worked for my case, but I’d love to hear about more idiomatic approaches.


A New Client for Smartphones: Ona Collect

Posted:

Ona Collect

Today we are announcing the launch of Ona Collect, a tweaked version of ODK Collect created especially for Ona users. This new mobile client is a baby step into building a seamless experience for our users, starting with a few small improvements.

 Continue reading A New Client for Smartphones: Ona Collect...


Take Our Survey!

Posted:

Projects

Ona is conducting an online survey to better understand challenges faced by our users. If you use Ona now — or have in the past — we’d like to hear from you. Click here to take the survey.

How it works:

Please take a few minutes to complete the survey. It’s your chance to help us define our roadmap! Responses to this survey will be used internally only — and all individual responses will be kept strictly confidential.

Following the survey, you will be entered into a drawing to win a $50 Amazon gift card (or equivalent online retailer in your country). We will randomly draw three (3) winners, to be notified on Friday, December 4, 2015.

Thank you for your participation.

  • The Ona Team