Full time position in Oklahoma City

Brightbit is looking for a Full Stack Developer (some front-end and back-end) to build well-crafted web applications at our Oklahoma City headquarters. As a member of our development team, you’ll build responsive and elegant interfaces using Ruby on Rails and similar technologies, while possessing a deep understanding of our entire application stack.

• Between 3 and 5 years development experience
• Basic proficiency jQuery and Javascript
• Understanding of best practices for HTML5 & CSS3
• Experience working in MVC frameworks and templating languages (Ruby on Rails)
• Proficiency in Git and using Github for pull requests
• Experience testing your code (e.g. rspec, minitest, Jasmine)
• Self managing and ready to be the lead on a project if necessary
• You already live in the Oklahoma City area or can relocate

• Proficiency in using Heroku to host and scale web applications
• You know what zeus, simple_form and pry are.
• Experience freelancing and handling client communication
• Contributions to open source software
• Show us some projects and sites you have built on your own
• You enjoy comfortable mexican sofas

• Competitive salary
• We’ll have a MacBook Pro ready for you (and other Apple equipment)
• 2 days in the office / 3 days telecommute per week
• We’ll pay for lunch on office days
• Flexible hours/schedule
• Relaxed and friendly office atmosphere
• 2 weeks paid time off

Send your resume and references to hello@brightbit.com * we’d love to work together!

Brightbit is an application development studio with years of experience crafting apps of all sizes. We are passionate about making the web a better place to live.

Full time position in Oklahoma City

Brightbit is looking for an experienced salesperson to help us continue to grow our company. The ideal candidate for this position possesses excellent communication skills and is passionate about innovation and web technology.

• At least one year of sales experience
• Basic familiarity with the processes and tools used to build web and mobile applications
• Enthusiasm for design, technology and the internet
• Strong writing and editing skills
• You already live in the Oklahoma City area or can relocate
• Honesty, integrity, and a good work ethic

• Experience with the sales process of large development projects
• You have managed an online ad campaign

• Competitive salary
• We’ll have a MacBook Pro ready for you (and other Apple equipment)
• 2 days in the office / 3 days telecommute per week
• We’ll pay for lunch on office days
• Flexible hours/schedule
• 2 weeks paid time off
• Relaxed and friendly office atmosphere

Send your resume and references to hello@brightbit.com - we’d love to work together!

Brightbit is an application development studio with years of experience crafting apps of all sizes. We are passionate about making the web a better place to live.

Jonathan joins us after spending a good amount of time freelancing, and we’re anxious for him to put his self-motivatied work ethic and entrepreneurial skills to use for us and our clients.

Matt’s focus will be helping us grow as a full-service web and mobile development studio by handling all the sales and day-to-day business operations work, allowing us to focus more on creating awesome things for our customers. We look forward to a great 2013 with Matt on board (assuming the apocalypse doesn’t come).

This post will cover how to add a custom validation, how to translate error message strings (including translating custom error message strings), and how to test for the existence of your custom validation error message with RSpec.

Add Your Custom Validator

This is the easy part. Add your custom validator like normal to the model you want to put it on using the validate method.

1
2
3
4
5
6
7
8
9
10
11
12
13
14

class Booking < ActiveRecord::Base
  belongs_to :listing

  validates_date :check_in, before: :check_out
  validate :listing_available?, if: :listing

  def listing_available?
    # Our actual logic in this case is on the related listing model
    if !listing.available?(check_in..check_out)
      # Add to :base when no specific single :field is applicable
      errors.add(:base, :not_available)
    end
  end
end

Note we are using the symbol :not_available instead of an actual error message string. This is because the text of this error message will be in the Rails locale file instead of hard-coded in the model. We are also using the excellent validates_timeliness gem to get the validates_date method.

Add your Validation Message to the Locale File

Your custom validation should be added to the locale file so that it can be translated and is more resilient to wording changes (i.e. updating the wording of the error message won’t break your tests). If you’re just getting started with locales, this is located in config/locales/en.yml by default (or you can create a new one for your target language in the same location like de.yml).

Full locale example with YAML indentation for both errors above:

1
2
3
4
5
6
7
8
9
10

en:
  activerecord:
    errors:
      models:
        booking:
          attributes:
            base:
              not_available:  'Listing is not available for specified date range'
            check_in:
              before: 'must be before check out'

Accessing the Translation Strings in Your App

To access the translation strings in your app and in your tests, use the translate library provided by Rails: I18n.t (see the Rails Guide for more info).

Expected locale error format:
activerecord.errors.models.<MODEL>.attributes.<FIELD_OR_BASE>.<ERROR_KEY>

Take note of the model name, field name, and key name where you are adding your custom validators, because you will need all of them when accessing your error message string for testing.

Examples

Booking model error on base (validates multiple fields):
I18n.t('activerecord.errors.models.booking.attributes.base.not_available')

Booking model error on check_in (one specific field):
I18n.t('activerecord.errors.models.booking.attributes.check_in.before')

Ensure the Validation Exists with RSpec

Now we need to make a test to ensure that our new custom validation is working properly. We use RSpec for writing & running tests, and FactoryGirl for creating our test objects, which are both available as gems.

1
2
3
4
5
6
7
8
9
10
11

describe "my custom validation"
  it "will not create a booking that overlaps another accepted booking in date range" do
    # We have previously setup a booking in this date range in our test fixtures, so this will error
    booking = FactoryGirl.build(:booking)
    booking.check_in  = Date.today - 2
    booking.check_out = Date.today

    booking.valid? # trigger validation to run (without saving)
    booking.errors[:base].should include I18n.t('activerecord.errors.models.booking.attributes.base.not_available')
  end
end

Run Your RSpec Tests

Now we can run the tests to ensure everything is working and that our validator is doing its job (or not). In practice, you will want to ensure the test fails by writing it first and verifying a failing test run result. You then write the code the makes the test pass, and re-run the tests to ensure it passes.

We use Guard on all our Rails projects so that our tests are automatically run after any filesystem changes. It can be easily integrated into your Rails project by adding it to your Gemfile. Check out the Guard RailsCast by Ryan Bates if you want to learn more about how to use Guard with RSpec and Rails.

The new office is in the beautiful historic Film Exchange building on Film Row, one of the iconic brick buildings downtown. Venture Spur is one of our neighbors, and their startup accelerator starts up in August so we look forward to being around the excitement.

About 10% of fantasy leagues don’t get paid out at the end of the season due to bad communication and questionable commissioners. SportsVault aims to help make sure that fantasy sports leagues stay active and team owners feel secure.

I’m not sure what it is about getting an office, but it makes thing seem more real to actually have a dedicated place of doing business. It somehow legitimizes your business for both you and your customers. Keeping expenses low is a concern, but it’s important to start things off in the right frame of mind. Fortunately, we were able to keep both concerns in check by getting a private office at the OKC Coworking Collaborative - a local tech-focused co-working space with good rates and great company. We pay a single monthly rate that covers the office, internet, electricity, and even coffee. It’s a great place to start a business that doesn’t require applications or approval like incubators. Come check us out if you’re in the area. We have a flexible schedule and we work from home sometimes, but there’s always at least one of us in the office on Tuesdays and Thursdays.

Brightbit 723 North Hudson Ave Oklahoma City, OK 73102

hello@brightb.it

Here’s to a long and successful future for Brightbit.