<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-7972942899684557472</atom:id><lastBuildDate>Fri, 22 Mar 2013 06:45:38 +0000</lastBuildDate><category>SpringFramework</category><category>Story</category><category>Quotes</category><category>Gradle</category><category>Zen</category><category>Philosophy</category><category>Writing</category><category>Design</category><category>WebStart</category><category>JavaScript</category><category>Java</category><category>Jokes</category><category>Presentations</category><category>Programming</category><title>Apprenticeship Notes</title><description>Notes of apprenticeship of programming and other things</description><link>http://www.apprenticeshipnotes.org/</link><managingEditor>noreply@blogger.com (Gamal Mateo)</managingEditor><generator>Blogger</generator><openSearch:totalResults>47</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ApprenticeshipNotes" /><feedburner:info uri="apprenticeshipnotes" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-1878539633596279721</guid><pubDate>Fri, 15 Mar 2013 02:03:00 +0000</pubDate><atom:updated>2013-03-21T19:40:34.835-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><category domain="http://www.blogger.com/atom/ns#">SpringFramework</category><title>Springframework - Using annotations to register Custom Converters</title><atom:summary>Source Code: Example.
Springframework 3.2.1.RELEASE

Problem

In order to register custom converters we have to do the following:

&lt;bean id="conversionService" class="org.springframework.context.support.ConversionServiceFactoryBean"&gt;
     &lt;property name="converters"&gt;
         &lt;list&gt;
             &lt;!-- list of converters--&gt;
             &lt;bean class="org.anotes.springexample.converter.PersonToClient</atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/1Za_qKbGidY/springframework-using-annotations-to_14.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/1Za_qKbGidY" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2013/03/springframework-using-annotations-to_14.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-5644460704416291721</guid><pubDate>Mon, 14 Jan 2013 00:57:00 +0000</pubDate><atom:updated>2013-01-14T11:13:01.925-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Java</category><category domain="http://www.blogger.com/atom/ns#">WebStart</category><category domain="http://www.blogger.com/atom/ns#">Gradle</category><title>Generating Java Web Start files using Gradle</title><atom:summary>Source Code: Example.

Problem

We have a Java Swing program and we need to create the files needed to use webstart in order to execute our program. 

Solution

We have to follow the next steps:

Generate the key file

Using the keytool.exe program that is in "\bin" we will generate the key using:

keytool -genkey -alias http://www.anotes.org -keystore D:/temp/anotes.keys


Next to this we have </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/XoMH5WXkXN4/generating-webstart-files-using-gradle.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/XoMH5WXkXN4" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2013/01/generating-webstart-files-using-gradle.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-3476362146822124234</guid><pubDate>Sun, 15 Apr 2012 04:05:00 +0000</pubDate><atom:updated>2012-04-17T11:05:01.740-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><category domain="http://www.blogger.com/atom/ns#">SpringFramework</category><title>Spring AOP–Examples</title><atom:summary>Source Code:Example  Setting Context&lt;?xml version="1.0" encoding="UTF-8"?&gt;&lt;beans xmlns="http://www.springframework.org/schema/beans"       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"       xmlns:aop="http://www.springframework.org/schema/aop"       xmlns:context="http://www.springframework.org/schema/context"       xsi:schemaLocation="http://www.springframework.org/schema/beans http://</atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/9KvsDGAO2ZE/spring-aopexamples.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>1</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/9KvsDGAO2ZE" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/04/spring-aopexamples.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-3892744222872912942</guid><pubDate>Sun, 15 Apr 2012 01:33:00 +0000</pubDate><atom:updated>2012-04-14T21:05:46.504-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><category domain="http://www.blogger.com/atom/ns#">SpringFramework</category><title>Spring Expression Language (SpEL).</title><atom:summary>Getting properties file&lt;util:properties id="settings" location="classpath:settings.properties"/&gt;Accesing a value in properties&lt;property name="accessToken" value="#{settings['twitter.accessToken']}"/&gt;systemEnvironment and systemPropertiesIn addition to reading properties from a &lt;util:properties&gt;-declared collection, Spring makes two special selections of properties available to SpEL:  </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/WR9ZYKF3aMg/spring-expression-language-spel.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/WR9ZYKF3aMg" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/04/spring-expression-language-spel.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-6430625973822102573</guid><pubDate>Thu, 12 Apr 2012 03:03:00 +0000</pubDate><atom:updated>2012-04-11T22:03:51.073-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Growing Object Oriented Software, Guided by Tests–Extracts</title><atom:summary>Source: Growing Object Oriented Software, Guided by Tests Roles, Responsibilities, Collaborators We try to think about objects in terms of roles, responsibilities, and collaborators, as best described by Wirfs-Brock and McKean.   An object is an implementation of one or more roles;  a role is a set of related responsibilities;  and a responsibility is an obligation to perform a task or know </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/tkEnlg33_Yw/growing-object-oriented-software-guided.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/tkEnlg33_Yw" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/04/growing-object-oriented-software-guided.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-1047407117552039500</guid><pubDate>Fri, 23 Mar 2012 01:10:00 +0000</pubDate><atom:updated>2012-03-22T20:13:07.149-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Art of Readable Code – Extracts</title><atom:summary>Source: The Art of Readable Code–Extracts  Basic Rules:  Code should be easy to understand. Code should be written to minimize the time it would take for someone else to understand it. Surface-Level Improvements  Picking good names,  Writing good comments,  Formatting your code neatly About names The best names are ones that can’t be misconstrued—the person reading your code will understand it </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/a9SQYZhoF-c/art-of-readable-code-extracts.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/a9SQYZhoF-c" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/03/art-of-readable-code-extracts.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-1677889812985484580</guid><pubDate>Sun, 18 Mar 2012 20:26:00 +0000</pubDate><atom:updated>2012-03-18T15:33:24.684-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Quotes</category><title>Quotes</title><atom:summary>“Luck favors the prepared mind only” - Louis Pasteur ”Success and rest don’t sleep together. “- Russian proverb ”About motivate problematic people:  create a rich picture, reframe your goals, stage the encounter” “Reasonable people adapt themselves to the world. Unreasonable people attempt to adapt the world to themselves. All progress, therefore, depends on unreasonable people.”— George Bernard </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/DDnZS0jhJmI/quotes.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/DDnZS0jhJmI" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/03/quotes.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-3957474428909178521</guid><pubDate>Sun, 18 Mar 2012 20:11:00 +0000</pubDate><atom:updated>2012-03-18T15:11:04.636-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Design</category><title>Architecture</title><atom:summary>Architecture is about looking at a system from a point of view that makes it appear simple, sometimes artificially so. It provides a way of looking at the "conceptual essence" of something without getting bogged down in every detail. An architectural viewpoint  It has to be simple to understand, to describe, to compare with other viewpoints, and, ultimately, to implement.The viewpoint might seek </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/5TkEQu3z1xM/architecture.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/5TkEQu3z1xM" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/03/architecture.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-5820713886729249403</guid><pubDate>Sun, 18 Mar 2012 19:50:00 +0000</pubDate><atom:updated>2012-03-18T14:50:36.011-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Presentations</category><title>Made to Stick: Why Some Ideas Survive and Others Die–Extracts</title><atom:summary>Source: Made To Stick Making your ideas sticky What's my point? And why does it matter? If your audience remembers only one thing, what should it be? Process for making your ideas stickier   Identify the central message you need to communicate—find the core;  Figure out what is counterintuitive about the message —i.e., What are the unexpected implications of your core message? Why isn't it </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/0m6tlMQuyXA/made-to-stick-why-some-ideas-survive.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/0m6tlMQuyXA" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/03/made-to-stick-why-some-ideas-survive.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-7464721251925987520</guid><pubDate>Mon, 30 Jan 2012 19:08:00 +0000</pubDate><atom:updated>2012-01-30T14:08:34.248-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Mythical Man-Month – Extracts VII</title><atom:summary>Source: The Mythical Man-Month Importance of Milestones  in Big Projects How does one control a big project on a tight schedule? The first step is to have a schedule. Each of a list of events, called milestones, has a date. Picking the dates is an estimating problem, discussed already and crucially dependent on experience. For picking the milestones there is only one relevant rule. Milestones </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/HPHAWWCgFgY/mythical-man-month-extracts-vii.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/HPHAWWCgFgY" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2012/01/mythical-man-month-extracts-vii.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-1589196360218708426</guid><pubDate>Thu, 06 Oct 2011 03:38:00 +0000</pubDate><atom:updated>2011-10-05T22:38:44.050-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Mythical Man-Month – Extracts VI</title><atom:summary>Source: The Mythical Man-Month Communication in the Large Programming Project Schedule disaster, functional misfits, and system bugs all arise because the left hand doesn't know what the right hand is doing. As work proceeds, the several teams slowly change the functions, sizes, and speeds of their own programs, and they explicitly or implicitly change their assumptions about the inputs available</atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/CkAvQXteJRk/mythical-man-month-extracts-vi.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/CkAvQXteJRk" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/10/mythical-man-month-extracts-vi.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-3881590484755567171</guid><pubDate>Wed, 05 Oct 2011 03:12:00 +0000</pubDate><atom:updated>2011-10-04T22:17:07.939-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">JavaScript</category><title>JavaScript II - Expressions and Operators</title><atom:summary>About Arrays, Objects and FunctionsObject Creation Expressionsnew Object()
new Point(2,3)
If no arguments are passed to the constructor function in an object creation expression, the empty pair of parentheses can be omitted:
new Object
new Date
Object and Array InitializersObject and array initializers are expressions whose value is a newly created object or array.
var arrayOfArrays = [[1,2], [3]</atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/rX4Bb1gr-10/javascript-ii-expressions-and-operators.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/rX4Bb1gr-10" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/10/javascript-ii-expressions-and-operators.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-3673862132044510074</guid><pubDate>Fri, 30 Sep 2011 03:12:00 +0000</pubDate><atom:updated>2011-09-29T22:18:46.064-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Mythical Man-Month – Extracts V</title><atom:summary>Source: The Mythical Man-Month Ensuring that everyone hears, understands, and implements the architects' decisions A whole technology for doing this was worked out for the System/360 hardware design effort, and it is equally applicable to software projects.  Written Specifications—the Manual The manual, or written specification, is a necessary tool, though not a sufficient one. The manual is the </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/dm5r4WqkhJE/mythical-man-month-extracts-v.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/dm5r4WqkhJE" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/09/mythical-man-month-extracts-v.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-3397135819147899337</guid><pubDate>Fri, 30 Sep 2011 01:00:00 +0000</pubDate><atom:updated>2011-09-29T20:00:20.722-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Mythical Man-Month – Extracts IV</title><atom:summary>Source: The Mythical Man-Month Architect - Needed Disciplines Having in mind that we have separated responsibility for functional specification (Architect) from responsibility for building a fast, cheap product (Builder), now we have to answer the question of: how we will achieve the best outcome of our project? The fundamental answer is thoroughgoing, careful, and sympathetic communication </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/aGedoJ9WZgg/mythical-man-month-extracts-iv.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/aGedoJ9WZgg" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/09/mythical-man-month-extracts-iv.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-1853617870326335909</guid><pubDate>Mon, 19 Sep 2011 02:10:00 +0000</pubDate><atom:updated>2011-09-18T21:25:10.528-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">JavaScript</category><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>JavaScript I - Initial Concepts</title><atom:summary>Basic Information  JavaScript is a case-sensitive language. Many client-side JavaScript objects and properties have the same names as the HTML tags and attributes they represent. While these tags and attribute names can be typed in any case in HTML, in JavaScript they typically must be all lowercase.  JavaScript’s strings (and its arrays) use zero-based indexing.  When the JavaScript interpreter </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/YTfAYn4jt5o/javascript-i-initial-concepts.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/YTfAYn4jt5o" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/09/javascript-i-initial-concepts.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-6251156358855291621</guid><pubDate>Sun, 18 Sep 2011 01:04:00 +0000</pubDate><atom:updated>2011-09-17T20:09:46.230-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Mythical Man-Month – Extracts III</title><atom:summary>Source: The Mythical Man-Month Conceptual Integrity I will contend that conceptual integrity is the most important consideration in system design. It is better to have a system omit certain anomalous features and improvements, but to reflect one set of design ideas, than to have one that contains many good but independent and uncoordinated ideas. Unfortunately most programming systems reflect big</atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/RNpUH6CU4Fs/mythical-man-month-extracts-iii.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/RNpUH6CU4Fs" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/09/mythical-man-month-extracts-iii.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-9171312457678169395</guid><pubDate>Fri, 09 Sep 2011 03:11:00 +0000</pubDate><atom:updated>2011-09-08T22:11:22.933-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Mythical Man-Month – Extracts II</title><atom:summary>Source: The Mythical Man-Month How to take forward really big projects Small sharp team concept is not a viable solution because it is too slow. So we have to find other options. The dilemma  For efficiency and conceptual integrity, one prefers a few good minds doing design and construction. For large systems one wants a way to bring considerable manpower to bear, so that the product can make a </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/Al4IoHqYD5c/mythical-man-month-extracts-ii.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/Al4IoHqYD5c" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/09/mythical-man-month-extracts-ii.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-8041023003758529532</guid><pubDate>Sat, 03 Sep 2011 20:24:00 +0000</pubDate><atom:updated>2011-09-03T15:24:59.656-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Mythical Man-Month – Extracts I</title><atom:summary>Source: The Mythical Man-Month Identifying the joys and woes inherent to the system programming. The Joys of the Craft Following we can find some answers to the questions:  Why is programming fun? What delights may its practitioner expect as his reward?  The sheer joy of making things.  The pleasure of making things that are useful to other people.  The fascination of fashioning complex </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/3SUC-hLKLJQ/mythical-man-month-extracts-i.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/3SUC-hLKLJQ" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/09/mythical-man-month-extracts-i.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-6867307831680918234</guid><pubDate>Fri, 19 Aug 2011 02:34:00 +0000</pubDate><atom:updated>2011-08-18T21:34:52.617-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Writing</category><title>Ideas into Words – Extracts III</title><atom:summary>Source: Ideas into Words Refining Your Draft Before you start refining, do whatever will freshen your view of the manuscript. At a minimum, take a break and print out the manuscript.  After your break, proceed as if you had never seen the manuscript before. The idea is to approximate an outsider’s clear view of the piece as it stands. Next do the following things: Read at cruising speed  and jot </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/PNYtwjJ46iU/ideas-into-words-extracts-iii.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/PNYtwjJ46iU" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/08/ideas-into-words-extracts-iii.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-8353315932584736158</guid><pubDate>Thu, 18 Aug 2011 19:06:00 +0000</pubDate><atom:updated>2011-08-18T14:11:55.509-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Writing</category><title>Ideas into Words – Extracts II</title><atom:summary>Source : Ideas into Words Creating your first draft Following you can find some advices to create your first draft As you write, keep your eye on the ball I borrowed the sporty image in this mixaphor, hackneyed though it is, because in sports we all know it’s true (which is how it got hackneyed). It is hard enough to hit a tennis ball streaking toward you at 118 miles an hour. It cannot be done </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/VIOv0UT_sO0/ideas-into-words-extracts-ii-creating.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/VIOv0UT_sO0" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/08/ideas-into-words-extracts-ii-creating.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-6894714786897135959</guid><pubDate>Thu, 11 Aug 2011 03:38:00 +0000</pubDate><atom:updated>2011-08-10T22:38:36.668-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Writing</category><title>Ideas into Words – Extracts I</title><atom:summary>Source: Ideas into Words Main Advice Whenever you get stuck while writing, stop struggling. Close your eyes, visualize a specific, living, breathing reader, and say to yourself, “What am I really trying to say?” Whatever the answer, write it down. Polish later if it’s needed, but you may be surprised at how trivial the polishing can be. Getting Started The first things that you have to do are: </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/wJf0VB5P23E/ideas-into-words-extracts-i.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/wJf0VB5P23E" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/08/ideas-into-words-extracts-i.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-801836798041214633</guid><pubDate>Sat, 02 Jul 2011 21:44:00 +0000</pubDate><atom:updated>2011-07-02T16:44:05.277-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Programming</category><title>The Clean Coder–Extracts</title><atom:summary>Source: The Clean Coder: A Code of Conduct for Professional Programmers About software projects The fundamental assumption underlying all software projects is that software is easy to change.If you violate this assumption by creating inflexible structures, then you undercut the economic model that the entire industry is based on. Professionals spend time caring for their profession. You should </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/4_2lZEcooA4/clean-coderextracts.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/4_2lZEcooA4" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/07/clean-coderextracts.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-6248347753650419279</guid><pubDate>Thu, 30 Jun 2011 16:37:00 +0000</pubDate><atom:updated>2011-07-02T12:58:42.515-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Quotes</category><title>Quotes</title><atom:summary>“Only connect!... Only connect the prose and the passion, and both will be exalted, and human love will be seen at its height.” - E. M. Forster "Man can be destroyed, but not defeated" – Hemingway "Living a life of defeat is death and a death with dignity is life."  "All happy families resemble each other, but each unhappy family is unhappy in its own way." – Tolstoy “Curiosity, happens when we </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/BaVVb41ELNI/quotes_30.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/BaVVb41ELNI" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/06/quotes_30.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-3261189686395182510</guid><pubDate>Wed, 29 Jun 2011 21:50:00 +0000</pubDate><atom:updated>2011-06-30T11:39:45.188-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Presentations</category><title>Points to take into account to prepare a presentation</title><atom:summary> Source: Confessions of a Public Speaker 1.- Take a strong position in the title.  All talks and presentations have a point of view, and you need to know what yours is. If you don’t know enough about the topic to have an opinion, solve that problem before you make your presentation. Even saying, “Here are five things I like” is a strong position, in that there are an infinite number of things you</atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/827Z1VqxVyw/points-to-take-into-account-to-prepare.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/827Z1VqxVyw" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/06/points-to-take-into-account-to-prepare.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7972942899684557472.post-1565135549868122419</guid><pubDate>Mon, 13 Jun 2011 18:59:00 +0000</pubDate><atom:updated>2011-06-13T13:59:27.221-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Quotes</category><title>Quotes</title><atom:summary>"I tell you that whether you fear it or not, disappointment will come.  The beauty is that through disappointment you can gain clarity, and with clarity comes conviction and true Originality" - Conan O'Brien  </atom:summary><link>http://feedproxy.google.com/~r/ApprenticeshipNotes/~3/lvNO0xJQFYI/quotes.html</link><author>noreply@blogger.com (Gamal Mateo)</author><thr:total>0</thr:total><description>&lt;img src="http://feeds.feedburner.com/~r/ApprenticeshipNotes/~4/lvNO0xJQFYI" height="1" width="1"/&gt;</description><feedburner:origLink>http://www.apprenticeshipnotes.org/2011/06/quotes.html</feedburner:origLink></item></channel></rss>
