<?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 NICCAI</title><link>http://disqus.com/by/NICCAI/</link><description></description><atom:link href="http://disqus.com/NICCAI/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 18 Sep 2014 17:32:50 -0000</lastBuildDate><item><title>Re: Search Vs Social</title><link>http://avc.com/2014/09/search-vs-social-2/#comment-1595323870</link><description>&lt;p&gt;Your blog is inherently social. It would be interesting to see the numbers for ecommerce and non-personal websites.  Also, which converts/transacts better?  Eyeballs aren't the only metric for performance.  What is the level of intent for each audience?  We often see the level of purchase intent higher for organic search users (those looking for a particular product).  Given that, my guess is that search is higher on the intent chain compared to pure social traffic.  There is no doubt that influencers like yourself can help seed intent and even generate a number of transactions, but conversion success is likely a function of influence level.&lt;/p&gt;&lt;p&gt;In short, Search vs Social isn't purely about traffic or even user acquisition.  It must also look at conversion success, and long-term retention (social is likely your retention mechanism).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Thu, 18 Sep 2014 17:32:50 -0000</pubDate></item><item><title>Re: Messaging, Notifications, and Mobile</title><link>http://avc.com/2014/07/messaging-notifications-and-mobile/#comment-1494348853</link><description>&lt;p&gt;Like most thinks these days, Context is King.  Communication is no different.  Some conversations happen more naturally alongside content, others in another app or medium, and for others timing is everything.&lt;/p&gt;&lt;p&gt;Further fragmentation is likely, but I expect we will have innovation around managing notifications and shifting conversations.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Sun, 20 Jul 2014 14:20:34 -0000</pubDate></item><item><title>Re: The Internet Of Things</title><link>http://avc.com/2014/05/the-internet-of-things/#comment-1406764002</link><description>&lt;p&gt;The dumb terminal was something we recognized early in computing, but the costs of cloud infrastructure were to high and cumbersome.  The internet of things is exactly that - a network.  The days of a standalone device with no piece in the cloud are over. The question that remains is which patterns of connectivity will prevail.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Tue, 27 May 2014 12:57:10 -0000</pubDate></item><item><title>Re: Markets and Clearing Prices</title><link>http://avc.com/2013/12/markets-and-clearing-prices/#comment-1170725690</link><description>&lt;p&gt;Surge pricing feels wrong, but I wonder if there is something to bid pricing? Is it any different? Maybe not, but optically it probably is.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Thu, 19 Dec 2013 16:50:29 -0000</pubDate></item><item><title>Re: Creative Link Effects</title><link>http://blog.niccai.com/post/57534961745#comment-990544451</link><description>&lt;p&gt;Really great that we can start thinking about flourishes like this without expensive and repetitive additions to the DOM.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Tue, 06 Aug 2013 14:17:20 -0000</pubDate></item><item><title>Re: Mentor/Investor Whiplash</title><link>http://avc.com/2013/07/mentorinvestor-whiplash/#comment-982308108</link><description>&lt;p&gt;"You have to learn to hear that feedback but not react to it." So true. Great post.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Wed, 31 Jul 2013 02:37:33 -0000</pubDate></item><item><title>Re: Improving Backbone App Performance</title><link>http://blog.pamelafox.org/2013/06/improving-backbone-app-performance.html#comment-921284468</link><description>&lt;p&gt;Nice post.  Some things we've realized in our development match up with your changes.  Like:&lt;/p&gt;&lt;p&gt;- avoiding some of the nice evented hooks like add&lt;br&gt;- using document fragments to render groups of elements&lt;br&gt;- cache everything you can when you can&lt;br&gt;- avoid fetching and refetching as much as possible&lt;/p&gt;&lt;p&gt;Posts like this are helpful. Thanks for taking the time.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Thu, 06 Jun 2013 14:03:14 -0000</pubDate></item><item><title>Re: App to App Handshakes</title><link>http://avc.com/2013/01/app-to-app-handshakes/#comment-758671899</link><description>&lt;p&gt;It's true that the big kids are fighting and for the most part control the devices, the OS, and the overall ecosystem.  But this post brings me back to the bigger story. There's a user revolution going on, but good design and interaction are really the tip of the iceberg.  UX is the low hanging user fruit.  The last few years have been about data, apis, and more data, but the next few years are going to be about the users behind that data and the actions they perform in content creation.  User intent is often overlooked in interaction design, but it needs to be at the forefront of the next generation.&lt;/p&gt;&lt;p&gt;What is sharing? Is it a copy of content on another website? Or is it something deeper? What is the intent behind it? The psychology? Users need an OS centered around actions that answer intent.&lt;/p&gt;&lt;p&gt;Fred, there is a trend in your posts. Whether it is content shifting or app handshakes, it's about the user.&lt;/p&gt;&lt;p&gt;Content is created by users.&lt;br&gt;Content is consumed by users.&lt;br&gt;Actions are performed by users.&lt;/p&gt;&lt;p&gt;We need an action OS, an action API.  Buttons and menus are not interfaces.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Mon, 07 Jan 2013 04:10:58 -0000</pubDate></item><item><title>Re: Mobile &amp;amp; Conversations</title><link>http://avc.com/2012/09/mobile-conversations/#comment-645645622</link><description>&lt;p&gt;The issue with many of the best commenting systems is that they're tied to the post itself, and not the greater conversation. It's a simple statement that unfortunately requires a complex solution. I'm a big believer in content shifting, and mobile will solidify this trend over time. I think the need or trend is shifting away from landing on &lt;a href="http://avc.com" rel="nofollow noopener" target="_blank" title="avc.com"&gt;avc.com&lt;/a&gt; or domains in general. This isn't to say that internet growth won't continue to add value to domains, but I think the deeper trend will lead us towards deeper semantic connectors.  I'm also wondering about the role of mobile and how it is treated today. Although there is no doubt about it's significance going forward, I think we will see less of the "mobile version" approach to thinking, and more about "mobile as an extension" of other processes. How might you consume this post in one medium and yet choose to answer twenty minutes later on another? How will your phone know what you watched on tv?&lt;/p&gt;&lt;p&gt;As it stands, conversation discovery occurs due to an explicit invitation (email, @ reply, etc) or at an explicit locale (avc, a point in time on twitter, etc).  It's true that you may be looped in via your own comment, or if fortunate enough by whom you follow in common, but I think the next generation of conversations will bubble up to you.  True value and rank can be assigned by what you read, where you've been, where a conversation starts, and how relevant the momentum is to you, your taste, and your social and business connectors.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Mon, 10 Sep 2012 03:08:06 -0000</pubDate></item><item><title>Re: Fun Friday: Where Do You Get Your News?</title><link>http://avc.com/2012/04/fun-friday-where-do-you-get-your-news/#comment-496758938</link><description>&lt;p&gt;My response to people when they roll their eyes about twitter..."Hey, it's my newspaper." Great in the morning, after dinner, pairs well with a cup of coffee.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Fri, 13 Apr 2012 19:30:49 -0000</pubDate></item><item><title>Re: Third-Party JavaScript Development Optimizing CSS Delivery - Bocoup</title><link>http://bocoup.com/weblog/3pjs-css-delivery/#comment-494576392</link><description>&lt;p&gt;Is the next article about optional namespacing? :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Wed, 11 Apr 2012 14:34:03 -0000</pubDate></item><item><title>Re: Feature Friday: Mark Unread In Gmail</title><link>http://avc.com/2011/12/feature-friday-mark-unread-in-gmail/#comment-400570004</link><description>&lt;p&gt;I use Star for follow-up. It's easier and typically has less taps.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Wed, 04 Jan 2012 13:59:27 -0000</pubDate></item><item><title>Re: #screwcable</title><link>http://avc.com/2012/01/screwcable/#comment-399891357</link><description>&lt;p&gt;I try like hell to pay for all of my content, but it is amazing how many content providers won't let you consume individual shows, teams, etc digitally.  I feel extorted.  The whole process is broken.  To add insult to injury, the marketing efforts by cable co's saying they allow individual channel selection is an ode to fine print.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Tue, 03 Jan 2012 16:54:45 -0000</pubDate></item><item><title>Re: PlayYourGame - Athlete Development Resource by Players for Players</title><link>http://www.playyourgame.com/#comment-377983162</link><description>&lt;p&gt;We've made the old site available through a backdoor.  Please keep in mind that news items, teams, etc are all out of date.  &lt;a href="http://www.playyourgame.com/home.html" rel="nofollow noopener" target="_blank" title="http://www.playyourgame.com/home.html"&gt;http://www.playyourgame.com...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Fri, 02 Dec 2011 17:42:31 -0000</pubDate></item><item><title>Re: PlayYourGame - Athlete Development Resource by Players for Players</title><link>http://www.playyourgame.com/#comment-377982928</link><description>&lt;p&gt;We've made the old site available through a backdoor.  Please keep in mind that news items, teams, etc are all out of date.  &lt;a href="http://www.playyourgame.com/home.html" rel="nofollow noopener" target="_blank" title="http://www.playyourgame.com/home.html"&gt;http://www.playyourgame.com...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Fri, 02 Dec 2011 17:42:04 -0000</pubDate></item><item><title>Re: PlayYourGame - Athlete Development Resource by Players for Players</title><link>http://www.playyourgame.com/#comment-377982841</link><description>&lt;p&gt;We've made the old site available through a backdoor.  Please keep in mind that news items, teams, etc are all out of date.  &lt;a href="http://www.playyourgame.com/home.html" rel="nofollow noopener" target="_blank" title="http://www.playyourgame.com/home.html"&gt;http://www.playyourgame.com...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Fri, 02 Dec 2011 17:41:55 -0000</pubDate></item><item><title>Re: PlayYourGame - Athlete Development Resource by Players for Players</title><link>http://www.playyourgame.com/#comment-377981529</link><description>&lt;p&gt;Thank you so much for taking the time to share your feedback with us as your insight and thoughtful comments are greatly appreciated. We created &lt;a href="http://PlayYourGame.com" rel="nofollow noopener" target="_blank" title="PlayYourGame.com"&gt;PlayYourGame.com&lt;/a&gt; with the vision of it being exactly what you’ve stated that you felt it was, a resource for players by players and to hear 10 years later that it had the impact on you that it did reinforces to us that the vision we had for &lt;a href="http://PlayYourGame.com" rel="nofollow noopener" target="_blank" title="PlayYourGame.com"&gt;PlayYourGame.com&lt;/a&gt; was the right one.&lt;br&gt; &lt;br&gt;The points/suggestions you’ve raised with how &lt;a href="http://PlayYourGame.com" rel="nofollow noopener" target="_blank" title="PlayYourGame.com"&gt;PlayYourGame.com&lt;/a&gt; should move forward are all valid and rest assured many of them had been attempted in the past. With that said, timing is everything and our goal for a re-launch of a new and improved &lt;a href="http://PlayYourGame.com" rel="nofollow noopener" target="_blank" title="PlayYourGame.com"&gt;PlayYourGame.com&lt;/a&gt; is to keep true to its vision and to create a viable business out of the resource so that for generations to come players like yourself, parents of players, coaches, scouts, etc, can turn to &lt;a href="http://PlayYourGame.com" rel="nofollow noopener" target="_blank" title="PlayYourGame.com"&gt;PlayYourGame.com&lt;/a&gt; for the same reasons you did 10 years ago.&lt;br&gt; &lt;br&gt;Thank you again for your feedback and we wish you all the best.&lt;br&gt; &lt;br&gt;Sincerely,&lt;br&gt; &lt;br&gt;Corey &amp;amp; Nick&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Fri, 02 Dec 2011 17:39:20 -0000</pubDate></item><item><title>Re: PlayYourGame - Athlete Development Resource by Players for Players</title><link>http://www.playyourgame.com/#comment-336437470</link><description>&lt;p&gt;Sorry, all.  We're working on other projects (and jobs) at the moment.  We love the site, but are trying to figure out the best way to make it viable for the long term.  If there are past articles that you are looking for, let us know, and we'll try to get you them.&lt;/p&gt;&lt;p&gt;Thanks,&lt;br&gt;Nick&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Mon, 17 Oct 2011 02:26:12 -0000</pubDate></item><item><title>Re: Disrupting The Photocopier Business</title><link>http://avc.com/2011/10/disrupting-the-photocopier-business/#comment-326721098</link><description>&lt;p&gt;I'd like my camera to have "paper recognition" so it would zoom/focus on the sheet in question.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Tue, 04 Oct 2011 18:57:33 -0000</pubDate></item><item><title>Re: Minimum Viable Personality</title><link>http://avc.com/2011/09/minimum-viable-personality/#comment-323133084</link><description>&lt;p&gt;READ BRILLIANT. DRAW AWESOME. DO WIN.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Thu, 29 Sep 2011 14:35:35 -0000</pubDate></item><item><title>Re: http://blog.niccai.com/post/10772030103</title><link>http://blog.niccai.com/post/10772030103#comment-323093983</link><description>&lt;p&gt;Yeah, it's impressive and totally doable when you control the browser.  Keep in mind that the whole UI will be preloaded and only data needs to be passed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Thu, 29 Sep 2011 13:37:25 -0000</pubDate></item><item><title>Re: Book - Scalable and Modular Architecture for CSS</title><link>http://smacss.com/book/type-state#comment-320737954</link><description>&lt;p&gt;This chapter is really important, but I think the examples might be confusing to newcomers. I'd probably try to illustrate why you apply the state to the parent element versus to all siblings. The sibling method could produce cleaner CSS, but the performance of application would be really bad. The outcome of state being combined with a module is thus generally preferred. Also a key take away (for the positive) would be the predictability of using a common class and point of application across modules - like the .selected class always gets applied to the li.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Tue, 27 Sep 2011 03:52:38 -0000</pubDate></item><item><title>Re: Book - Scalable and Modular Architecture for CSS</title><link>http://smacss.com/book/type-layout#comment-320730636</link><description>&lt;p&gt;Spoke too soon...just read the next chapter. That said, the module bit in this chapter could probably be pushed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Tue, 27 Sep 2011 03:25:25 -0000</pubDate></item><item><title>Re: Book - Scalable and Modular Architecture for CSS</title><link>http://smacss.com/book/type-layout#comment-320728383</link><description>&lt;p&gt;I would suggest classing out your li as something like .gridItem to avoid the child selector in a module like this. By doing so, you'd also avoid the element as key selector. It might also be worth noting in your text why you use the child selector for readers. It is too easy to miss this reasoning, and most will end up countering their module in descendent list items (say in a nested action list).  I know I have made this mistake too often in fast moving projects in the past, and I've made it a personal rule to follow in my CSS architecture.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Tue, 27 Sep 2011 03:16:06 -0000</pubDate></item><item><title>Re: Book - Scalable and Modular Architecture for CSS</title><link>http://smacss.com/book/type-base#comment-320415385</link><description>&lt;p&gt;Agreed, we do the same - state usually follows close to base.  It might not lend itself to the flow of your overall book, but it might be good to reflect your cascade order in your chapter order (but I haven't read that far yet).  :)   Excuse my backseat writing...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">NICCAI</dc:creator><pubDate>Mon, 26 Sep 2011 16:06:51 -0000</pubDate></item></channel></rss>