Haught Codeworks

Exploring topics dear our hearts including prototyping, project rescues, growing teams,
working remote, current trends in software, and more!


I’ve been working on a Rails 5 project that employs an infinite loop in conjunction with a few nested breakable loops. Code/case coverage is particularly important, as the program interacts with Cryptocurrency exchanges. Errors or unexpected behaviors can potentially result in financial loss.

I was expecting the loop tests to be convoluted, heavy...


I recently added file upload support to an Ember application that talks to a Phoenix API server using the JSONAPI protocol. I wanted a solution that integrated well with Ember and ember-data, supported direct uploads to S3 from the client, included drag and drop support for choosing files, and had the ability to show upload progress. After experimenting...


Recently, a project we’ve been working on at Haught Codeworks got to the point where we needed to add additional columns to the database for one particular model. This meant that for any future instances of this model, those columns could be populated upon creating the instance, but any past instances would not have those fields associated with them...


In the last article we looked at using Ecto schemas to read records and associations from a database built according to Rails naming conventions. This time we will extend the examples used in that article to see how Ecto changesets can help us write records to the database in a safe and consistent way.

The example apps can be found at PlaygroundRails


I recently migrated a Rails JSONAPI server to Phoenix, and in the process I learned a lot about using Ecto with a database that conforms to Rails naming conventions. It turned out that I was able to share an existing Rails database between the Rails and Phoenix implementations of the server during development, which allowed me to use a phased approach...

Page 10 of 14

Newer posts

Older posts