<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Desktop on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/desktop/</link><description>Recent content in Desktop on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 07 Nov 2010 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/desktop/index.xml" rel="self" type="application/rss+xml"/><item><title>The screen I couldn't read</title><link>https://blog.vnykmshr.com/writing/the-screen-i-couldnt-read/</link><pubDate>Sun, 07 Nov 2010 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/the-screen-i-couldnt-read/</guid><description>&lt;p&gt;The options chain lit up for the first time this morning. Calls on the left, puts on the right, strikes down the middle. A grid of numbers, green for up, red for down, delta arrows pointing the direction of the move. The rest stays black. The screen is dense. It should be.&lt;/p&gt;
&lt;p&gt;Options is the team&amp;rsquo;s first full product built from scratch. Not the company&amp;rsquo;s &amp;ndash; they&amp;rsquo;ve shipped before us. But this one is ours. We picked the stack, laid out the panels, argued about the grid. Java Swing on the front. A real-time price wire feeding the chain. The server is behind the screen, but the screen is where the work happens.&lt;/p&gt;</description></item></channel></rss>