Bendyworks

This is about that oft-neglected corner of programming, the humble boolean. Perhaps, by thinking about what’s going on in many boolean expressions, we can iron out his quickly-forking complexity. And, oh, what luck! Here’s a slab of boolean logic that I just happened to have at hand (variable names have been changed to protect the innocent):

I have found that stuff like this is easy for me to get wrong, hard to read, and hard to refactor. What could be done to simplifiy these cases? Consider just the first line of the above, (hash[:foo] == "1" || !hash.has_key?(:foo)). Already, there are two competing interests here. What is going on is that we are conflating value-testing with existence-testing. What we may ...

Yesterday, at the request of their teacher Suman Banerjee, I presented a view of what it’s like to be a professional programmer to a class of Computer Sciences students at the University of Wisconsin–Madison. The focus of the talk was “Mobile & Professionalism,” since the class’ title is “Foundations of Mobile Systems and Applications.”

The slides are available on Speakerdeck and auxiliary information is available on my github page.

In essence, my talk was split into two sections: Mobile Development & Professional Development. Given only 75 minutes to talk, I had to pick just a few topics for the entirety.

I started with an in-depth discussion of the MVC pattern and how it applies to native applications. Upon asking the class who had heard of this pattern, only about half of the hands went up, so I certainly had my work cut out for me. ...

Today marks a milestone for the Travis CI project: it launched a crowd-funding campaign titled love.travis-ci.org to finance a slew of new features. Among the planned additions are private build support, pre-tested Github pull requests, build artifacts, and more language support.

Bendyworks is proud to be a platinum sponsor of this effort. We sincerely believe Travis CI is ushering in a renaissance of software authorship, doing for testing what Github did for source code management.

Why do we believe this? If you look at the proposed feature list, Travis CI is looking to turn a simple continuous integration server that simply reports “red” or “green” into a complete service that takes the guesswork out of a project’s health. And once you can see a project’s health, you can start improving it. Here are a few of the planned additions that will make Travis more that just a community CI server: ...

Here’s how Bendyworks has given back to the community in the past week:

Jim recorded an interview with the fine folks at EngineYard about our experiences working with them. Look for the link to the audio soon!

Madison Ruby registration and Call for Proposals are now open!

Brad started a gem called guard-readme-on-github that allows you to preview your README files as if they were already pushed to Github. Just pull it into your gemfile and set up your Guardfile with:

[bundle exec] guard init readme-on-github

Matt worked with Angel N. Sciortino on schedule_fu and rschedule.

Brad and Matt made a change to the popular heroku_san gem to store the last deployed git commit SHA in Heroku config variables. You can view the pull request for this feature in the mainline heroku_san ...