<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for peteonrails</title><link>http://disqus.com/by/peteonrails/</link><description></description><atom:link href="http://disqus.com/peteonrails/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 30 Mar 2018 11:00:47 -0000</lastBuildDate><item><title>Re: Alpina&amp;#039;s Startimer Pilot is Simple, Yet Elegant</title><link>https://www.flyingmag.com/alpina-startimer-pilot-reviewed#comment-3831581019</link><description>&lt;p&gt;I saw this advertisement disguised as an article in the magazine a couple of days ago. You  describe a watch "designed with aviators firmly  in mind" and then fail to mention whether it has a GMT hand or a timer, or really any other feature that aviators find important.&lt;/p&gt;&lt;p&gt;Yet you are really excited that it is water resistant to 330 feet (you know, the depth at which we fly our airplanes).&lt;/p&gt;&lt;p&gt;It makes me wonder whether the Flying Staff who claims the byline really did write the copy for this advert, or whether the manufacturer provided the words you printed. If it's the former, you've done a bad job of evaluating a new product, and I am surprised. If the latter, you ought to at least mark the page as an advertisement.&lt;/p&gt;&lt;p&gt;Either way, I'd prefer to see an honest, fair evaluation of a new and expensive aviation watch. Do you really think this thing is great for pilots? Why or why not?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Fri, 30 Mar 2018 11:00:47 -0000</pubDate></item><item><title>Re: Exclusive: FAA probes Air Canada near-miss at SFO</title><link>http://www.mercurynews.com?p=4663515&amp;preview_id=4663515#comment-3411757420</link><description>&lt;p&gt;28-R is not the runway on the left. It's the runway on the right. The taxiway is to its right. Coming from the other direction, that runway is Runway 10-L.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 11 Jul 2017 15:37:12 -0000</pubDate></item><item><title>Re: Exclusive: FAA probes Air Canada near-miss at SFO</title><link>http://www.mercurynews.com?p=4663515&amp;preview_id=4663515#comment-3411752733</link><description>&lt;p&gt;Taxiway lights are blue. Runway lights are white and have REIL indicators. Things happen, but it is not hard to tell the difference.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 11 Jul 2017 15:34:31 -0000</pubDate></item><item><title>Re: Supervisor threatens to hang worker for drinking from 'white people' fountain </title><link>http://www.cnn.com/2014/06/05/us/memphis-supervisor-racist-audio/index.html#comment-1420744414</link><description>&lt;p&gt;"So they are to blame since they didn't know about it?"&lt;/p&gt;&lt;p&gt;Yes.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Thu, 05 Jun 2014 08:01:12 -0000</pubDate></item><item><title>Re: Supervisor threatens to hang worker for drinking from 'white people' fountain </title><link>http://www.cnn.com/2014/06/05/us/memphis-supervisor-racist-audio/index.html#comment-1420699983</link><description>&lt;p&gt;"Federal Compress very much regrets that the allegations were not reported to it when the first incident is claimed to have occurred."&lt;/p&gt;&lt;p&gt;It's Federal Compress' fault. Nobody else's. It's not hard to see how a company that fails to accept responsibility and apologize directly, choosing instead to deflect blame onto their customers, might harbor a culture that allows this kind of behavior to develop in the first place.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Thu, 05 Jun 2014 07:14:51 -0000</pubDate></item><item><title>Re: Open WhisperSystems &gt;&gt; Blog &gt;&gt; Open Whisper Systems is coming to iPhone!</title><link>https://whispersystems.org/blog/iphone-rsn/#comment-1233559817</link><description>&lt;p&gt;I look forward to an iOS release. I also get it that you're building a free, open source product and snarky nagging about the delivery date only serves to make you less excited about building it. :)&lt;/p&gt;&lt;p&gt;Good work, keep it up!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Thu, 06 Feb 2014 11:43:51 -0000</pubDate></item><item><title>Re: Lessons Learned: The First Two Years of Running a Software Consultancy</title><link>http://reefpoints.dockyard.com/2013/12/22/lessons-learned-two-years-of-running-a-dockyard.html#comment-1176636340</link><description>&lt;p&gt;You wouldn't have gotten away with leaving it out! And it's an important part of company lore now.&lt;/p&gt;&lt;p&gt;I enjoyed last year's retrospective and this one. I look forward to the next one.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Wed, 25 Dec 2013 12:24:38 -0000</pubDate></item><item><title>Re: Littlelines | Matt Sears | A Guide for Writing Maintainable Rails Tests</title><link>http://www.littlelines.com/blog/2013/12/17/a-guide-for-writing-maintainable-rails-tests/#comment-1174767143</link><description>&lt;p&gt;Heya Dan: I agree that you often want to test that a user has orders: see my comment above. What do you think about scoping down the tested interface to only those associative methods that you actually use? eg:&lt;/p&gt;&lt;p&gt;expect (user).to have_many(:orders) =&amp;gt; expect(user).to respond_to?(:orders)&lt;/p&gt;&lt;p&gt;For most cases I think that's a good test that allows for refactoring, though for more tightly coupled relationships the has_many() matcher may be appropriate. I think there's a tipping point in there somewhere.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Mon, 23 Dec 2013 11:46:15 -0000</pubDate></item><item><title>Re: Littlelines | Matt Sears | A Guide for Writing Maintainable Rails Tests</title><link>http://www.littlelines.com/blog/2013/12/17/a-guide-for-writing-maintainable-rails-tests/#comment-1174764034</link><description>&lt;p&gt;Good points, all.&lt;/p&gt;&lt;p&gt;I agree that testing it { should have_many(:orders) } may be the wrong test. What you're really interested in is testing that you can ask a User for orders, and it gives you back a set of them. To Dan's point, { should have_many(:orders) } is a shorthand way to check for all of the build_* and other associative methods. Usually, though, you only want to test a subset of them, which would allow a refactor later. 90% of the time, what you really want is: { should respond_to?(:orders) }&lt;/p&gt;&lt;p&gt;As far as mocks and stubs go: I have found little utility in the user.any_instance.should_receive(:orders).and_return(fake_orders) expectation syntax. Every time I have written one of those, it has broken later for no good reason. Those kinds of false negatives discourage good testing and you are right to call that out. FactoryGirl has been a big win for many developers recovering from over-mocking and over-stubbing.&lt;/p&gt;&lt;p&gt;In my work at FasterAgile, we tell our clients that 100% test coverage is not an unreachable or unreasonable expectation. I have noticed that developers who are new to TDD often have trouble grokking what to test in the first place. Some will structure unit tests like acceptance tests. Some can't do an acceptance test without tons of setup and mocking. Many will give up and just test manually. In all cases, writing our requirements as pending tests has been the key to drive behavior change.&lt;/p&gt;&lt;p&gt;Thanks for the article!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Mon, 23 Dec 2013 11:43:07 -0000</pubDate></item><item><title>Re: Andrew Palmer Sends Jaws II (5.15a)</title><link>http://www.climberism.com/andrew-palmer-sends-jaws-ii-5-15a/#comment-1092655100</link><description>&lt;p&gt;That's quite an accomplishment, congratulations! I'm kicking myself for being to lazy to hike up the hill on Sunday. :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 22 Oct 2013 16:24:31 -0000</pubDate></item><item><title>Re: What A Time To Be 17 Years Old</title><link>http://www.rooshv.com/what-a-time-to-be-17-years-old#comment-1090711178</link><description>&lt;p&gt;Guide him into a field where he can start a business that he will be successful with. Plumbing is fine, but not if you're going to be a plumber for 40 years. Own the plumbing company. Working your ass off so that someone else can get all the money is still a kind of slavery.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Mon, 21 Oct 2013 09:38:47 -0000</pubDate></item><item><title>Re: Goodbye TextMate | Pete On Rails</title><link>http://blog.peteonrails.com/2010/03/goodbye-textmate/#comment-1026421108</link><description>&lt;p&gt;Hi Kevin. This is a really really old article. Today, I use Sublime Text on my linux machine. Give it a go!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Mon, 02 Sep 2013 10:28:11 -0000</pubDate></item><item><title>Re: Goodbye TextMate | Pete On Rails</title><link>http://blog.peteonrails.com/2010/03/goodbye-textmate/#comment-916932105</link><description>&lt;p&gt;It's a pretty old article, so I'd argue that it's no longer timely. However, the folks who read my RSS feed were interested at the time. I'm sorry that you didn't like the article.&lt;/p&gt;&lt;p&gt;In the future, please remember Rule #1: Don't Be A Jerk.&lt;/p&gt;&lt;p&gt;Thanks,&lt;/p&gt;&lt;p&gt;--Pete&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Sun, 02 Jun 2013 16:05:19 -0000</pubDate></item><item><title>Re: Herb Conn Dies at 91</title><link>http://www.climbing.com/news/hotflashes/herb_conn_dies_at_91/#comment-435801138</link><description>&lt;p&gt;Herb and Jan put up many of the classic routes that I started climbing on about 20 years ago. Though it's of an easy grade, Conn's East at Seneca Rocks is one of the most wildly exposed pitches I've ever set foot on. I'm already planning my trip back to WV to climb it again in his memory. You'll be missed, Herb. Thank you for a lifetime of exploration, and for sharing it with the rest of us.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Fri, 10 Feb 2012 20:10:12 -0000</pubDate></item><item><title>Re: The Revenge of Inigo Montoya</title><link>http://blog.peteonrails.com/?p=238#comment-259622674</link><description>&lt;p&gt;I don't usually feed the trolls Derek, especially not on something I &lt;br&gt;wrote over a year ago. But in this case, I think a response is &lt;br&gt;warranted.&lt;/p&gt;&lt;p&gt;You're conflating a bunch of issues in your argument, but here's my best go:&lt;/p&gt;&lt;p&gt;1. Yes, I read all of the code behind ci_auth. The :false symbol may not&lt;br&gt; have been evaluated anywhere for its truthiness in the library itself, &lt;br&gt;but I assure you, it caused a bug that I spent a long time tracking &lt;br&gt;down.&lt;/p&gt;&lt;p&gt;2. Yes. I understood the requirements of authentication at said company.&lt;br&gt; I stand by my assertion that rolling your own security / authentication&lt;br&gt; library was a mistake.&lt;/p&gt;&lt;p&gt;3. There's a reason there are no tests in The Mod. You'll have to ask &lt;br&gt;David why, though. I'm really sorry that you're stuck maintaining that &lt;br&gt;code base for more reasons than the fact that it's got poor unit test &lt;br&gt;coverage.&lt;/p&gt;&lt;p&gt;In my original post, Derek, I didn't rag on your code. I didn't mention &lt;br&gt;your name, your employer, the project in question, or even say it was a &lt;br&gt;huge steaming pile of shit. If you think The Mod codebase sucks, then &lt;br&gt;you should make the case to your bosses for a rewrite, rather than rag &lt;br&gt;on me for making the best of a shitty situation with your stakeholders.&lt;/p&gt;&lt;p&gt;Just don't put "if case == :false" in there anywhere and I'll be happy. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Thu, 21 Jul 2011 09:57:42 -0000</pubDate></item><item><title>Re: Goodbye TextMate</title><link>http://blog.peteonrails.com/?p=217#comment-174028737</link><description>&lt;p&gt;It's not THAT outrageous. :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 29 Mar 2011 09:11:25 -0000</pubDate></item><item><title>Re: Goodbye TextMate</title><link>http://blog.peteonrails.com/?p=217#comment-174028529</link><description>&lt;p&gt;No doubt! I ended up using RedCar. I found it to be a nice happy medium.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 29 Mar 2011 09:11:04 -0000</pubDate></item><item><title>Re: Goodbye TextMate</title><link>http://blog.peteonrails.com/?p=217#comment-174028121</link><description>&lt;p&gt;I used to LOVE emacs. Over time, I migrated away from it. I can totally understand the cult-of-emacs crowd's love of the most long-running successful editor in the universe, but I never stay with it for long. I'm the same way with vi, vim, and macvim. I get it, but I don't get it. :) &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 29 Mar 2011 09:10:26 -0000</pubDate></item><item><title>Re: Goodbye TextMate</title><link>http://blog.peteonrails.com/?p=217#comment-174026746</link><description>&lt;p&gt;Thanks for writing, Adrian. In all candor, my switch to NetBeans was fairly short-lived. I didn't last the whole year. Based on Tom's feedback 6 months ago, I started using Redcar, which is everything I like about TextMate, and nothing that I hate about TextMate, plus it's free.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 29 Mar 2011 09:08:19 -0000</pubDate></item><item><title>Re: Goodbye TextMate</title><link>http://blog.peteonrails.com/?p=217#comment-81548457</link><description>&lt;p&gt;Thanks Tom! Haven't tried it, but I'm giving it a whirl now. I appreciate the feedback. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 28 Sep 2010 09:19:09 -0000</pubDate></item><item><title>Re: Why I Don't Like Stock Buybacks</title><link>http://avc.com/2010/06/why-i-dont-like-stock-buybacks/#comment-58608503</link><description>&lt;p&gt;I always have viewed a stock buyback as a signal that the company it under-performing in the innovation department.&lt;/p&gt;&lt;p&gt;That said, I think it is a responsible thing to do if management can't adequately invest my capital in innovative projects. Giving me my money back is a good thing.&lt;/p&gt;&lt;p&gt;The different take I have is that I'd take the money and run: to invest it in a company that needed the cash so that they could change the world. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Fri, 25 Jun 2010 11:15:42 -0000</pubDate></item><item><title>Re: VoteFu is now available on GemCutter</title><link>http://blog.peteonrails.com/?p=191#comment-54361350</link><description>&lt;p&gt;I am glad you got it working, but your original point about an update to the docs being required still stands. Thanks for the analysis of what went wrong: it's either a bug I need to fix, or an incompatibility that I need to document.&lt;/p&gt;&lt;p&gt;Take care!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Thu, 03 Jun 2010 20:38:28 -0000</pubDate></item><item><title>Re: VoteFu is now available on GemCutter</title><link>http://blog.peteonrails.com/?p=191#comment-53413344</link><description>&lt;p&gt;Yes, I concur. The documentation is currently very bad. It got outdated over time, and I've put off updating it until I can get the new version out the door.&lt;/p&gt;&lt;p&gt;If you send me a gist or snippet with your migration and your model I can help you get it working. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 01 Jun 2010 15:29:35 -0000</pubDate></item><item><title>Re: The Revenge of Inigo Montoya</title><link>http://blog.peteonrails.com/?p=238#comment-52008381</link><description>&lt;p&gt;Other implementations of The Inigo Montoya Attack include cargo-culting things like the bang-bang boolean trick when you don't really need it:&lt;/p&gt;&lt;p&gt;val = !!false&lt;/p&gt;&lt;p&gt;Why would you do that? Why?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 25 May 2010 16:05:09 -0000</pubDate></item><item><title>Re: The Revenge of Inigo Montoya</title><link>http://blog.peteonrails.com/?p=238#comment-52007467</link><description>&lt;p&gt;I have seen this in exactly one codebase. To protect the innocent, I will not say whose codebase it was, but I will tell you that our friend in common Kate probably knows why the symbol :false is used in place of 'false'.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">peteonrails</dc:creator><pubDate>Tue, 25 May 2010 16:00:26 -0000</pubDate></item></channel></rss>