Jamie Schembri

PointFactory builds an RGeo point, DRYing up similar calls across the codebase. Instead of returning the raw point, however, I define `lng` and `lat` methods on it, which are just aliases. This makes the resulting object more ergonomic without bike-shedding bigger tools like inheritance.

2/2

require "rgeo" module PointFactory REFERENCE_SYSTEM = 4326 def self.build(lng:, lat:) raw_point_factory.point(lng, lat).tap do |point| def point.lng = x def point.lat = y end end def self.raw_point_factory @raw_point_factory ||= RGeo::Geographic.spherical_factory(srid: REFERENCE_SYSTEM) end end

Today I used a little technique I picked up from a @kaspth.com workshop: defining methods directly on objects.

1/2

In which counterworld do you live?

A "procedure" is as much of an object as a "user", a "controller" or a "cat". The fact that some things are more clearly described as a sequence of operations does not make them "not object oriented". And even if it did, who cares!
Good code describes the flow of information effectively. That's it.

Love this!

That’s no caterpillar, it’s a snake.

I love this.

…ohhhh

I wear crocs all the time at home and in the garden. Have no kids.

If either of you do, please report back!
I’m not sure what I’d make of seeing this on a cv tbh.

Code Complete is timeless. Need to re-read it, really.

TIL The Linux Foundation offers a course + certificate for $79 on JSON and YAML.

JSON. And YAML.

I wonder who this is targeted at.

trainingportal.linuxfoundation.org/courses/open...
trainingportal.linuxfoundation.org/courses/open...

This, I agree with.

Didn’t mean to be reductive. Fantastic post! /o is crazy.

If you see this, post a castle.

youtu.be/qZwr511qGoY

As a Brit living in The Netherlands, I feel conflicting emotions.

If developers focused on optimisation as much as they used to, you would also not have nearly as much (useful) software.

TL;DR: never use /o. Thanks!

Live coding interviews measure stress, not coding skills hadid.dev/posts/living... HN discussion news.ycombinator.com/item?id=4475...

I like to think that people whom I compliment feel about 1/10 as good as I feel when I receive a compliment, and that makes it a very worthwhile investment.

Well, you've definitely succeeded in the interesting department!

This might just be the trade-off of the framework having strong opinions. In general I think that has been a great thing, but it leaves Rubyisms which aren't Railsisms in the shadow.

Very neat work, and quick too!

Screenshot of a part of the Minitest changelog: 5.0.0 / 2013-05-10 Oh god... here we go...

And now onto the other Ruby 2.3 (but Sinatra this time) codebase of the week, and I know I'm in for some pain.

They nailed the zero-uptime upgrade, though.

The other side of this is that `ActiveRecord::Type::Serialized` refuses to serialize default values. Another facet is that MySQL doesn't let you set defaults on TEXT columns.

Hahaha monkey-patches go brrrrrr.

rails/activerecord/lib/active_record/attribute_methods/dirty.rb at 3c194d4a8d585547d1fe45f596d2800c155b1a4c · rails/rails Ruby on Rails. Contribute to rails/rails development by creating an account on GitHub.

TIL that non-nullable serialized attribute columns without a default will break in Rails 4.1 and/or 4.2 because of changes to Dirty.

I didn't need to discover that, but I did. And now, so did you.

github.com/rails/rails/...

If you're feeling down, just remember: you could always be working on a Rails 4.0 / Ruby 2.3 codebase like I am this week.

Not from the Space Invaders prompt, I hope.

So that's what his eyes look like!