<?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 topfunky</title><link>http://disqus.com/by/topfunky/</link><description></description><atom:link href="http://disqus.com/topfunky/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 26 May 2017 00:20:40 -0000</lastBuildDate><item><title>Re: Farer Introduces 3 New Mechanical GMTs</title><link>http://wornandwound.com/farer-introduces-3-new-mechanical-gmts/#comment-3325317688</link><description>&lt;p&gt;A prescient line from this very site's review of the quartz Barnato last year: "...had it been a mechanical GMT and cost $1200 – 1500 (and had a sapphire) the watch would still be very compelling..."&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 26 May 2017 00:20:40 -0000</pubDate></item><item><title>Re: Hands-on with The Daily by Richardt Mejer</title><link>http://wornandwound.com/review/hands-daily-richardt-mejer/#comment-3325270340</link><description>&lt;p&gt;There's also a white model and a black model for more subdued colorways.&lt;/p&gt;&lt;p&gt;I just received the white model and it's very well designed and cleanly executed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Thu, 25 May 2017 23:28:35 -0000</pubDate></item><item><title>Re: Abstract Art With Sass - Code School Blog</title><link>https://www.codeschool.com/blog/2015/11/06/abstract-art-with-sass/#comment-2346353105</link><description>&lt;p&gt;Very cool! I did something similar with a ring of circles. You could click one to move it to the center.&lt;/p&gt;&lt;p&gt;And a bit of `filter: blur(5px)` on the particle adds a cool effect.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 06 Nov 2015 14:51:56 -0000</pubDate></item><item><title>Re: qc: Quick calculator | Daniel Corin</title><link>http://danielcorin.github.io/blog/2013/07/23/qc/#comment-973783643</link><description>&lt;p&gt;Even simpler, just use a bash function:&lt;/p&gt;&lt;p&gt;    function qc() { python -c "print $*" }&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Tue, 23 Jul 2013 15:45:39 -0000</pubDate></item><item><title>Re: How to create compelling technical screencasts</title><link>http://www.backbonerails.com/blog/how-to-create-compelling-technical-screencasts#comment-919179632</link><description>&lt;p&gt;Spot on! We blogged (more briefly) about how to write technical content for developers: &lt;a href="https://peepcode.com/blog/2013/teaching-developers" rel="nofollow noopener" target="_blank" title="https://peepcode.com/blog/2013/teaching-developers"&gt;https://peepcode.com/blog/2...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Tue, 04 Jun 2013 18:56:06 -0000</pubDate></item><item><title>Re: A Week with Elixir</title><link>https://joearms.github.io/published/2013-05-31-a-week-with-elixir.html#comment-915298333</link><description>&lt;p&gt;Three weeks ago we recorded a two hour intro video to Elixir taught by none other than it's creator José Valim. We'll be publishing it in June at &lt;a href="https://peepcode.com" rel="nofollow noopener" target="_blank" title="https://peepcode.com"&gt;https://peepcode.com&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I'm glad to send you a draft if you're interested, Joe. Email boss@topfunky.com&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 31 May 2013 14:56:44 -0000</pubDate></item><item><title>Re: Finnovation™ brings you a heap of new features</title><link>https://blog.bitbucket.org/2013/04/02/finnovation-brings-you-a-heap-of-new-features/#comment-878049006</link><description>&lt;p&gt;Does Finnovation week happen in Finland?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Sat, 27 Apr 2013 15:48:03 -0000</pubDate></item><item><title>Re: Really Simple Social Syndication</title><link>http://smus.com/really-simple-social-syndication/#comment-829599481</link><description>&lt;p&gt;Exactly!&lt;/p&gt;&lt;p&gt;I built something like that for myself that I've been using every week for the past few years (before Flipboard and the like). It catalogs links mentioned by the people I follow on Twitter and shows me a report.&lt;/p&gt;&lt;p&gt;&lt;a href="http://news.peepcode.com/" rel="nofollow noopener" target="_blank" title="http://news.peepcode.com/"&gt;http://news.peepcode.com/&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Thu, 14 Mar 2013 19:34:22 -0000</pubDate></item><item><title>Re: Cielo and Chris King</title><link>https://theradavist.com/2013/02/2013-nahbs-cielo-and-chris-king/#comment-817892618</link><description>&lt;p&gt;It looks like radial lacing on the front wheel of the CX bike. But I thought King hubs disallow radial lacing?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Sun, 03 Mar 2013 01:17:04 -0000</pubDate></item><item><title>Re: 2013 NAHBS: Moots Trail Clearer</title><link>https://theradavist.com/2013/02/2013-nahbs-moots-trail-clearer/#comment-817868744</link><description>&lt;p&gt;And a $250 Shadow Plus rear derailleur.&lt;/p&gt;&lt;p&gt;At least there will be no chain slap when slogging your chainsaw and 6-pack up the trail.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Sat, 02 Mar 2013 23:54:05 -0000</pubDate></item><item><title>Re: Shipping a Conference &amp;#8211; CascadiaJS</title><link>http://www.twilio.com/blog/2012/11/shipping-a-conference-cascadiajs.html#comment-711141138</link><description>&lt;p&gt;It was a fantastic conference. I loved the customized sweatshirts with each person's name on the sleeve. Not just the speakers, either. Everyone!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Thu, 15 Nov 2012 13:43:55 -0000</pubDate></item><item><title>Re: Web and mobile consultancy specializing in Ruby on Rails ~ DockYard</title><link>http://reefpoints.dockyard.com/ruby/2012/02/14/love-your-lib-directory.html#comment-709304146</link><description>&lt;p&gt;The same care that you take to organize your "lib" directory should be used when naming files. For example, "haml/filters/handlebars.rb" instead of the generic "custom_filters.rb".&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Tue, 13 Nov 2012 14:09:54 -0000</pubDate></item><item><title>Re: MOSX Tumblelog - Final Cut Pro X: What I Learned</title><link>http://mosx.tumblr.com/post/31530959779#comment-650719239</link><description>&lt;p&gt;After 5 years on Final Cut, I switched to Premiere Pro. No software is perfect, but it solved so many problems that I had with Final Cut 7 and X.&lt;/p&gt;&lt;p&gt;You can work at any resolution. Adobe Media Encoder is much more reliable than Apple Compressor and Queue Master. Premiere Pro works great with 80 GB source files, where Final Cut would beachball again and again. And After Effects is one of my favorite programs of all time. It's efficient, scriptable, and the timeline makes much more sense than Motion. It's easy to store Premiere Pro project files in Git.&lt;/p&gt;&lt;p&gt;It's great to hear that Final Cut X is working for you, but I would have saved myself so much trouble if I had abandoned Final Cut years ago. I'm so glad I finally did.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 14 Sep 2012 16:25:07 -0000</pubDate></item><item><title>Re: Why Documentary at Rubyconf 2012, Denver</title><link>http://www.akitaonrails.com/2012/09/03/why-documentary-at-rubyconf-2012-denver#comment-642104752</link><description>&lt;p&gt;I had a similar experience trying to interview why for the Ruby on Rails Podcast.&lt;/p&gt;&lt;p&gt;He was very interested in doing the interview, and I saw him in person several times. We even talked about how we would do the interview. But somehow, it never happened.&lt;/p&gt;&lt;p&gt;Right now I'm on a bus, riding to downtown Seattle where I'll record a few interviews for the documentary.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Thu, 06 Sep 2012 12:13:32 -0000</pubDate></item><item><title>Re: Learn Meteor Fundamentals and Best Practices</title><link>http://andrewscala.com/meteor/#comment-600087995</link><description>&lt;p&gt;It's painful that it uses underscores in variable and function names. All modern JavaScript uses camel case.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 27 Jul 2012 17:06:41 -0000</pubDate></item><item><title>Re: http://garrettdimon.com/post/27002421078</title><link>http://garrettdimon.com/post/27002421078#comment-584559121</link><description>&lt;p&gt;I definitely agree about the co-founder issue.&lt;/p&gt;&lt;p&gt;I hired my first full-time employee about a year and a half ago. The business has boomed since then and I'm much happier working in person with someone every day. Entire swaths of problems disappear when you can talk to someone technical instead of exclusively mulling around issues in your head.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Wed, 11 Jul 2012 17:41:02 -0000</pubDate></item><item><title>Re: Never fix a bug twice</title><link>https://lukeplant.me.uk/blog/posts/never-fix-a-bug-twice/#comment-579153125</link><description>&lt;p&gt;Brilliant and practical.&lt;/p&gt;&lt;p&gt;The trouble with tests is that developers think they have covered all the possible cases as long as they have written at least one positive and one negative test for every method.&lt;/p&gt;&lt;p&gt;Your strategy is useful for getting beyond simple unit testing to consider the whole system (language, framework, and implementation).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 06 Jul 2012 20:40:44 -0000</pubDate></item><item><title>Re: Tutorial: Build Reddit in Sinatra</title><link>http://www.drurly.com/blog/2012/06/05/build-reddit-in-sinatra/#comment-570533493</link><description>&lt;p&gt;reddit.rb line 52: So I can POST to /:id/vote/1000000 and add a million points to an article?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Thu, 28 Jun 2012 12:17:54 -0000</pubDate></item><item><title>Re: Crash Course: Design for Startups — PaulStamatiou.com</title><link>http://paulstamatiou.com/startup-web-design-ux-crash-course#comment-567967915</link><description>&lt;p&gt;I recorded a 90 minute (commercial) video with GitHub designer Kyle Neath that many people have found useful. It's cool to see how he solves UI problems without a ton of in-your-face design, but just simple, straightforward UI elements:&lt;/p&gt;&lt;p&gt;&lt;a href="https://peepcode.com/products/play-by-play-kneath" rel="nofollow noopener" target="_blank" title="https://peepcode.com/products/play-by-play-kneath"&gt;https://peepcode.com/produc...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Tue, 26 Jun 2012 18:12:56 -0000</pubDate></item><item><title>Re: Rails 4.0 Sneak Peek: Queueing</title><link>http://reefpoints.dockyard.com/ruby/2012/06/25/rails-4-sneak-peek-queueing.html#comment-566387228</link><description>&lt;p&gt;At first the syntax seemed too verbose to me. Calling "new" when Resque just passes a whole object? But I guess that's a chance for the app to send arguments (such as a user ID to operate on).&lt;/p&gt;&lt;p&gt;But then it gets interesting. The only time I switched queue systems was when I went from Beanstalk to Resque. I still think Beanstalk is a better queue: time-delayed jobs, better retry, etc. The major problem I had was removing arguments to Beanstalk features that weren't in Resque's API.&lt;/p&gt;&lt;p&gt;Does this API help? It doesn't. If you switch to a queue that has different features, you'll still need to edit your calls to your queue object's "new" method. It seems to mostly help only if you are switching to a queue with the same feature set as the one you are currently using. And if so, why switch?&lt;/p&gt;&lt;p&gt;The real benefit seems to be that Rails can make use of a queue internally. And I think that's a good thing.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Sun, 24 Jun 2012 23:45:48 -0000</pubDate></item><item><title>Re: RSpec's New Expectation Syntax</title><link>http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax#comment-558875894</link><description>&lt;p&gt;To be or to not be.&lt;/p&gt;&lt;p&gt;I get it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 15 Jun 2012 18:26:10 -0000</pubDate></item><item><title>Re: RSpec's New Expectation Syntax</title><link>http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax#comment-558865637</link><description>&lt;p&gt;To me, "to_not" reads better than "not_to". &lt;/p&gt;&lt;p&gt;For example, this reads more naturally:   &lt;/p&gt;&lt;p&gt;    expect(donut).to_not be :tasty&lt;/p&gt;&lt;p&gt;This seems awkward:&lt;/p&gt;&lt;p&gt;    expect(donut).not_to be :tasty&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Fri, 15 Jun 2012 18:10:14 -0000</pubDate></item><item><title>Re: Veritabill: Predictive Time Tracking in Ruby</title><link>http://blog.priorknowledge.com/blog/veritabill#comment-555365094</link><description>&lt;p&gt;The demo link should be: &lt;a href="http://veritabill.herokuapp.com/" rel="nofollow noopener" target="_blank" title="http://veritabill.herokuapp.com/"&gt;http://veritabill.herokuapp...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Tue, 12 Jun 2012 13:52:32 -0000</pubDate></item><item><title>Re: Testing Your Model with Mocha, Mongo, and NodeJS</title><link>http://wekeroad.com/2012/02/25/testing-your-model-with-mocha-mongo-and-nodejs/#comment-451581428</link><description>&lt;p&gt;I also like setting process.env['NODE_ENV'] = 'test' at the beginning of the first test file to run. Then I can set an appropriate database connection or other info in both implementation code and tests.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Tue, 28 Feb 2012 15:55:22 -0000</pubDate></item><item><title>Re: Simple Blog with CoffeeScript, Node.js and CouchDB</title><link>http://blog.koostudios.com/?p=398#comment-451491579</link><description>&lt;p&gt;Even if you installed CoffeeScript elsewhere, you can install it locally with "npm install coffee-script --save". &lt;/p&gt;&lt;p&gt;This will install it to the local "node_modules" and add it to package.json for the current app. &lt;/p&gt;&lt;p&gt;And it makes it tons easier to deploy when you're done developing.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Geoffrey Grosenbach</dc:creator><pubDate>Tue, 28 Feb 2012 14:17:44 -0000</pubDate></item></channel></rss>