<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Digital Thoughts</title>
    <link rel="alternate" type="text/html" href="http://blog.lib.umn.edu/stevew/digital_thoughts/" />
    <link rel="self" type="application/atom+xml" href="http://blog.lib.umn.edu/stevew/digital_thoughts/atom.xml" />
    <id>tag:blog.lib.umn.edu,2009-06-24:/stevew/digital_thoughts//10475</id>
    <updated>2010-11-10T22:46:02Z</updated>
    <subtitle>Random thoughts digitized.  Mostly University of Minnesota computer support related.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Enterprise 4.31-en</generator>

<entry>
    <title>Innovation on the cheap</title>
    <link rel="alternate" type="text/html" href="http://blog.lib.umn.edu/stevew/digital_thoughts/2010/11/innovation-on-the-cheap.html" />
    <id>tag:blog.lib.umn.edu,2010:/stevew/digital_thoughts//10475.259609</id>

    <published>2010-11-10T22:33:27Z</published>
    <updated>2010-11-10T22:46:02Z</updated>

    <summary><![CDATA[Many times I've seen small under funded, but stubborn agents succeed at projects large well funded groups have failed at.&nbsp; I've come to believe that lack of funds can be a major driver of innovation.I've always admired the touch screen...]]></summary>
    <author>
        <name>Steve Winckelman</name>
        
    </author>
    
    <category term="byoe" label="byoe" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="innovation" label="innovation" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="qrbarcode" label="QR bar code" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="roomscheduling" label="room scheduling" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-us" xml:base="http://blog.lib.umn.edu/stevew/digital_thoughts/">
        <![CDATA[Many times I've seen small under funded, but stubborn agents succeed at 
projects large well funded groups have failed at.&nbsp; I've come to believe 
that lack of funds can be a major driver of innovation.<br /><br />I've 
always admired the touch screen room scheduling devices found outside of
 business conference rooms such as those at the General Mills 
headquarters.&nbsp; But implementing such a system required funding for 
installation of displays at the room doors and a back-end server with 
dedicated applications software.&nbsp; <br /><br />The new STSS building has such a system for the classrooms (see below).<br /><br /><img src="file:///C:/Users/stevew/Desktop/Schedule%20devices/DSCN2874.JPG" alt="" /><img alt="DSCN2874.JPG" src="http://blog.lib.umn.edu/stevew/myblog/DSCN2874.JPG" class="mt-image-center" style="text-align: center; display: block; margin: 0pt auto 20px;" height="768" width="1024" /><div>Which
 got us wondering about how we could gain some of the same functionality
 on the cheap.&nbsp; This is really useful for those times you want to borrow
 a room to have a quick meeting, but don't want to interfere with an 
officially scheduled event or when you want to know if this is the room 
your meeting or class is being held in.&nbsp; Our solution lies in the 
observation that more and more of us are carrying small, internet 
attached computers around in our pockets and bags.<br /><br /><img alt="DSCN2879.JPG" src="http://blog.lib.umn.edu/stevew/myblog/DSCN2879.JPG" class="mt-image-center" style="text-align: center; display: block; margin: 0pt auto 20px;" height="594" width="755" /></div>The
 phone camera scans the bar code bringing up a URL that goes to the room
 scheduling web site and displays a mobile device formatted room 
reservation schedule.&nbsp; Instant, cheap solution.&nbsp; And if you don't happen
 to have or be with anyone having a smart phone, you still have the 
old fashion method of typing a URL for the reservation system into a 
browser on your laptop.<br /><br />If you want to try something like this on your own, a useful QR code generator can be found at <a href="http://qrcode.kaywa.com/">http://qrcode.kaywa.com/</a>.<br /> ]]>
        
    </content>
</entry>

<entry>
    <title>Can we make this any harder?</title>
    <link rel="alternate" type="text/html" href="http://blog.lib.umn.edu/stevew/digital_thoughts/2009/06/can-we-make-this-any-harder.html" />
    <id>tag:blog.lib.umn.edu,2009:/stevew/digital_thoughts//10475.184379</id>

    <published>2009-06-24T21:45:39Z</published>
    <updated>2009-06-24T21:53:29Z</updated>

    <summary> Normal 0 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:&quot;Table Normal&quot;; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:&quot;&quot;; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:&quot;Times New Roman&quot;; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} Imagine if every component vendor and sub-contractor involved...</summary>
    <author>
        <name>Steve Winckelman</name>
        
    </author>
    
        <category term="Desktop computer support" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="patches" label="patches" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="software" label="software" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="updates" label="updates" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en-us" xml:base="http://blog.lib.umn.edu/stevew/digital_thoughts/">
        <![CDATA[<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Cstevew%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" LatentStyleCount="156">
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]-->

<p class="MsoNormal">Imagine if every component vendor and sub-contractor
involved in the production of your automobile refined and changed their bits of
your vehicle every day while you drove.<span style="">&nbsp;
</span>It seems obvious that sooner or later specification drift or feature
improvements would cause a cascading failure of one sort or another.<span style="">&nbsp; </span>Yet this is exactly how we drive our desktop
computer systems here on the internet highway.<span style="">&nbsp;
</span></p>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<p class="MsoNormal">This all started innocently enough.<span style="">&nbsp; </span>A software vendor wanted to ensure that their
software was protected from recently discovered flaws allowing hackers to gain
access to the computer so the vendors began offering easier methods of
downloading updates from their websites.<span style="">&nbsp;
</span>Soon it became clear that many users had neither the time nor the
inclination to download and install these updates, so methods of automatically
pushing them out to computers were developed and deployed. </p>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<p class="MsoNormal">The result is an environment where many parts of a
computer's software persona can change at a moments notice in response to
perceived threats.<span style="">&nbsp; </span>These threats are
often very real as I am sure anyone who has lost their mutual fund account
password to a hacker employing a keystroke logger would tell you.<span style="">&nbsp; </span>Yet from a usability perspective all this
change can be unnerving.<span style="">&nbsp; </span><a href="http://www.itilfoundation.org/">ITIL</a> processes
for example try to rein in undocumented computer changes in their attempt to
increase stability and usability.</p>

<p class="MsoNormal"><span style="">&nbsp;</span></p>

<p class="MsoNormal">Just off the top of my head here's a list of people that can
make changes the computer I'm using to type this post:</p>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<p class="MsoNormal">Local IT staff</p>

<p class="MsoNormal">Central IT staff</p>

<p class="MsoNormal">Microsoft employees</p>

<p class="MsoNormal">Sun employees</p>

<p class="MsoNormal">Apple employees</p>

<p class="MsoNormal">Adobe employees</p>

<p class="MsoNormal">Symantec employees</p>

<p class="MsoNormal">The Firefox and Mozilla support communities</p>

<p class="MsoNormal">And of course any hacker that can slip something in via a malicious
advertisement, malicious webpage, malicious image, or any other clever use of the
software flaws discovered on a daily basis.</p>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<p class="MsoNormal">From a support perspective this means that the computer
placed on your desk yesterday is not the computer you are using today.<span style="">&nbsp; </span>And resistance is futile, for if the vendor
updates are ignored, it's only a matter of time before some automated hacking automata
exercises a flaw in your computer's software environment and changes your
computer to meet some else's nefarious needs.</p>

 ]]>
        
    </content>
</entry>

</feed>
