<?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 ReinH</title><link>http://disqus.com/by/ReinH/</link><description></description><atom:link href="http://disqus.com/ReinH/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 30 Sep 2013 12:15:12 -0000</lastBuildDate><item><title>Re: Clojure's core.typed vs Haskell - Adam Bard and his magical blog</title><link>https://adambard.com/blog/core-typed-vs-haskell/#comment-1064635481</link><description>&lt;p&gt;To clarify, there is no "in Haskell spec" way to say "pretend that this type signature is really this other type signature". This would fundamentally break the type system. It's also not necessary because Haskell is ubiquitously typed whereas core.typed is bolted on to an untyped language and needs some facility for asserting types where none are available.&lt;/p&gt;&lt;p&gt;Also, `unsafeCoerce` is not a part of the Haskell language spec and so is not technically "in Haskell" for some values of "Haskell". `unsafeCoerce` is added by GHC and is meant to be used in very specific cases where its advantages outweigh its (significant) disadvantages.&lt;/p&gt;&lt;p&gt;The most common use afaik is in efficiently implementing some data structure internals in a way that is provably correct (and thus safe) but breaks some type system assumption and so cannot be implemented directly. It's certainly not a part of the every-day Haskell toolkit.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 30 Sep 2013 12:15:12 -0000</pubDate></item><item><title>Re: Edward Kmett on Lenses - The Haskell Cast</title><link>http://haskellcast.com/episode/001-edward-kmett-on-lenses/#comment-1018058528</link><description>&lt;p&gt;And I helped! :D&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 26 Aug 2013 12:38:18 -0000</pubDate></item><item><title>Re: Rails Security in the Wild</title><link>http://excid3.com/blog/rails-security-in-the-wild/#comment-741924716</link><description>&lt;p&gt;Awesome! I gave a talk on software security at RubyConf this year that might be of interest as well. &lt;a href="http://www.confreaks.com/videos/1299-rubyconf2012-making-security-priority-zero" rel="nofollow noopener" target="_blank" title="http://www.confreaks.com/videos/1299-rubyconf2012-making-security-priority-zero"&gt;http://www.confreaks.com/vi...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Tue, 18 Dec 2012 12:41:39 -0000</pubDate></item><item><title>Re: Disappearing test cases or did another part of MySQL just become closed source?</title><link>http://blog.mariadb.org/disappearing-test-cases/#comment-622789419</link><description>&lt;p&gt;Any time a member of one community calls members of another community "fanboys", everyone is diminished. Shame on you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Sat, 18 Aug 2012 11:26:32 -0000</pubDate></item><item><title>Re: Keeping the Magic Alive</title><link>http://hashrocket.com/blog/posts/keeping-the-magic-alive#comment-583352803</link><description>&lt;p&gt;"Accepting on input, strict on output" is one of the fundamental tenets of unix programming. Generally speaking, deferring decisions as late as possible is often better for the user experience.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Tue, 10 Jul 2012 15:03:05 -0000</pubDate></item><item><title>Re: Navigating your bundled gems in Vim - Vim</title><link>http://effectif.com/vim/using-ctags-with-bundler-gems#comment-453727676</link><description>&lt;p&gt;You may like &lt;a href="https://github.com/tpope/gem-ctags" rel="nofollow noopener" target="_blank" title="https://github.com/tpope/gem-ctags"&gt;https://github.com/tpope/ge...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Thu, 01 Mar 2012 16:02:04 -0000</pubDate></item><item><title>Re: 10 things I&amp;#8217;ve never heard a successful startup founder say</title><link>https://blog.asmartbear.com/quotes-startup-founders.html#comment-287557352</link><description>&lt;p&gt;They really are neither.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 15 Aug 2011 20:10:23 -0000</pubDate></item><item><title>Re: installing-homebrew-for-OSX - User Primary</title><link>http://userprimary.net/posts/2010/08/19/installing-homebrew-for-OSX/#comment-115272415</link><description>&lt;p&gt;Sure, tell Apple to make build essentials available in a smaller package. Nothing Homebrew can do about it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 20 Dec 2010 13:59:11 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; Ch-Ch-Ch-Changes</title><link>http://reinh.com/blog/2009/09/21/ch-ch-ch-changes.html#comment-45539968</link><description>&lt;p&gt;Ok, I think I'll just delete further comments from Average. I'll keep the original trolling around for posterity (and the lulz).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 19 Apr 2010 16:53:23 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; Ch-Ch-Ch-Changes</title><link>http://reinh.com/blog/2009/09/21/ch-ch-ch-changes.html#comment-45533866</link><description>&lt;p&gt;No worries. I hope people realize that this anonymous asshole does not, in fact, represent Hashrocket: they would never stoop so low. Hashrocket is an outstanding company full of classy, professional people.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 19 Apr 2010 16:00:07 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; Ch-Ch-Ch-Changes</title><link>http://reinh.com/blog/2009/09/21/ch-ch-ch-changes.html#comment-45532416</link><description>&lt;p&gt;I hope you aren't representing Hashrocket in an official capacity, "Average". This is pretty pathetic.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 19 Apr 2010 15:48:35 -0000</pubDate></item><item><title>Re: Always Use Git Diffs / hg tip</title><link>http://hgtip.com/tips/beginner/2009-10-22-always-use-git-diffs/#comment-36309138</link><description>&lt;p&gt;Git style diffs are also compatible with patch. You just have to use patch -p1 (iirc, who uses patch amirite?).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Wed, 24 Feb 2010 12:32:35 -0000</pubDate></item><item><title>Re: http://blog.101ideas.cz/post/391285028</title><link>http://blog.101ideas.cz/posts/rails-stop-steal-our-projects.html#comment-35900464</link><description>&lt;p&gt;Childish words from an angry and confused person with no understanding of open source or how to form a cohesive opinion. What a waste.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 22 Feb 2010 14:21:13 -0000</pubDate></item><item><title>Re: Make Your Blog More Social In 3 Easy Steps</title><link>http://blog.adsdevshop.com/2009/11/02/make-your-blog-more-social-in-3-easy-steps/#comment-21726870</link><description>&lt;p&gt;Disqus has improved tremendously in the past months. I'm definitely enjoying using it as both a blogger and a blog reader.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Mon, 02 Nov 2009 22:10:12 -0000</pubDate></item><item><title>Re: Joining Reductive Labs</title><link>http://codefluency.com/2009/10/24/joining-reductive-labs.html#comment-20986520</link><description>&lt;p&gt;We're glad to have you! It's about time we finally had the opportunity to work together.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Sun, 25 Oct 2009 12:33:30 -0000</pubDate></item><item><title>Re: Marty Haught</title><link>http://martyhaught.com/articles/2009/10/06/when-is-agile-too-much/#comment-19464743</link><description>&lt;p&gt;It sounds like we are violently (or, in this case, quite politely) agreeing. Cheers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Wed, 07 Oct 2009 19:51:19 -0000</pubDate></item><item><title>Re: Marty Haught</title><link>http://martyhaught.com/articles/2009/10/06/when-is-agile-too-much/#comment-19273452</link><description>&lt;p&gt;Marty,&lt;br&gt;&lt;br&gt;As a Hashrocket alumnus and a strong supporter of Agile, there are some points in your post that I would like to address. The crux of my issue is with the following sentence: "To insist that a pair of programmers should be assigned, spend a week’s worth of time story carding and write a full test suite would have given this client nothing today."&lt;br&gt;&lt;br&gt;The danger here is in defining Agile by a specific set of processes, in this case Pair Programming, Story Carding, and Test Driven Development. While these processes are common in Agile implementations, Agile is not a set of practices. The Manifesto itself makes this clear by favoring "Individuals and interactions over processes and tools".&lt;br&gt;&lt;br&gt;The writers of the Agile Manifesto were wise in not espousing a specific set of processes. No set of processes, how ever well designed, can be suited for all tasks. The Agile Manifesto says, "Working software is the primary measure of progress", "Simplicity--the art of maximizing the amount of work not done--is essential", and "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software." I think this makes the Agile stance on your issue quite clear, and quite different from your analysis.&lt;br&gt;&lt;br&gt;Indeed, your attitude as expressed in your conclusion is far more in line with Agile than your previous descriptions of Agile. You say, "... I care more about meeting the client’s needs than insisting on a process that might not be appropriate". This is an excellent description of a fundamental Agile principle.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Tue, 06 Oct 2009 23:44:28 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; Ch-Ch-Ch-Changes</title><link>http://reinh.com/blog/2009/09/21/ch-ch-ch-changes.html#comment-17237390</link><description>&lt;p&gt;Thanks for the well wishes, folks. It's greatly appreciated.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Wed, 23 Sep 2009 15:41:28 -0000</pubDate></item><item><title>Re: ReinH | A Git Workflow for Agile Teams</title><link>http://railsnotes.com/442-git-workflow/#comment-13124205</link><description>&lt;p&gt;Hi Melvin, thanks for the mention! Glad you found my article useful.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Wed, 22 Jul 2009 14:47:34 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; Simplify Your Dev Environment With Passenger&amp;nbsp;Pane</title><link>http://reinh.com/blog/2009/04/17/simplify-your-dev-environment-with-passenger-pane.html#comment-8659733</link><description>&lt;p&gt;@Nick: I'm not certain that the purpose of Passenger Pane is to make it more difficult for you to get to your log files. I'm pretty sure that it's to put all your ruby development app servers in one place and make it trivial to add, remove or restart them. YMMV, of course.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Fri, 24 Apr 2009 13:13:40 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; A Git Workflow for Agile&amp;nbsp;Teams</title><link>http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html#comment-8337416</link><description>&lt;p&gt;David: That is simpler but only works on more recent versions of git.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Sat, 18 Apr 2009 17:40:03 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; A Git Workflow for Agile&amp;nbsp;Teams</title><link>http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html#comment-6851273</link><description>&lt;p&gt;@jackdempsey is absolutely correct.&lt;/p&gt;&lt;p&gt;One point of this workflow is to treat master as a dumb tracking branch. Never commit into master, always into a topical branch. This means that master can always be fastforwarded, no need to rebase. There are other workflows that use pull --rebase or fetch and rebase to achieve similar goals. I prefer a branch-often workflow for its simplicity.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Tue, 03 Mar 2009 18:29:49 -0000</pubDate></item><item><title>Re: Utilize Canonical URLs in Your Rails Applications - Intridea Company Blog</title><link>http://intridea.com/2009/2/13/utilize-canonical-urls-in-your-rails-apps?blog=company#comment-6377797</link><description>&lt;p&gt;Unprofessional? The only one being unprofessional here is this anonymous asshat. Good work Michael.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Wed, 18 Feb 2009 12:50:22 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; Story Driven Development With&amp;nbsp;Rails</title><link>http://reinh.com/blog/2008/12/09/story-driven-development-with-rails.html#comment-4339474</link><description>&lt;p&gt;@josh Check out tpope's pickler gem: &lt;a href="http://github.com/tpope/pickler/tree/master" rel="nofollow noopener" target="_blank" title="http://github.com/tpope/pickler/tree/master"&gt;http://github.com/tpope/pic...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Thu, 11 Dec 2008 21:04:49 -0000</pubDate></item><item><title>Re: ReinH &amp;mdash; Story Driven Development With&amp;nbsp;Rails</title><link>http://reinh.com/blog/2008/12/09/story-driven-development-with-rails.html#comment-4339410</link><description>&lt;p&gt;@joshknowles Funny you should mention that. We actually do have a proof of concept that uses the Pivotal Tracker API to pull properly written stories into cucumber features that we're using on a current project. (By we I mean Tim Pope.) We are also using a more formal GWT syntax in our acceptance tests partially for this purpose.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ReinH</dc:creator><pubDate>Thu, 11 Dec 2008 21:00:44 -0000</pubDate></item></channel></rss>