tcopeland

11 ms·

61.
by tcopeland 10y ago
Ah ha! It was a Ruby bug... longer writeup here: http://thomasleecopeland.com/2016/06/26/basicobject-is-a-ran...
62.
by tcopeland 10y ago
Yeah sounds like in the same ballpark. David Stostik did a nice writeup of the oddities of ActiveSupport::Duration 4.1 here http://www.bnjs.co/2015/01/14/rails-date-class-durations-and... . I'm surprised
63.
by tcopeland 10y ago
Yup that's the code that I'm wondering about. The case I ran into was in a Rails 4.1 app where ActiveSupport::Duration (which subclassed BasicObject) was used like this: "rand(10.minutes)". That raised an exception in 2
64.
by tcopeland 10y ago
That's exactly right; but that's happening because vm_respond_to is returning true on a nil method entry. It's a puzzler...
65.
by tcopeland 10y ago
But that's just it; I would have thought the NoMethodError would have been around the missing "respond_to?" - like it was in 2.2.3 - not around a missing "begin".
66.
by tcopeland 10y ago
I am still surprised by this behavior change from 2.2.3 to 2.3.0 (and also present in 2.3.1 and 2.4.0): $ ./ruby -e "puts RUBY_DESCRIPTION ; rand(BasicObject.new)" ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin
67.
How to make your next Ruby on Rails upgrade easier(thomasleecopeland.com)
1 points by tcopeland 11y ago|0 comments
68.
by tcopeland 11y ago
I commute from Herndon VA into DC a couple times a week. It takes about 1:15 each way. But I ride the Loudon Country transit bus, which has decent-size seats and aisles. So as soon as I get on the bus, I pop open my laptop and work on wha
69.
by tcopeland 11y ago
The funny thing is that that is as old as the hills - that's practically the plot of the first couple chapters of Gogol's "Dead Souls".
70.
by tcopeland 11y ago
That sounds a little like Mark Eberhart's "Why Things Break", where he talks about a company made a contact lens product out of materials similar to Corelle. One product was almost ready to be put on the market when they rea
71.
by tcopeland 11y ago
Remind me of this Slashdot comment about killing the goose that laid the golden eggs: http://news.slashdot.org/comments.pl?sid=7754987&cid=5019893... Perhaps GitHub will be able to resist "change for change's
72.
by tcopeland 11y ago
Here's a longer article ( http://codon.com/consider-static-typing ) with more background / history about static typing and Ruby. This topic has been knocked around in Ruby-land for a while; I remember seeing Michael
73.
by tcopeland 11y ago
> the incremental improvements have been increasing at a rate of knots and folks are beginning to notice the positive effects Right on. I see this at $DAY_JOB too; after a certain amount of cleanup and dead code deletion and whatnot sud
74.
by tcopeland 11y ago
> Technical debt will be incurred, if you like it or not. Right on. I've seen discussions about feature toggles which suggested not using them because they led to an explosion of code paths. But that won't happen if you dele
75.
by tcopeland 11y ago
I think that's not quite the full story; my site cross references a bunch of lists and allows you to see which books were on (for example) both the Army and Navy reading lists, shows past revisions, allows you to keep track of what y
76.
Sunday afternoon reading – CIA reading list (2011)(militaryprofessionalreadinglists.com)
3 points by tcopeland 11y ago|2 comments
77.
by tcopeland 11y ago
That is a fantastic book indeed. It's on the Combat Studies Institute reading list, and rightly so.
78.
by tcopeland 11y ago
Was it the Robert Coram book ( https://militaryprofessionalreadinglists.com/books/665-boyd-... )? That book made it into four different reading lists from various branches of the military (USMC, USAF, Army, and a chair o
79.
by tcopeland 11y ago
There are a bunch of reports of maritime casualties here: http://emsa.europa.eu/marine-casualties-a-incidents.html Grim reading, but gives you a feel for what can go wrong.
80.
by tcopeland 11y ago
That sounds like a dicey business for sure. Depending on the vessel it can take some time and effort to fire up the engines and get underway, especially if it's been sitting for a while. Not to mention all the stuff that can go wrong
81.
Finding bugs with HTTP verb and response code mismatches(thomasleecopeland.com)
2 points by tcopeland 11y ago|0 comments
82.
by tcopeland 11y ago
Not free, but an excellent book along the same lines, is John Levine's "Linkers and Loaders": http://www.amazon.com/Linkers-Kaufmann-Software-Engineering-... He's been the moderator of comp.compilers sin
83.
Picking the right data structure(thomasleecopeland.com)
3 points by tcopeland 11y ago|0 comments
84.
by tcopeland 11y ago
It was pretty wild being underway on the west coast of the US and seeing a huge smear appear on the radar as a container ship swept by. If we were going north and they were going south the relative speed was really something. And the CPA
85.
by tcopeland 11y ago
I just read Catch-22 (for the first time) because it was on the USMA reading list. I soldiered through it... but... meh.
86.
by tcopeland 11y ago
I started the site about 8 years ago because 1) these lists have lots of great selections that you might not come across otherwise (e.g., "The Cruel Sea" by Nicholas Monsarrat) and 2) .mil web sites tend to get reorganized regular
87.
U.S. Army Engineer School Commandant’s Reading List(militaryprofessionalreadinglists.com)
84 points by tcopeland 11y ago|23 comments
88.
Some lessons learned using the Google Directory SDK Ruby client(thomasleecopeland.com)
1 points by tcopeland 11y ago|0 comments
89.
by tcopeland 12y ago
Yup. And part of leadership is handing over the reins cleanly once you're no longer engaged in a project. By "cleanly" I mean removing your own admin access, no longer merging patches once you're not really checking the
90.
Ruby String API use and misuse(thomasleecopeland.com)
3 points by tcopeland 12y ago|0 comments

More ›