This blog has moved to http://blog.michaelgreenly.com
Jun 17, 2014
Jun 17, 2012
The original code I posted was flawed. The gist below is modified and I think would work but it's not as clear as I'd like it to be. I'll follow up on this soon.
I recently released a tiny Gem called JustMaybe. This caused me to do more reading on the subject. I ran across the If you gaze into nil nil gazes also into you post. In the JustMaybe readme I sort of mention this but I wanted to express it more clearly here.
I don't really think using Maybe mixed in with the logic of your application is a good idea.
As an example I think the problem presented in that article could be solved much more clearly with this bit of code. Here's a solution that will never return nil.
My suggestion is that if you find yourself wrestling with possible nil return values . See if you can turn the operation on it's head. Don't ask your object about it's associations. Ask the association about your object. I often find this will clean up the logic.
I did however just release JustMaybe so obviously I think it's useful in some way? For me that's almost strictly in presentation. When you are presenting information you often have to reach deep down into the hierarchy of objects to extract the necessary bits. Interestingly, at presentation, is when I think you should be deciding what to display when information is missing. To me that creates a perfect situation for using the Maybe pattern.
Feb 27, 2012
Here's a micro-nugget. The following Apache config redirects incoming HTTP traffic to the equivalent HTTPS page. Nothing special but I don't spend enough time working on Apache configurations to keep this stuff fresh in my mind so I find it useful to record what I learn in case I need to do it again later.
<virtualhost *:80> RedirectMatch permanent /(.*)$ https://example.com/$1 </virtualhost> <virtualhost *:443> ServerName example.com # config... </virtualhost>
Feb 20, 2012
I had previously made posts about parsing user supplied dates in Ruby
Apparently in Ruby 1.9.3 the Date library was re-implemented in C for performance and of course that broke my extension. I updated it to support Ruby 1.9.3 below
This may not work on Ruby versions prior to 1.9.3 I didn't try it.
I also found the american_date gem which apparently existed before I had originally written my extension and is almost certainly a better choice if you don't need any custom formats.
Feb 6, 2012
I'm really lazy and have started using the exact same ".rvmrc" file for all my Ruby projects....
rvm use @$(basename `pwd`) --create
I'm not sure but I think I first seen this exact format while reading this code https://github.com/dkubb/veritas
Jan 27, 2012
Jan 7, 2012
Until they make the content available when people want to see it on which ever device or service they want to view it they have no footing in the argument against it being a service problem.
There's a ton more material out there but that's a good start if you're new to the topic.
Jan 6, 2012
The example above does return a time value in the current timezone and will work as expected. One big problem with strptime is that it isn't very flexible, the input string must match the provided format string exactly right down the the separator characters and spaces. So this approach can work if your processing the output of a control but tends to fail if you need to process human input.
Another problem I have with the approach above is that it quickly becomes incredibly redundant if you're working with a large number of date/time fields in many different models. To Dry that up a bit I decided to move my specialized processing into a modified version of Date._parse. This means I don't have to litter my controllers with date time parsing code and I have a single entry point to test that all desired formats are supported.
Basically all this is doing is taking the input string and re-arranging the values into an order the original method will understand. The biggest disadvantage to this problem is that it doesn't support per-locale input formats. It guess I'll cross that bridge if I ever get to it.
Assuming your local timezone is not 'UTC' you most likely will want to configure Postgres to use it anyway on your development machine so that your development environment behaves like your production environment. To do this just find the 'timezone=' line in postgresql.conf and set it to 'UTC'.
Jan 4, 2012
I'm in the middle of correcting some date/time handling in a Rails app. One of things that was wrong was the handling of user input date/time fields. Obviously when users provide date/time values they're assuming we understand the information was provided from the perspective of their timezone. Especially when we don't explicitly require them to provide timezone information.
The problem with this is that Ruby's DateTime.parse method always returns UTC based times. You can see this clearly in the example below:
You can see the problem on the 6th line in the example above. Even though the user input "2011/01/01T00:00" when that DateTime instance is converted to localtime the current timezone offset was subtracted. In this case resulting in a time that's 6 hours earlier than desired.
The solution is straight forward of course. You just have to add the inverse of the users timezone offset to the value returned from DateTime.parse as demonstrated below.
On line 4 you can see it's correct even when converted from UTC to local time.
As an alternative you could include the timezone information before parsing it but that's not always easy because you don't necessarily now the format of the user's input.
Of course all of this is generally pretty obvious but I shared just in case it can help some one less familiar with the issues.