<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Sheep without Muzzle</title>
	<link>http://blog.solomakhin.net</link>
	<description>The ideal is to hear the present as noise outside our window, while we continue to follow the discourse of the classics which resounds clearly and articulately inside our room.</description>
	<pubDate>Wed, 03 Sep 2008 06:19:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
	<language>en</language>
			<item>
		<title>&#8220;On the Art of Writing&#8221;</title>
		<link>http://blog.solomakhin.net/2008/09/03/on-the-art-of-writing/</link>
		<comments>http://blog.solomakhin.net/2008/09/03/on-the-art-of-writing/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 06:19:54 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Books]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2008/09/03/on-the-art-of-writing/</guid>
		<description><![CDATA[Today I read &#8220;On the Art  of Writing&#8221; by Sir Arthur Quiller-Couch. My eyes opened wide every time I recognized my own silly mistakes. I recommend everyone to read the whole book, and pay special attention to Chapter 5 &#8220;On Jargon&#8221; and Chapter 12 &#8220;On Style.&#8221;
Sir Arthur Quiller-Couch, &#8220;On the Art of Writing: Lectures Delivered [...]]]></description>
			<content:encoded><![CDATA[<p>Today I read &#8220;On the Art  of Writing&#8221; by Sir Arthur Quiller-Couch. My eyes opened wide every time I recognized my own silly mistakes. I recommend everyone to read the whole book, and pay special attention to Chapter 5 &#8220;On Jargon&#8221; and Chapter 12 &#8220;On Style.&#8221;</p>
<p><small>Sir Arthur Quiller-Couch, &#8220;On the Art of Writing: Lectures Delivered in the University of Cambridge, 1913–1914,&#8221; Cambridge: University Press, 1916, Bartleby.com, 2000. <a href="http://www.bartleby.com/190/">www.bartleby.com/190/</a>. 24 August 2008</small></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2008/09/03/on-the-art-of-writing/feed/</wfw:commentRss>
		</item>
		<item>
		<title>&#8220;Write Anything&#8221;</title>
		<link>http://blog.solomakhin.net/2008/08/29/write-anything/</link>
		<comments>http://blog.solomakhin.net/2008/08/29/write-anything/#comments</comments>
		<pubDate>Fri, 29 Aug 2008 00:32:12 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Career]]></category>

		<category><![CDATA[Study]]></category>

		<category><![CDATA[Work]]></category>

		<category><![CDATA[inspiration]]></category>

		<category><![CDATA[time management]]></category>

		<category><![CDATA[writer's block]]></category>

		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2008/08/29/write-anything/</guid>
		<description><![CDATA[Read awesome paper on overcoming writer&#8217;s block. The two principles I learned and successfully applied at work are:  (1) allocate a bit of time every day for writing, and (2) separate writing and editing. The separation trick feels awkward at first but has great results. I highly recommend reading this paper to anyone who struggles [...]]]></description>
			<content:encoded><![CDATA[<p>Read <a href="http://www4.ncsu.edu/unity/lockers/users/f/felder/public/Columns/WriteAnything.pdf" title="Open PDF">awesome paper</a> on overcoming writer&#8217;s block. The two principles I learned and successfully applied at work are:  (1) allocate a bit of time every day for writing, and (2) separate writing and editing. The separation trick feels awkward at first but has great results. I highly recommend reading this paper to anyone who struggles writing anything longer than a paragraph.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2008/08/29/write-anything/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Evolution Bugfix</title>
		<link>http://blog.solomakhin.net/2008/08/23/evolution-bugfix/</link>
		<comments>http://blog.solomakhin.net/2008/08/23/evolution-bugfix/#comments</comments>
		<pubDate>Sat, 23 Aug 2008 19:03:32 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Open Source]]></category>

		<category><![CDATA[bug]]></category>

		<category><![CDATA[bugfix]]></category>

		<category><![CDATA[evolution]]></category>

		<category><![CDATA[mail client]]></category>

		<category><![CDATA[patch]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2008/08/23/evolution-bugfix/</guid>
		<description><![CDATA[Patched bug 547822 in Evolution mail client. The patch removes 6 lines and adds 18. A user filed the bug because both task list and appointment list show &#8220;Upcoming Appointments&#8221; in title when printed or exported in PDF. The patch changed the titles to &#8220;Tasks&#8221; and &#8220;Calendar.&#8221;
]]></description>
			<content:encoded><![CDATA[<p>Patched bug <a href="http://bugzilla.gnome.org/show_bug.cgi?id=547822" title="Bug 547822">547822</a> in Evolution mail client. The patch removes 6 lines and adds 18. A user filed the bug because both task list and appointment list show &#8220;Upcoming Appointments&#8221; in title when printed or exported in PDF. The patch changed the titles to &#8220;Tasks&#8221; and &#8220;Calendar.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2008/08/23/evolution-bugfix/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Learning Styles</title>
		<link>http://blog.solomakhin.net/2008/08/19/learning-styles/</link>
		<comments>http://blog.solomakhin.net/2008/08/19/learning-styles/#comments</comments>
		<pubDate>Tue, 19 Aug 2008 01:21:47 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Career]]></category>

		<category><![CDATA[goals]]></category>

		<category><![CDATA[know yourself]]></category>

		<category><![CDATA[plans]]></category>

		<category><![CDATA[self-assessment]]></category>

		<category><![CDATA[study styles]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2008/08/19/learning-styles/</guid>
		<description><![CDATA[Took Felder and Solomon Learning Styles Test. Results:
This means that I am extremely &#8220;visual&#8221; and &#8220;intuitive learner.&#8221; This makes sense, because my class notes are often drawings. I also try to visualize what people tell me.
Advantages are being &#8220;better at grasping new concepts&#8221; as well as &#8220;working faster and being more innovative.&#8221; I noticed this [...]]]></description>
			<content:encoded><![CDATA[<p>Took Felder and Solomon Learning Styles Test. Results:<img src="http://blog.solomakhin.net/wp-content/uploads/2008/08/results1.png" alt="Results" /></p>
<p>This means that I am extremely &#8220;visual&#8221; and &#8220;intuitive learner.&#8221; This makes sense, because my class notes are often drawings. I also try to visualize what people tell me.</p>
<p>Advantages are being &#8220;better at grasping new concepts&#8221; as well as &#8220;working faster and being more innovative.&#8221; I noticed this when doing forensics at <a href="http://www.mobilearmor.com">Mobile Armor</a>.</p>
<p>Possible pitfalls are &#8220;missing important details&#8221; and &#8220;making careless mistakes in calculations or hands-on work.&#8221; Thankfully, being aware of such issues helps to complete tasks successfully.</p>
<p><small>Richard M. Felder and Barbara A. Solomon, &#8220;Learning Styles and Strategies,&#8221; North Carolina State University, 18 August 2008, <a href="http://www4.ncsu.edu/unity/lockers/users/f/felder/public/ILSdir/styles.htm" title="Learning Styles and Strategies">http://www4.ncsu.edu/unity/lockers/users/f/felder/public/ILSdir/styles.htm</a></small></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2008/08/19/learning-styles/feed/</wfw:commentRss>
		</item>
		<item>
		<title>&#8220;A Study of Passwords and Methods Used in Brute-Force SSH Attacks&#8221;</title>
		<link>http://blog.solomakhin.net/2008/04/06/awesome-password-talk/</link>
		<comments>http://blog.solomakhin.net/2008/04/06/awesome-password-talk/#comments</comments>
		<pubDate>Sun, 06 Apr 2008 03:19:00 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2008/04/06/awesome-password-talk/</guid>
		<description><![CDATA[This is a great security talk from Clarkson.

Audio
OpenOffice.Org Slides
PowerPoint Slides

]]></description>
			<content:encoded><![CDATA[<p>This is a great security talk from Clarkson.</p>
<ul>
<li><a href="http://monitor.sclab.clarkson.edu/Owens_thesis_defense.mp3">Audio</a></li>
<li><a href="http://monitor.sclab.clarkson.edu/Owens_thesis_defense.odp">OpenOffice.Org Slides</a></li>
<li><a href="http://monitor.sclab.clarkson.edu/Owens_thesis_defense.ppt">PowerPoint Slides</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2008/04/06/awesome-password-talk/feed/</wfw:commentRss>
<enclosure url="http://monitor.sclab.clarkson.edu/Owens_thesis_defense.mp3" length="41299016" type="audio/mpeg" />
		</item>
		<item>
		<title>Scale Awareness</title>
		<link>http://blog.solomakhin.net/2008/03/19/scale-awareness/</link>
		<comments>http://blog.solomakhin.net/2008/03/19/scale-awareness/#comments</comments>
		<pubDate>Wed, 19 Mar 2008 05:23:49 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2008/03/19/scale-awareness/</guid>
		<description><![CDATA[Integers and floats are not sufficient representations of measurements. If an engineer has an int to count bytes and an int to count sectors, adding the two yields useless gibberish. A C compiler is not able to catch such mistakes. An engineer can discover such blunders during a review, but developer time is expensive. Therefore, [...]]]></description>
			<content:encoded><![CDATA[<p>Integers and floats are not sufficient representations of measurements. If an engineer has an <em>int</em> to count bytes and an <em>int</em> to count sectors, adding the two yields useless gibberish. A <strong>C</strong> compiler is not able to catch such mistakes. An engineer can discover such blunders during a review, but developer time is expensive. Therefore, the compiler needs to be made aware of scales. There are two ways to accomplish this.</p>
<pre>int size = 123; // bytes
int location = 4; // sectors
int new_location = location + size;</pre>
<p><em>This is legal <strong>C</strong>, but a human reader sees the mistake of adding two variables of different scale.</em></p>
<p>The first method for scale awareness is to define types using the already existing tools. In the bytes and sectors example, an engineer can create a <em>struct</em> for sectors and a <em>struct</em> for bytes with accompanying arithmetic and conversion functions.</p>
<pre>typedef struct {
      int value : 0;
} sector;
sector add(sector, sector);
sector sub(sector, sector);
byte to_bytes(sector);</pre>
<pre>class Sector {
    int value = 0;
    void add(Sector);
    void sub(Sector);
    Byte toBytes();
}</pre>
<p><em>Scale aware software can prevent conversion errors.</em></p>
<p>The second method for scale awareness is a built-in compiler construct for defining scale relationships. Using such tool, an engineer can define a sector to be equal to 512 bytes. The compiler can then evaluate the addition of bytes and sectors as an expression of type <em>byte</em>, converting sectors to bytes at run-time.</p>
<pre>typedef int sector;
typedef int byte;
<span style="color:#ff0000">scaledef sector = 512 byte;</span>
byte size = 123;
sector location = 4;
byte new_location = location + size;</pre>
<p><em>A modified <strong>C</strong> compiler can verify existence of scale conversions at  compile time and perform the conversions at run time.</em></p>
<p>There are arguments in favor of both methods. Types can be placed into a standalone software library. This ensures modularity by separating the standard library, the scales library, and the controlling module that utilizes these libraries. However, because it is hard to account for all possible types of scales and conversions, the scales library must be constantly modified and updated, defeating one of the main advantages of modularity – code reuse.</p>
<p>The argument in favor of <em>scaledef</em> lies in its inherent simplicity from an engineer&#8217;s perspective. Having only one line of scaling definition increases readability of software source. The guarantee of automatic conversions by the compiler allows an engineer to concentrate on the higher level of logic rather than dwelling upon the details of ubiquitous conversions.</p>
<p>The software engineering community can benefit from a study in the quality of software produced by engineers who use the scale aware paradigm as compared to those who perform manual conversions. An other benefit of such study is the collection of first prototypes of the  software libraries for scaling.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2008/03/19/scale-awareness/feed/</wfw:commentRss>
		</item>
		<item>
		<title>What Exactly We&#8217;re Trying To Accomplish</title>
		<link>http://blog.solomakhin.net/2007/10/31/what-exactly-were-trying-to-accomplish/</link>
		<comments>http://blog.solomakhin.net/2007/10/31/what-exactly-were-trying-to-accomplish/#comments</comments>
		<pubDate>Wed, 31 Oct 2007 04:06:18 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Environment]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2007/10/31/what-exactly-were-trying-to-accomplish/</guid>
		<description><![CDATA[The world embraces Adam Smith&#8217;s ideal of individualism, hoping that the Scottish philosopher is right and everyone will benefit in the end. Unfortunately, we have arrived at the Nash equilibrium in the matters of sustainable development. No one is willing to pay the price for preserving the environment, so it is degrading in negligence. Using [...]]]></description>
			<content:encoded><![CDATA[<p>The world embraces Adam Smith&#8217;s ideal of individualism, hoping that the Scottish philosopher is right and everyone will benefit in the end. Unfortunately, we have arrived at the Nash equilibrium in the matters of sustainable development. No one is willing to pay the price for preserving the environment, so it is degrading in negligence. Using Hurwicz&#8217;s ideas, we need to design a mechanism that will make preserving the environment economically advantageous.</p>
<p>UN has a committee on environment preservation, and holds annual international conferences. We have not seen much progress. The problem is in the soft and unequal requirements.</p>
<p>The best way to make the requirements hard is to bar the percentage of trade equal to the percentage of unmet financial obligations per country. This will make countries very much motivated to meet their contribution promises and possibly lower them.</p>
<p>To make the requirements fair, every country must contribute the same percentage of their gross domestic product to the cause of environmental improvement. This will be the resource for building renewable, non-polluting sources of energy like wind and solar panel farms.</p>
<p>Following these rules, the countries will strive to meet their contribution promises in order to keep trade uninterrupted. The incentive to  grow the gross domestic product is also preserved.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2007/10/31/what-exactly-were-trying-to-accomplish/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Ahoy from St. Louis</title>
		<link>http://blog.solomakhin.net/2007/10/26/ahoy-from-st-louis/</link>
		<comments>http://blog.solomakhin.net/2007/10/26/ahoy-from-st-louis/#comments</comments>
		<pubDate>Fri, 26 Oct 2007 07:14:36 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Fun]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2007/10/26/ahoy-from-st-louis/</guid>
		<description><![CDATA[Yarrr, mateys!

We be the softwarrre pirrrates!
]]></description>
			<content:encoded><![CDATA[<p>Yarrr, mateys!</p>
<p><a href="http://blog.solomakhin.net/images/yarrr.jpg"><img src="http://blog.solomakhin.net/images/yarrr.jpg" title="I look much better in person." alt="Pirate." height="240" width="320" /></a></p>
<p>We be the softwarrre pirrrates!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2007/10/26/ahoy-from-st-louis/feed/</wfw:commentRss>
		</item>
		<item>
		<title>gvocab IPO</title>
		<link>http://blog.solomakhin.net/2007/10/14/gvocab-ipo/</link>
		<comments>http://blog.solomakhin.net/2007/10/14/gvocab-ipo/#comments</comments>
		<pubDate>Sun, 14 Oct 2007 04:49:11 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2007/10/14/gvocab-ipo/</guid>
		<description><![CDATA[gvocab has a new home at google code. There is also a link at gnome files.
]]></description>
			<content:encoded><![CDATA[<p>gvocab has a new home at <a href="http://code.google.com/p/gvocab/">google code</a>. There is also a link at <a href="http://gnomefiles.org/app.php/gvocab">gnome files</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2007/10/14/gvocab-ipo/feed/</wfw:commentRss>
		</item>
		<item>
		<title>gvocab 0.2 &#8220;You must die! I alone am best!&#8221;</title>
		<link>http://blog.solomakhin.net/2007/10/13/gvocab-02-you-must-die-i-alone-am-best/</link>
		<comments>http://blog.solomakhin.net/2007/10/13/gvocab-02-you-must-die-i-alone-am-best/#comments</comments>
		<pubDate>Sat, 13 Oct 2007 17:03:36 +0000</pubDate>
		<dc:creator>Rouslan Solomakhin</dc:creator>
		
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://blog.solomakhin.net/2007/10/13/gvocab-02-you-must-die-i-alone-am-best/</guid>
		<description><![CDATA[Here is the second release of gvocab, the vocabulary builder. New features:

gvocab remembers session state after closing
mistakes are crossed out, hints are bold
faster start up time with a progress bar for reading the words xml file

Click to view the screenshot:

It turned out that gconf recommends to not store anything except properties in the gconf database. [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.solomakhin.net/files/gvocab-0.2.tar.bz2">Here</a> is the second release of gvocab, the vocabulary builder. New features:</p>
<ul>
<li>gvocab remembers session state after closing</li>
<li>mistakes are crossed out, hints are bold</li>
<li>faster start up time with a progress bar for reading the words xml file</li>
</ul>
<p>Click to view the screenshot:<br />
<a href="http://blog.solomakhin.net/images/gvocab-0,2-screenshot.png"><img src="http://blog.solomakhin.net/images/gvocab-0,2-screenshot.png" title="GVocab 0.2" alt="GVocab 0.2 Screenshot" height="198" width="352" /></a></p>
<p>It turned out that <a href="http://www.gnome.org/projects/gconf/">gconf</a> recommends to not store anything except properties in the gconf database. gvocab stores session state in ~/.gnome2/gvocab/session.xml, similar to <a href="http://www.gnome.org/projects/gedit/">gedit</a>, which stores its own session information in ~/.gnome2/gedit/sessions/gedit-*.</p>
<p>For the next release, I am planning improvement to the teaching algorithm. I think a word should not be marked as learned the first time the user guessed its meaning right. Repetition is essential to learning.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.solomakhin.net/2007/10/13/gvocab-02-you-must-die-i-alone-am-best/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
