<?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 joeyguerra</title><link>http://disqus.com/by/joeyguerra/</link><description></description><atom:link href="http://disqus.com/joeyguerra/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 04 Dec 2013 07:54:22 -0000</lastBuildDate><item><title>Re: There&amp;#8217;s No Such Thing as a &amp;#8220;Devops Team&amp;#8221;</title><link>http://continuousdelivery.com/2012/10/theres-no-such-thing-as-a-devops-team/#comment-1150135101</link><description>&lt;p&gt;I was so ready to jump on the band wagon when I read the post title because devops is more of a philosophy than a role and I disagree with the tactic of creating a separate team called devops. But as I read, I got the feeling that the post is saying that the software engineers should just take more responsibility of the system and that the operational engineers are just there to support the software engineers and that's where I realized that there IS such thing as a devops team. However, it's not what you think.&lt;/p&gt;&lt;p&gt;Devops is a cross functional team of operational, software, and test engineers who, as a team, are responsible for building, deploying and monitoring a system. So in that regard, the devops team is most certainly on the hook for the systems that get built, deploying them, writing the build deployment scripts and the operations of them. Not just the software engineers, but the team as a whole. I think part of the problem is that typically operational and test engineers are viewed as shared resources, providing a service. And the software engineers are project or product resources, effectively dividing them. If we start viewing the systems we build as products and the people building them as a team, then we can start referring to that team as our devops team. Which would then make sense to me. I'd be on board with that.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Wed, 04 Dec 2013 07:54:22 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1143651717</link><description>&lt;p&gt;That presentation seemed to basically say use your HTML site as THE API by implementing the semantic web, &lt;a href="http://schema.org" rel="nofollow noopener" target="_blank" title="http://schema.org"&gt;http://schema.org&lt;/a&gt;. I think Facebook and G+ are already doing that per their sharing integrations. This presentation was pretty cool. I like his point that you get all this tooling right away and that is a key point in the decision to use semantic HTML as an API. That's what I like about implementing content negotiation too. I'm certainly going to add micro data to my blog engine when i get home.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Thu, 28 Nov 2013 21:49:45 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1130543855</link><description>&lt;p&gt;I give up. I'm going to go build web sites in Java.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Tue, 19 Nov 2013 22:25:48 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1129407919</link><description>&lt;p&gt;I wonder what that reason is that most sites are not built like this? Content negotiation is part of the HTTP protocol (&lt;a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html);" rel="nofollow noopener" target="_blank" title="http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html);"&gt;http://www.w3.org/Protocols...&lt;/a&gt; and it's not just bout XML or JSON, but language too.&lt;/p&gt;&lt;p&gt;Why have we as web developers not implemented in our applications what seems to be a big part of the protocol that we have been building on top of for so long?&lt;/p&gt;&lt;p&gt;If my implementation was constrained to 1 model per view, I would say that you're right on, this design would fail before hitting the ground. But while one of the parameters is "users" (a model) in the code above, the next parameter is "self" which is an instance of "Resource", which can have whatever the view might need. That said, I have NOT used this design in an evolving, big application. So I haven't seen it taken through the normal paces that we've experienced. I would like to though. I've built several small web sites with this technique and really liked how easy it was to add functionality to it. What kind of app would I have to build with it to prove it out? A dating web site:)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Tue, 19 Nov 2013 06:15:55 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1129069126</link><description>&lt;p&gt;Here's the link to NancyFX's Content Negotiation doc. &lt;a href="https://github.com/NancyFx/Nancy/wiki/Content-Negotiation" rel="nofollow noopener" target="_blank" title="https://github.com/NancyFx/Nancy/wiki/Content-Negotiation"&gt;https://github.com/NancyFx/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 18 Nov 2013 22:58:29 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1129052284</link><description>&lt;p&gt;I just downloaded Xamarin and built my first hello world app in NacnyFx. It's nice. You should do it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 18 Nov 2013 22:47:58 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1129021923</link><description>&lt;p&gt;Yeah, I had a bug on the home page Disqus integration. The comments were attached to the home page, not the article. When I updated the Disqus integration on the home page to be attached to the article that was on the home page, your comment went into limbo.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 18 Nov 2013 22:13:29 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1129020593</link><description>&lt;p&gt;I notice the same idea when looking at how Express JS does it, seeing your code and reading an article which stated that the content negotiation facility should call a different "action". I think that's the main design difference in what I've coded in my blog engine and what I'm seeing elsewhere. In my blog engine, the same "action" is called and the content negotiation happens after the routing code has executed and returned with it's result. I do see how the design decision could be less flexible in the case where the "model" is different depending on the representation. But now that I type that out, I'm asking myself if it's different then shouldn't it really be a separate resource all together?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 18 Nov 2013 22:12:12 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1129016300</link><description>&lt;p&gt;I agree, an API is serious and I don't suggest using content negotiation within a web site to solve the problem that an API should solve. I see implementing content negotiation in a web site more as a "base" to build upon for the web site, not with the intent of using it as an API which should have well defined and stable interfaces.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 18 Nov 2013 22:07:18 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/#comment-1125379572</link><description>&lt;p&gt;Grant it, the code I wrote hasn't been tested in every browser and so forth, but yeah, I think your point that the problem isn't very hard to solve natively is a great take away. I'm not knocking frameworks, more the overuse of them, especially when it's not necessary. And I would love it if people read this and felt challenged to question more using a framework before jumping in so quickly. What's the first step in the scientific method, define the problem?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Fri, 15 Nov 2013 22:31:01 -0000</pubDate></item><item><title>Re: Death to the IF statement</title><link>http://haacked.com/archive/2013/11/08/death-to-the-if-statement.aspx#comment-1120633528</link><description>&lt;p&gt;I agree with what your saying. I wonder if the point in the article would be better highlighted if the example presented was more like:&lt;/p&gt;&lt;p&gt;if(){&lt;br&gt;}else{&lt;br&gt;}&lt;br&gt;foreach(){}&lt;br&gt;while(){}&lt;br&gt;while(){}&lt;br&gt;foreach(){}&lt;br&gt;switch(){&lt;br&gt;case:&lt;br&gt;default:&lt;br&gt;}&lt;/p&gt;&lt;p&gt;I've totally seen code like this which had tons of control structures and branching. In that particular case, it was obvious that a tactic to reducing the complexity would be to target removing if statements and loops. I think that's why the article's point really rings true with me. But as with many things, it's good practice to strive for balance, especially when modifying existing systems, which is how I interpreted your response.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Tue, 12 Nov 2013 23:10:15 -0000</pubDate></item><item><title>Re: Death to the IF statement</title><link>http://haacked.com/archive/2013/11/08/death-to-the-if-statement.aspx#comment-1118949695</link><description>&lt;p&gt;Wow. I'm really surprised at what seems to be a mostly negative reaction to this article. I would've thought the idea of reducing code complexity by focusing on reducing conditional statements would've rung true with more people. It does with me. Here's my +1 for what it's worth.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 11 Nov 2013 22:29:56 -0000</pubDate></item><item><title>Re: Asp.net MVC Content Negotiation | kijana woodard</title><link>http://kijanawoodard.com/asp-net-mvc-content-negotiation#comment-1118523469</link><description>&lt;p&gt;IIIIIIEEEEEEEEE!!!!!! IE Accepts header doesn't include text/html.&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.gethifi.com/blog/browser-rest-http-accept-headers" rel="nofollow noopener" target="_blank" title="http://www.gethifi.com/blog/browser-rest-http-accept-headers"&gt;http://www.gethifi.com/blog...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 11 Nov 2013 15:14:07 -0000</pubDate></item><item><title>Re: Introducing Liaison | kijana woodard</title><link>http://kijanawoodard.com/introducing-liaison#comment-1097484183</link><description>&lt;p&gt;And I couldn't help but &lt;a href="http://www.youtube.com/watch?v=b2F-DItXtZs" rel="nofollow noopener" target="_blank" title="http://www.youtube.com/watch?v=b2F-DItXtZs"&gt;http://www.youtube.com/watc...&lt;/a&gt; to the web scale link.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Sat, 26 Oct 2013 10:41:41 -0000</pubDate></item><item><title>Re: Introducing Liaison | kijana woodard</title><link>http://kijanawoodard.com/introducing-liaison#comment-1097187370</link><description>&lt;p&gt;This reminds me of a pub sub implementation, which of course, I LOVE!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Sat, 26 Oct 2013 00:03:09 -0000</pubDate></item><item><title>Re: Interface Inversion | kijana woodard</title><link>http://kijanawoodard.com/interface-inversion#comment-1083895264</link><description>&lt;p&gt;Oh the paradox!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Tue, 15 Oct 2013 21:52:43 -0000</pubDate></item><item><title>Re: class Foo: IFoo is an Anti-Pattern | kijana woodard</title><link>http://kijanawoodard.com/foo-ifoo-is-an-anti-pattern#comment-1082627218</link><description>&lt;p&gt;Can we go further? Can't we just say that class Oauth2Authentication is the interface? I mean, why do I have to care if it implements IAuthenticate? Do I care if it implements that "interface" or do I care if it has or doesn't a method called Authenticate?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 14 Oct 2013 22:08:23 -0000</pubDate></item><item><title>Re: How to Wake up Your Kids | kijana woodard</title><link>http://kijanawoodard.com/how-to-wake-up-your-kids#comment-1079980323</link><description>&lt;p&gt;I have personally observed and confirmed every one of these techniques as valid proven facts.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Sat, 12 Oct 2013 10:20:25 -0000</pubDate></item><item><title>Re: Welcoming Cloud Code to the Parse Family</title><link>http://blog.parse.com/announcements/welcoming-cloud-code-to-the-parse-family/#comment-649856331</link><description>&lt;p&gt;You guys need a devil's advocate. Someone who throws rocks at all the cool stuff ya'll do. I don't have time to do it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Thu, 13 Sep 2012 23:00:01 -0000</pubDate></item><item><title>Re: ASP.NET Deployment Needs To Be Fixed</title><link>http://wekeroad.com/post/4373719917#comment-181652226</link><description>&lt;p&gt;I deploy with vs one click publish. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Sat, 09 Apr 2011 16:42:42 -0000</pubDate></item><item><title>Re: Waxin' &amp; Milkin': A Visual Mixtape</title><link>http://waxandmilk.tumblr.com/post/69641969#comment-13993324</link><description>&lt;p&gt;Classic. I'm feeling nostalgic.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Wed, 05 Aug 2009 15:10:53 -0000</pubDate></item><item><title>Re: Opera to reinvent the web &amp;ndash; web waits for fat lady to sing</title><link>http://www.geeksaresexy.net/2009/06/15/opera-to-reinvent-the-web-web-waits-for-fat-lady-to-sing/#comment-44508693</link><description>&lt;p&gt;Reinventing the web to me would be peer to peer communications within the browser. I guess imagine the browser IS the IM client.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Mon, 15 Jun 2009 19:50:23 -0000</pubDate></item><item><title>Re: Surrender! Foucault and Twitter</title><link>http://twopointouch.com/2009/05/27/surrender-foucault-and-twitter/#comment-24847295</link><description>&lt;p&gt;So is social networks the new God? new religion? To control people's behavior?&lt;/p&gt;&lt;p&gt;As I was reading this article, I was thinking, "Yeah, I'm not gonna post anything that my boss might see". Hmm. That's a shame.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Wed, 27 May 2009 11:13:34 -0000</pubDate></item><item><title>Re: XMLHTTPRequest, JSONP &amp;#038; Cappuccino</title><link>http://cappuccino.org/discuss/2008/10/08/xmlhttprequest-jsonp-cappuccino/#comment-3222395</link><description>&lt;p&gt;Adding and removing the &amp;lt;script/&amp;gt; elements seems to leak memory in IE. Does the JSONP technique just add &amp;lt;script/&amp;gt; elements to the DOM?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Wed, 22 Oct 2008 00:21:24 -0000</pubDate></item><item><title>Re: XMLHTTPRequest, JSONP &amp;#038; Cappuccino</title><link>http://cappuccino.org/discuss/2008/10/08/xmlhttprequest-jsonp-cappuccino/#comment-3222274</link><description>&lt;p&gt;Nice job. I wanted to comment about using CPJSONPConnection class for accomplishing cross domain communications. I've built a chat web app that's loaded within one domain but communicates with a subdomain. I've implemented a polling messaging technique to inform the user of any messages that they've received. Have you tested using the CPJSONPConnection class in a situation where the app has to make multiple requests (5 seconds apart)? Do you have any ideas about the browser memory usage when using the &amp;lt;script/&amp;gt; tag technique?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joey Guerra</dc:creator><pubDate>Wed, 22 Oct 2008 00:07:29 -0000</pubDate></item></channel></rss>