<?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 bjeanes</title><link>http://disqus.com/by/bjeanes/</link><description></description><atom:link href="http://disqus.com/bjeanes/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 24 Nov 2023 20:11:20 -0000</lastBuildDate><item><title>Re: How much are electric cars in Australia?</title><link>https://www.whichcar.com.au/advice/electric-car-costs-australia#comment-6330616149</link><description>&lt;p&gt;"every new EV in Australia"&lt;/p&gt;&lt;p&gt;new Hyundai Kona EV isn't even on the page... 😒&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Fri, 24 Nov 2023 20:11:20 -0000</pubDate></item><item><title>Re: Rails Quick Tips - Random Records - The Hashrocket Blog</title><link>http://hashrocket.com/blog/posts/rails-quick-tips-random-records#comment-1071205040</link><description>&lt;p&gt;Excellent points, but it also assumes you have sequential IDs of some kind. This isn't the case if you are using UUIDs for example, but you could always add an incrementing column specifically for supporting the random ordering use case, I suppose.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Sat, 05 Oct 2013 02:19:31 -0000</pubDate></item><item><title>Re: Misunderstanding the Law of Demeter - Dan Manges's Blog</title><link>http://www.dan-manges.com/blog/37#comment-1071203419</link><description>&lt;p&gt;Great article. I'm tempted to say that the final example you can (and possibly should) avoid your view reaching into your domain model without changing your domain model by presenters. Views reaching into your domain model can still lead to some pretty brittle coupling and an element of indirection can help greatly there. Something, somewhere, will have to traverse your domain model and that *IS* OK, which is I think the point you are trying to make anyway, but it's much nicer if that's the only thing it does. Views are already dealing with a lot of responsibilities, so splitting some of those out from the rendering component is a good thing, IMO.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Sat, 05 Oct 2013 02:15:58 -0000</pubDate></item><item><title>Re: ActiveRecord: Enhanced Query Objects</title><link>http://hasghari.github.io/2013/09/15/active-record-enhanced-query-objects.html#comment-1058619930</link><description>&lt;p&gt;Ruby 2.1 fixes this, but any prior version invalidates all method caches (in MRI)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 25 Sep 2013 11:03:39 -0000</pubDate></item><item><title>Re: Rails Quick Tips - Random Records - The Hashrocket Blog</title><link>http://hashrocket.com/blog/posts/rails-quick-tips-random-records#comment-920081087</link><description>&lt;p&gt;This is a good tip, but it is important to note that this *can* be very inefficient, in both MySQL and PostgreSQL. It will require a full table scan and sort so the query time grows with the size of the table instead of being constant. Far better would be to do something like:&lt;/p&gt;&lt;p&gt;    count = User.count&lt;/p&gt;&lt;p&gt;    User.offset("RANDOM()*#{count}").first&lt;/p&gt;&lt;p&gt;If you want N random things, it gets harder to do it efficiently, but for small numbers of things, it will be quicker to execute N queries as per above than do a full table scan+sort, if the table is nontrivially sized.&lt;/p&gt;&lt;p&gt;This post is a decent summary of the options: &lt;a href="http://stackoverflow.com/questions/5297396/quick-random-row-selection-in-postgres" rel="nofollow noopener" target="_blank" title="http://stackoverflow.com/questions/5297396/quick-random-row-selection-in-postgres"&gt;http://stackoverflow.com/qu...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 05 Jun 2013 14:38:35 -0000</pubDate></item><item><title>Re: 2011 Rubyist&amp;#8217;s guide to a Mac OS X development environment</title><link>http://robots.thoughtbot.com/post/8700977975#comment-281688104</link><description>&lt;p&gt;Same here. &amp;lt;3 Babushka for this kind of stuff...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Tue, 09 Aug 2011 22:03:00 -0000</pubDate></item><item><title>Re: http://turriate.com/articles/2011/feb/how-to-generate-signed-rails-session-cookie/</title><link>http://turriate.com/articles/2011/feb/how-to-generate-signed-rails-session-cookie/#comment-143035789</link><description>&lt;p&gt;Would curl work, though? The subsequent requests would still need to&lt;br&gt;be associated with that session so you'd still need to be able to set&lt;br&gt;cookies.&lt;/p&gt;&lt;p&gt;Anyway, nice write up. Another solution I've thought of doing and&lt;br&gt;releasing was to mount an OAuth provider as a rack app during test&lt;br&gt;mode since rack-test sends all requests to your app regardless of the&lt;br&gt;hostname. This would mean you could have the full twitter flow and&lt;br&gt;maintain readable stories. You'd still want at least one test properly&lt;br&gt;communicating with twitter to be sure their process doesn't change, of&lt;br&gt;course ...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Tue, 08 Feb 2011 18:35:10 -0000</pubDate></item><item><title>Re: http://turriate.com/articles/2011/feb/how-to-generate-signed-rails-session-cookie/</title><link>http://turriate.com/articles/2011/feb/how-to-generate-signed-rails-session-cookie/#comment-142977920</link><description>&lt;p&gt;Do all capybara drivers support setting session and/or cookies? Last time I checked they didn't :(&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Tue, 08 Feb 2011 17:38:12 -0000</pubDate></item><item><title>Re: http://til.developingego.com/post/2971548501</title><link>http://til.developingego.com/post/2971548501#comment-139316005</link><description>&lt;p&gt;See the String#succ method (&lt;a href="http://t.co/rVaPW5j)" rel="nofollow noopener" target="_blank" title="http://t.co/rVaPW5j)"&gt;http://t.co/rVaPW5j)&lt;/a&gt; to know why this works :).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Thu, 03 Feb 2011 01:09:26 -0000</pubDate></item><item><title>Re: Chicago&amp;#8217;s Ruby Developer Crisis</title><link>http://nuts.redsquirrel.com/post/2680658687#comment-127200760</link><description>&lt;p&gt;Another thing to consider is: who can we hire to do the things programmers do but don't have to (or don't want to). For instance, too few dev shops hire designers. They can go years convincing themselves they have no need for one, but I am positive once any one of these companies make the leap and get a designer, they can't hold the work back.&lt;/p&gt;&lt;p&gt;At Mocra, we had a designer come to us and say "I love what you guys do and I want to work for you." At first, we told him we didn't have a need, but he insisted that if we just gave him a week we'd change our mind. Within a week, we sometimes wished we had two designers. They make our awesome apps look even more awesome and in the extremely rare case where there isn't client work to work on or improve, they can always maintain or improve the main website, company branding, business cards, or just do general visually-related grunt work that usually gets lumped on developers.&lt;/p&gt;&lt;p&gt;So, everyone who doesn't have a designer, get one. Or three. They are pretty much the best asset you didn't know you needed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Mon, 10 Jan 2011 19:26:57 -0000</pubDate></item><item><title>Re: Chicago&amp;#8217;s Ruby Developer Crisis</title><link>http://nuts.redsquirrel.com/post/2680658687#comment-127159989</link><description>&lt;p&gt;Nailed it. Employers really are competing on quality of work now, because there is way more Ruby work than there are good developers. That means some employers are going to lose. Some of Dave's solutions aim to solve not just getting employees for your own company (Obtiva in this case) but getting enough to meet the demand in general. Training new developers in Rails and its best practices is the primary way that this can happen.&lt;/p&gt;&lt;p&gt;Also, you're completely right that it isn't a Chicago epidemic. In fact, it's not even a USA epidemic. As one of the developers that Dave mentioned are being relocated to Chicago, I can attest that this problem exists even here in Australia. At Mocra, we had the same conversation almost weekly about how to find or create new Ruby talent.&lt;/p&gt;&lt;p&gt;Personally, one of the biggest reasons why there is so much demand, IMO, is that Ruby devs love start ups. We love being part of an exciting and inspiring team that are passionate about their new idea and we jump on board for a year or two trying to realise that dream. Eventually, though, there's a newer and cooler startup and we want to be a part of that too, so we jump ship. This pattern of great developers forming the infrastructure of these start ups on Rails and then jumping ship could be a contributing factor in the demand. These startups and small businesses need Rails developers to stay afloat but might not know how to find them or how to convince them to stay.&lt;/p&gt;&lt;p&gt;It's just a theory, but maybe it holds some weight? What do you guys think about my idea that some of us (to an extent) seed and abandon Rails projects in companies that depend on them?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Mon, 10 Jan 2011 18:57:59 -0000</pubDate></item><item><title>Re: Objective-C Memory Management For Lazy People</title><link>http://interfacelab.com/objective-c-memory-management-for-lazy-people/#comment-109277386</link><description>&lt;p&gt;Thanks. I thought `retain` was missing from Rule #1 as well, but wasn't sure as I'm not an Objective-C developer. Even the examples the author gives show releasing an object that was neither alloced, copied, or instantiated with new. It confused me briefly.&lt;/p&gt;&lt;p&gt;Also, something being easy because you are used to it is not the same thing as something being easy in general. I'm sure manual memory management is a lot easier than most people think, but I also think it's a lot harder than those who do it think...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Thu, 09 Dec 2010 08:08:29 -0000</pubDate></item><item><title>Re: [Web Wednesday] Let&amp;#039;s create a crowd-sourced UK co-working map!</title><link>http://www.freelanceadvisor.co.uk/resources/web-wednesday-lets-create-a-crowd-sourced-uk-co-working-map/#comment-88527492</link><description>&lt;p&gt;Well, at the very least we plan on building an API into our service eventually, so there will definitely be that. :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 20 Oct 2010 11:11:40 -0000</pubDate></item><item><title>Re: [Web Wednesday] Let&amp;#039;s create a crowd-sourced UK co-working map!</title><link>http://www.freelanceadvisor.co.uk/resources/web-wednesday-lets-create-a-crowd-sourced-uk-co-working-map/#comment-88523364</link><description>&lt;p&gt;Everything you see there was built in 48 hours by 4 people (3 of us freelancers/independents, and 1 wannabe). It's written in Ruby on Rails with a dedicated database. Our plans are much more than a simple map with locations but an actual vibrant community where freelancers can meet up at fantastic venues to work together. We plan to make it more about the people than the actual workplaces themselves. Skill exchanges, useful ratings.&lt;/p&gt;&lt;p&gt;We especially care about those fantastic companies that offer up a spare desk or two free of charge to freelancers or small teams trying to get a business off the ground. We think that's an awesome thing for a company to do for our community, and we wanted to help foster that and help the freelancers find those spots.&lt;/p&gt;&lt;p&gt;We've already started on a lot of other great features (like mobile interfaces, iphone app, better booking management for workplace manages, and a distinction between paid and free workplaces for the users)!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 20 Oct 2010 10:55:25 -0000</pubDate></item><item><title>Re: [Web Wednesday] Let&amp;#039;s create a crowd-sourced UK co-working map!</title><link>http://www.freelanceadvisor.co.uk/resources/web-wednesday-lets-create-a-crowd-sourced-uk-co-working-map/#comment-88519662</link><description>&lt;p&gt;We started doing this exact thing this weekend, except globally! Why not join the effort and help build a united community of passionate coworkers and nomadic freelancers.&lt;/p&gt;&lt;p&gt;&lt;a href="http://desksnear.me" rel="nofollow noopener" target="_blank" title="http://desksnear.me"&gt;http://desksnear.me&lt;/a&gt; has been live for only ~3 days and we've already had 70+ workplaces listing themselves without us advertising. We're been highlighted by freelanceswitch, we made it to the #3 on hackernews website and have had an overwhelming amount of visits and page views this week.&lt;/p&gt;&lt;p&gt;I think we (as a community) have a real chance of making something special and we'd love all the help we can get.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 20 Oct 2010 10:40:01 -0000</pubDate></item><item><title>Re: http://rubyquicktips.tumblr.com/post/831412465</title><link>http://rubyquicktips.tumblr.com/post/831412465#comment-63438191</link><description>&lt;p&gt;I'd go a step further and make it print out the appropriate `caller` entry to show the file and line number, then call super. That way you don't disrupt the tests running or have to restart the tests if the raise aborts the tests for some reason.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Tue, 20 Jul 2010 18:43:26 -0000</pubDate></item><item><title>Re: Sailing down the Hudson with RVM</title><link>http://robots.thoughtbot.com/post/712609699#comment-61058808</link><description>&lt;p&gt;afaict CCMenu won't work with Hudson when you need to authenticate.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Thu, 08 Jul 2010 02:53:58 -0000</pubDate></item><item><title>Re: Emphasized Insanity: A Ruby script to stay productive</title><link>http://blog.eizesus.com/2009/10/a-ruby-script-to-stay-productive#comment-20095832</link><description>&lt;p&gt;good to hear. thanks again for the mention :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 14 Oct 2009 23:52:28 -0000</pubDate></item><item><title>Re: Emphasized Insanity: A Ruby script to stay productive</title><link>http://blog.eizesus.com/2009/10/a-ruby-script-to-stay-productive#comment-20095623</link><description>&lt;p&gt;i'd test your script though, because I did that from memory&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 14 Oct 2009 23:46:22 -0000</pubDate></item><item><title>Re: Emphasized Insanity: A Ruby script to stay productive</title><link>http://blog.eizesus.com/2009/10/a-ruby-script-to-stay-productive#comment-20094635</link><description>&lt;p&gt;Hey thanks for the ghost mention, I'm glad you find it useful.&lt;/p&gt;&lt;p&gt;Pro-tip, you don't need to call out to the binary to add new hosts or delete them. The command line tool is only a wrapper around the library which you can use directly:&lt;/p&gt;&lt;p&gt;require 'ghost'&lt;/p&gt;&lt;p&gt;Host.add('host.local', '127.0.0.1')&lt;br&gt;Host.delete('host.local)&lt;br&gt;Host.list # displays existing hosts&lt;/p&gt;&lt;p&gt;You can see the source of the ghost command here and how it uses it: &lt;a href="http://github.com/bjeanes/ghost/blob/master/bin/ghost" rel="nofollow noopener" target="_blank" title="http://github.com/bjeanes/ghost/blob/master/bin/ghost"&gt;http://github.com/bjeanes/g...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 14 Oct 2009 23:20:50 -0000</pubDate></item><item><title>Re: Active Record Association Methods | hughevans.net</title><link>http://hughevans.net/2009/03/06/active-record-association-methods#comment-12242854</link><description>&lt;p&gt;Remember you cal also put those methods in a module and include it like:&lt;/p&gt;&lt;p&gt;has_many :items, :dependent =&amp;gt; :destroy, :extend =&amp;gt; AssociationMethodsModule&lt;/p&gt;&lt;p&gt;It's a much nicer API if you have a big method or lots of methods to add to an association&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Tue, 07 Jul 2009 02:43:29 -0000</pubDate></item><item><title>Re: Safe code....</title><link>http://blog.iphone-dev.org/post/42583223#comment-926618</link><description>&lt;p&gt;yeah .... what bricked iphones?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Thu, 17 Jul 2008 18:26:04 -0000</pubDate></item><item><title>Re: I am rice</title><link>http://iamrice.org/post/33260704#comment-396299</link><description>&lt;p&gt;Haha that's exactly what I've been doing! Both games == awesome++&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bjeanes</dc:creator><pubDate>Wed, 30 Apr 2008 04:44:16 -0000</pubDate></item></channel></rss>