<?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 hgimenez</title><link>http://disqus.com/by/hgimenez/</link><description></description><atom:link href="http://disqus.com/hgimenez/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 14 May 2018 17:36:36 -0000</lastBuildDate><item><title>Re: Determine the gender of a first name</title><link>https://genderize.io/#comment-3900794920</link><description>&lt;p&gt;Hi! As far as privacy and and regulations like GDPR go, it'd be very useful to know how data is being processed by &lt;a href="http://genderize.io" rel="nofollow noopener" target="_blank" title="genderize.io"&gt;genderize.io&lt;/a&gt; itself. For instance, are the names being saved in your side at all, or does the app do a lookup and respond with the payload without storing anything? How about any caches, or logs? Thanks in advance!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Mon, 14 May 2018 17:36:36 -0000</pubDate></item><item><title>Re: PostgreSQL Addict</title><link>http://blog.pgaddict.com/posts/the-two-kinds-of-stats-in-postgresql#comment-1588209665</link><description>&lt;p&gt;I reserve comment on the name "Monitoring stats," but I kind of like "Planner Stats" as a better name for the proposed "Data distribution stats"&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Sat, 13 Sep 2014 23:17:45 -0000</pubDate></item><item><title>Re: Copying Heroku Databases Between Apps</title><link>https://blog.codeship.com/heroku-copy-database-between-apps/#comment-873400915</link><description>&lt;p&gt;Hi. Thanks for the article.&lt;/p&gt;&lt;p&gt;It should be noted that with a production tier database (crane and up) you can instead create a fork of your database into your staging app. &lt;a href="https://postgres.heroku.com/#fork" rel="nofollow noopener" target="_blank" title="https://postgres.heroku.com/#fork"&gt;https://postgres.heroku.com...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;-Harold&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Tue, 23 Apr 2013 13:09:21 -0000</pubDate></item><item><title>Re: http://biggestfool.tumblr.com/post/24049554541</title><link>http://biggestfool.tumblr.com/post/24049554541#comment-747897234</link><description>&lt;p&gt;&amp;lt;3&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Wed, 26 Dec 2012 13:05:09 -0000</pubDate></item><item><title>Re: http://biggestfool.tumblr.com/post/24049554541</title><link>http://biggestfool.tumblr.com/post/24049554541#comment-747841899</link><description>&lt;p&gt;On Heroku you can just add a config var with your secret token and load that up using ENV, 12 factor app style: &lt;a href="http://www.12factor.net/config" rel="nofollow noopener" target="_blank" title="http://www.12factor.net/config"&gt;http://www.12factor.net/config&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Wed, 26 Dec 2012 12:01:23 -0000</pubDate></item><item><title>Re: Boundary: not just for clusters</title><link>http://boundary.com/blog/2012/08/08/boundary-not-just-for-clusters/#comment-614715388</link><description>&lt;p&gt;Thanks for sharing. What version of postgres?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 09 Aug 2012 14:27:18 -0000</pubDate></item><item><title>Re: https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default</title><link>https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default#comment-489091107</link><description>&lt;p&gt;This only applies to dedicated databases (ronin and up). For now.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Fri, 06 Apr 2012 13:10:14 -0000</pubDate></item><item><title>Re: https://postgres.heroku.com/blog/past/2012/1/16/postgresql_91_available_in_beta</title><link>https://postgres.heroku.com/blog/past/2012/1/16/postgresql_91_available_in_beta#comment-489090192</link><description>&lt;p&gt;No, both forks and followers are of the same version as their parents.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Fri, 06 Apr 2012 13:09:04 -0000</pubDate></item><item><title>Re: https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default</title><link>https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default#comment-453683500</link><description>&lt;p&gt;Nope, actually all dedicated postgres plans run on their own clusters. Dedicated plans can be seen here: &lt;a href="https://postgres.heroku.com/pricing" rel="nofollow noopener" target="_blank" title="https://postgres.heroku.com/pricing"&gt;https://postgres.heroku.com...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 01 Mar 2012 15:21:42 -0000</pubDate></item><item><title>Re: https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default</title><link>https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default#comment-453664988</link><description>&lt;p&gt;Thanks for the heads up. I see it too; we will get it fixed soon.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 01 Mar 2012 15:03:10 -0000</pubDate></item><item><title>Re: https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default</title><link>https://postgres.heroku.com/blog/past/2012/3/1/postgresql_91_now_default#comment-453661091</link><description>&lt;p&gt;pg_cancel_backend was only available to super user roles. Because we don't give users super user accounts, that was a problem for users wanting to cancel their queries, so this is a safe way to empower non-super users to do that on their own backends.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 01 Mar 2012 14:58:01 -0000</pubDate></item><item><title>Re: Convert Ruby 1.8 to 1.9 hash syntax</title><link>http://robots.thoughtbot.com/post/17450269990#comment-436432401</link><description>&lt;p&gt;My thing also didn't take care of &lt;/p&gt;&lt;p&gt;`rescue Some::Exception =&amp;gt; e`&lt;/p&gt;&lt;p&gt;So here's what worked across an entire project.&lt;/p&gt;&lt;p&gt;`perl -pi -e 's/([^\w^:]):([\w\d_]+)\s*=&amp;gt;/\1\2:/g' **/*.rb`&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Sat, 11 Feb 2012 18:23:52 -0000</pubDate></item><item><title>Re: Convert Ruby 1.8 to 1.9 hash syntax</title><link>http://robots.thoughtbot.com/post/17450269990#comment-436419840</link><description>&lt;p&gt;Because the regex looks for any non whitespace character - [^ ]* - it will be too greedy when there are colons prior to that symbol's colon, as is the case with ruby in many cases when colons are used to fully qualify a namespaced class: &lt;a href="http://rubular.com/r/xlMLC6LE0Z" rel="nofollow noopener" target="_blank" title="http://rubular.com/r/xlMLC6LE0Z"&gt;http://rubular.com/r/xlMLC6...&lt;/a&gt;. In that case I ended up with something like Namespace:Class.method(:key: "value")&lt;/p&gt;&lt;p&gt;A more restrictive regex:&lt;/p&gt;&lt;p&gt;`perl -pi -e 's/:([\w\d_]+)(\s*)=&amp;gt;/\1:/g' **/*.rb`&lt;/p&gt;&lt;p&gt;#lolperl&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Sat, 11 Feb 2012 18:03:47 -0000</pubDate></item><item><title>Re: https://postgres.heroku.com/blog/past/2012/2/8/small_change_big_win</title><link>https://postgres.heroku.com/blog/past/2012/2/8/small_change_big_win#comment-434510708</link><description>&lt;p&gt;Joe,&lt;/p&gt;&lt;p&gt;2 is a better value than 4. Tuning is a continuous process, and as we gather more data there's always the possibility it will change again.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 09 Feb 2012 19:05:57 -0000</pubDate></item><item><title>Re: https://postgres.heroku.com/blog/past/2012/1/18/postgresql_91_available_in_beta</title><link>https://postgres.heroku.com/blog/past/2012/1/18/postgresql_91_available_in_beta#comment-422478206</link><description>&lt;p&gt;@Pierre, check out &lt;a href="http://addons.heroku.com/heroku-shared-postgresql" rel="nofollow noopener" target="_blank" title="http://addons.heroku.com/heroku-shared-postgresql"&gt;http://addons.heroku.com/he...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Fri, 27 Jan 2012 14:10:55 -0000</pubDate></item><item><title>Re: The Durable Document Store You Didn&amp;#8217;t Know You Had, But Did</title><link>http://robots.thoughtbot.com/post/13829210385#comment-380457265</link><description>&lt;p&gt;Hey @nirvdrum , no idea, have never done compression in the database itself. Something to investigate for sure. With an untrusted language, unlike PLV8, you could shell out and call `gzip` or something. I wonder if there's something on PGXN to do this?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Tue, 06 Dec 2011 13:17:40 -0000</pubDate></item><item><title>Re: The Durable Document Store You Didn&amp;#8217;t Know You Had, But Did</title><link>http://robots.thoughtbot.com/post/13829210385#comment-380384813</link><description>&lt;p&gt;They both use libxml2 to do the actual work, but that said I haven't done crazy amounts of parsing inside Postgres so I can't speak to that.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Tue, 06 Dec 2011 11:36:43 -0000</pubDate></item><item><title>Re: The Durable Document Store You Didn&amp;#8217;t Know You Had, But Did</title><link>http://robots.thoughtbot.com/post/13829210385#comment-380380324</link><description>&lt;p&gt;That's awesome. Definitely check out the javascript language I link to here (PLV8). It's a fast, trusted language that you can run inside postgres to parse JSON data as demonstrated in Will's talk (also linked).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Tue, 06 Dec 2011 11:29:43 -0000</pubDate></item><item><title>Re: Tidy views and beyond with Decorators</title><link>http://robots.thoughtbot.com/post/13641910701#comment-380356765</link><description>&lt;p&gt;I'm not sure what the DSL would look like but it'd be good to see what you're thinking.&lt;/p&gt;&lt;p&gt;I will say, I haven't felt any pain with the API here, so creating a "cleaner" DSL seems unnecessary, IMO.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Tue, 06 Dec 2011 10:50:55 -0000</pubDate></item><item><title>Re: Tidy views and beyond with Decorators</title><link>http://robots.thoughtbot.com/post/13641910701#comment-380355868</link><description>&lt;p&gt;Yeah, I've put them in lib/.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Tue, 06 Dec 2011 10:49:28 -0000</pubDate></item><item><title>Re: How-To: Quick Rails Benchmarking</title><link>http://robots.thoughtbot.com/post/12241426497#comment-354669548</link><description>&lt;p&gt;yup, the command I posted there will install the gcdata patched 1.9.2 MRI Ruby. I added &lt;code&gt;--name gcdata&lt;/code&gt; so that it would also call it that. I therefore have:&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;pre&gt;&lt;code&gt;$ rvm list&lt;br&gt;...&lt;br&gt;   ruby-1.9.2-p180-gcdata [ x86_64 ]&lt;br&gt;=&amp;gt; ruby-1.9.2-p290 [ x86_64 ]&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;and I can just do&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;pre&gt;&lt;code&gt;$ rvm use ruby-1.9.2-p180-gcdata&lt;br&gt;Using /Users/hgimenez/.rvm/gems/ruby-1.9.2-p180-gcdata&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 03 Nov 2011 08:31:33 -0000</pubDate></item><item><title>Re: http://davidczarnecki.com/post/9766126496</title><link>http://blog.davidczarnecki.com/post/9766126496#comment-302315256</link><description>&lt;p&gt;Hey David, thanks for the patch!&lt;/p&gt;&lt;p&gt;Maybe I should've just been straight up: No tests, no merge. It's not about whether it warrants a test: No code should exist that is not tested. If you practice TDD every line of code you write is motivated by a failing test, so this si just a natural extension of that.&lt;/p&gt;&lt;p&gt;There are many ways to test this, but at the end it's not about whether Capistrano logger is doing its job (we know it is) - it's about whether we're using the capistrano logger (the point of your pull request), ensuring no regression bugs, and making it easy to make changes in the future.&lt;/p&gt;&lt;p&gt;Thanks again for the patch, and hope to see more contributions from you in the future!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Sun, 04 Sep 2011 11:11:44 -0000</pubDate></item><item><title>Re: ActiveRecord, Caching, and the Single Responsibility Principle</title><link>http://robots.thoughtbot.com/post/9123160250#comment-301962423</link><description>&lt;p&gt;it's an (awesome) RSpec helper: &lt;a href="http://relishapp.com/rspec/rspec-core/docs/helper-methods/let-and-let" rel="nofollow noopener" target="_blank" title="http://relishapp.com/rspec/rspec-core/docs/helper-methods/let-and-let"&gt;http://relishapp.com/rspec/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Sat, 03 Sep 2011 19:00:43 -0000</pubDate></item><item><title>Re: See you at PostgreSQL West </title><link>http://robots.thoughtbot.com/post/9670242845#comment-300514869</link><description>&lt;p&gt;you could always OUTER join us.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 01 Sep 2011 13:20:51 -0000</pubDate></item><item><title>Re: How to make the most of an apprenticeship</title><link>http://robots.thoughtbot.com/post/9638248298#comment-300382587</link><description>&lt;p&gt;Hey Alex,&lt;/p&gt;&lt;p&gt;Great article! Linking you to the ESR article was arguably a cold move - although it is a classic that must be read at least once. And you're right, there's no such thing as a stupid question.&lt;/p&gt;&lt;p&gt;One of the things that I wanted you to accomplish is improve your autodidacticism even more by tinkering, trying stuff out, researching, experimenting, whatever. That's one the most valuable skills a doer can have and helps secure a life-long learning experience. Go you!&lt;/p&gt;&lt;p&gt;I agree with your sentiment about pairing. Pairing with someone new always teaches me something, either a new programming technique or pattern, a vim trick, or generally anything that helps me become more productive. It's a great way to share knowledge, oftentimes ignorant of the fact you're actually sharing it.&lt;/p&gt;&lt;p&gt;Hopefully we can pair again some day, and you will teach me a thing or two.&lt;/p&gt;&lt;p&gt;Best of luck with the next thing!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Harold Giménez</dc:creator><pubDate>Thu, 01 Sep 2011 10:11:07 -0000</pubDate></item></channel></rss>