<?xml version="1.0" encoding="UTF-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>TechTrouts.com &#187; management</title>
	<atom:link href="http://techtrouts.com/topics/management/feed/" rel="self" type="application/rss+xml" />
	<link>http://techtrouts.com</link>
	<description>Doin' the dev dance o/</description>
	<lastBuildDate>Thu, 23 Jul 2009 10:42:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Application deployment shell script using rsync</title>
		<link>http://techtrouts.com/application-deployment-shell-script-using-rsync/</link>
		<comments>http://techtrouts.com/application-deployment-shell-script-using-rsync/#comments</comments>
		<pubDate>Thu, 07 May 2009 22:14:07 +0000</pubDate>
		<dc:creator>Carlos Ouro</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[servers]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://techtrouts.com/application-deployment-shell-script-using-rsync/</guid>
		<description><![CDATA[Hi all, here is a simple deployment shell script (.sh) using rsync to deploy your local application to a productive location. You can download it here. Follow the README file for setup and usage. Feedback comments are always welcome :)]]></description>
			<content:encoded><![CDATA[<p>Hi all,</p>
<p>here is a simple deployment shell script (.sh) using rsync to deploy your local application to a productive location.</p>
<p>You can download it <a href="http://techtrouts.com/downloads/deploy_sh.zip" title="Application deployment shell script using rsync">here</a>.</p>
<p>Follow the README file for setup and usage.</p>
<p>Feedback comments are always welcome :)</p>
]]></content:encoded>
			<wfw:commentRss>http://techtrouts.com/application-deployment-shell-script-using-rsync/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What about backward compatibility modules?</title>
		<link>http://techtrouts.com/what-about-backward-compatibility-modules/</link>
		<comments>http://techtrouts.com/what-about-backward-compatibility-modules/#comments</comments>
		<pubDate>Sat, 21 Jun 2008 18:32:53 +0000</pubDate>
		<dc:creator>Carlos Ouro</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[how-tos]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[mootools]]></category>
		<category><![CDATA[naturePhp]]></category>
		<category><![CDATA[opinion]]></category>

		<guid isPermaLink="false">http://techtrouts.com/what-about-backward-compatibility-modules/</guid>
		<description><![CDATA[Hi again, being working a lot with mootools, dojo, wordpress and some other frameworks and toolkits lately, my question today is this: Why, most of the times, don&#8217;t frameworks and toolkits developers launch any backward compatibility modules at all? It might seem pretty complicated getting old deprecated funcionalities working  on newer, better versions, but, apart [...]]]></description>
			<content:encoded><![CDATA[<p>Hi again,</p>
<p>being working a lot with <a href="http://mootools.net/" title="MooTools - a compact javascript framework">mootools</a>, <a href="http://dojotoolkit.org/" title="The Dojo Toolkit" target="_blank">dojo</a>, <a href="http://wordpress.org/" title="WordPress › Blog Tool and Weblog Platform" target="_blank">wordpress</a> and some other frameworks and toolkits lately, my question today is this:<br />
Why, most of the times, don&#8217;t frameworks and toolkits developers launch any <a href="http://en.wikipedia.org/wiki/Backward_compatibility" title="Backward compatibility - Wikipedia, the free encyclopedia" target="_blank">backward compatibility</a> modules at all?</p>
<p>It might seem pretty complicated getting old deprecated funcionalities working  on newer, better versions, but, apart from some real specific embembed funcionalities, it really shouldn&#8217;t be that hard.</p>
<p>For the following example i&#8217;ll use Mootools as an explanatory example:</p>
<p>All you need is a nicely designed dynamic version transitioning system.<br />
One that allows you to, anytime on the execution, define which version will the following code run on.</p>
<p>Imagine you design a backward compatibility plugin from version B to version A.<br />
On version C you&#8217;ll design a backward compatibility plugin to version B.</p>
<p>So now, on a page running &#8220;mootools-C.js&#8221; you should include the backward compatibility modules &#8220;mootools-back-C-B.js&#8221; and &#8220;mootools-back-B-A.js&#8221;, or a compiled version (having just a copy paste of both previous files content) &#8220;mootools-back-C-to-A.js&#8221;.</p>
<p>So if you run something like &#8220;Mootools.use_version(&#8216;A&#8217;);&#8221; the dynamic version transitioning system would automatically look for it&#8217;s previous version compatilities execution for version B at, let&#8217;s suppose, &#8220;MootoolsBack_C_B();&#8221; and then rerun the same command (&#8220;Mootools.use_version(&#8216;A&#8217;);&#8221;) while already running on version B to travel back to version A (the dynamic version transitioning system, already on version B would run something like &#8220;MootoolsBack_B_A();&#8221;).</p>
<p>This method would, in theory, work for multiple version transitions without having to design a specific plugin for each version to version compatibility. It would save developers hours in trying to put two different tools, based on two different framework/toolkit versions, together on the same execution &#8211; like using both <a href="http://www.e-magine.ro/web-dev-and-design/41/moodalbox_1_3_b2/" title="MOOdalBox 1.3 is now cooking (Beta 2 is here)" target="_blank">MOOdalbox 1.3 beta 2</a> and <a href="http://www.outcut.de/MooFlow/" title="Mooflow (aka Coverflow)" target="_blank">mooflow v0.2</a> in the same page.</p>
<p>The system would work both ways, as you could &#8220;Mootools.version_reset();&#8221; or &#8220;Mootools.use_version(&#8216;C&#8217;);&#8221; to travel back to version C on the rest of the execution, the system would run the consecutive version travel functions eg. &#8220;MootoolsBack_A_B();&#8221; and &#8220;MootoolsBack_B_C();&#8221; and the rest of the code would be running on Mootools version C.</p>
<p>This &#8220;dynamic version transitioning system&#8221; will be used for every release transition on <a href="http://naturephp.org/" title="NaturePhp - An Open Source Natural PHP Toolkit" target="_blank">NaturePhp</a>.<br />
It might not work perfectly at first, but it will certainly relieve many developers&#8217; headaches.</p>
<p>I hope in the future more and more projects start using a system like this.</p>
]]></content:encoded>
			<wfw:commentRss>http://techtrouts.com/what-about-backward-compatibility-modules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My new daily routine</title>
		<link>http://techtrouts.com/my-new-daily-routine/</link>
		<comments>http://techtrouts.com/my-new-daily-routine/#comments</comments>
		<pubDate>Wed, 14 May 2008 14:27:47 +0000</pubDate>
		<dc:creator>Carlos Ouro</dc:creator>
				<category><![CDATA[life]]></category>
		<category><![CDATA[management]]></category>

		<guid isPermaLink="false">http://techtrouts.com/my-new-daily-routine/</guid>
		<description><![CDATA[Hi, Since we started 9tree i&#8217;ve began a wonderful daily routine, which i recommend to all who might read this. 8:30 AM : Wakeup I usually take about 15 mins to get up + 5 mins do get ready and 10 mins to arrive at Cartaxo so i set my alarm clock to 8:30 . [...]]]></description>
			<content:encoded><![CDATA[<p>Hi,</p>
<p>Since we started <a href="http://9tree.net" title="9tree - Natural Revolution for the Web" target="_blank">9tree</a> i&#8217;ve began a wonderful daily routine, which i recommend to all who might read this.</p>
<h3>8:30 AM : Wakeup</h3>
<p>I usually take about 15 mins to get up + 5 mins do get ready and 10 mins to arrive at Cartaxo so i set my alarm clock to 8:30 .</p>
<h3>9:00 AM : Daily sports</h3>
<p>This one has completely changed my life. I was used to drive 1 hour to work (about 43 miles) and having to go through Lisbon&#8217;s heavy traffic in the morning.<br />
Now i wake up every morning with a smile because i&#8217;m not going to drive long, not get into traffic and i&#8217;m not even going to work &#8211; i&#8217;m going to play soccer or basketball, maybe some tennis or a swim. Believe me, i now almost prefer weekdays to weekends.</p>
<h3>10:00 AM : Bath &amp; Breakfeast</h3>
<p>Ahhh the cold 10 mins shower after sweating &#8211; so fine.<br />
And a big breakfast to calm your stomach.</p>
<h3>10:30  AM : Arriving at work, read/answer the emails</h3>
<p>Arriving to work is supposed to be the boring part right? not quite.<br />
Nobody here actually works upon arrival, we start by saying hi to everyone at work discussing the daily news, reading emails, setting to-dos, etc.</p>
<h3>11:00 AM : Work a while</h3>
<p>Now we work.<br />
Layout design, cool new features, some open source development or old fashioned system administration.<br />
We get it done.</p>
<h3>12:30 PM : Lunch time!</h3>
<p>Food! :D</p>
<h3>2:00 PM : Read the news, write a post!</h3>
<p>I usually read <a href="http://slashdot.org" target="_blank" title="Slashdot: News for nerds, stuff that matters">slashdot</a>, portuguese news on <a href="http://www.publico.clix.pt/" title="PUBLICO.PT" target="_blank">publico</a> and the latest comic on <a href="http://explosm.net" title="Explosm! - Flash Animations, Daily Comics, and more! @ Explosm.net">explosm</a> .<br />
A post doesn&#8217;t come around every day, but i try to post as often as possible.</p>
<h3>2:30 PM : Worktime</h3>
<p>Main worktime starts here.</p>
<h3>4:00 PM : The pause</h3>
<p>Have a coffe, a smoke and a talk with friend&#8217;s from work.</p>
<h3>4:15 PM : Back to work!</h3>
<p>Work continues.</p>
<h3>7:30 PM : Go home or work late.</h3>
<p>Here we usually make a choice depending on our moods. Sometimes we stay, sometimes we go.</p>
<h3>8:00 PM : Dinner!</h3>
<p>Ahhhh more food! :D</p>
<h3>9:30 PM : Coffee with friends :)</h3>
<p>Going out with friend&#8217;s for a coffee and chat is a must have.<br />
When you don&#8217;t feel like it &#8211; how about a movie? latest Lost episode?</p>
<h3>12:00 AM : Go to sleep :o</h3>
<p>Another of my favorites :)</p>
<p>See you tomorrow ;)</p>
]]></content:encoded>
			<wfw:commentRss>http://techtrouts.com/my-new-daily-routine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to create a company</title>
		<link>http://techtrouts.com/how-to-create-a-company/</link>
		<comments>http://techtrouts.com/how-to-create-a-company/#comments</comments>
		<pubDate>Sat, 22 Mar 2008 13:40:27 +0000</pubDate>
		<dc:creator>Carlos Ouro</dc:creator>
				<category><![CDATA[management]]></category>
		<category><![CDATA[9tree]]></category>
		<category><![CDATA[company]]></category>

		<guid isPermaLink="false">http://techtrouts.com/how-to-create-a-company/</guid>
		<description><![CDATA[Here&#8217;s a little stress free guide on how to create the company you&#8217;ve always dreamed of. This is basically how we&#8217;ve created 9tree Step 1: Get the idea Well, this is actually not a step, but an event. It can happen anywhere, with anyone, anyhow. The idea should be independent, not forced. You do not [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a little stress free guide on how to create the company you&#8217;ve always dreamed of.<br />
This is basically how we&#8217;ve created <a href="http://9tree.net" title="9tree - Natural Revolution for the Web" target="_blank">9tree</a></p>
<h4><strong>Step 1</strong>: Get the idea</h4>
<p>Well, this is actually not a step, but an event.<br />
It can happen anywhere, with anyone, anyhow. The idea should be independent, not forced. You do not &#8220;sit and get an idea&#8221;, it rarely works this way.<br />
Best ideas come from getting together and speaking with friend&#8217;s/colleagues, idling in the couch, walking around the streets in the afternoon or when your trying to sleep at night.<br />
You probably already have lot&#8217;s of these ideas.</p>
<h4><strong>Step 2</strong>: Ask around/Talk about it</h4>
<p>Many people don&#8217;t share this opinion, but i always talk about my ideas with most of my friend&#8217;s and/or colleagues, even in single projects. I try not to live by the &#8220;what if they use my idea&#8221; policy that strangles most of us these days.<br />
Maybe i just have good friends or trust a lot, but it works fine most times, and the few times it goes bad serve as a lesson in who not to trust.<br />
Anyhow the feedback is great, my ideas get clearer, i find most of the downsides initially covered by the illusion of greatness, and work them around right from the beginning.<br />
People around me are an essential part of my ideas.</p>
<h4><strong>Step 3</strong>: Mind up</h4>
<p>Ok, now think about it.<br />
How much do you like it? Is it too risky? Is it worth it? Can you do it?<br />
Answer these within you must.<br />
Then let it flow: &#8220;i can do it, i want to do it, i&#8217;ll do it!&#8221;.</p>
<h4><strong>Step 4</strong>: Get name(s)</h4>
<p>One of the hardest steps imho.<br />
Our process involved many days of wandering around trying to get nice ideas, stickers on the forehead with a bunch of words we liked and a few rounds of <a href="http://en.wikipedia.org/wiki/Jan-ken-pon" title="Jan-ken-pon's definition" target="_blank">Jan-ken-pon</a> (rock-paper-scissor).<br />
In the end we came up with a list of six names and a first choice &#8211; 9tree.</p>
<h4><strong>Step 5</strong>: Get into it!</h4>
<p>Prospect you market, start preparing your projects, get the tools, work for some test run clients. Freelance into it.<br />
This is a critical control point in the process. It will show you if you can really do it, how good is your work, how well you and your partner(s) get along, company potencial, etc.</p>
<h4><strong>Step 6</strong>:Final decision</h4>
<p>This is where you sit down and talk/think about all of it. Upsides, downsides, realities, illusions.<br />
Think straight,  look around, set, go! After this there is hardly any turning back.</p>
<h4><strong>Step 7</strong>: Plan ahead</h4>
<p>Make a roadmap from here until your working at the company, timing is now the key to get everything working together.</p>
<h4><strong>Step 7</strong>: Get some money</h4>
<p>You need the funds to start the company and maintain it at least for a couple of months.<br />
Use your spared money, lone, ask your mom and dad, whatever.</p>
<h4><strong>Step 8</strong>: Get an office</h4>
<p>Preferably close to home, calm, spacy and with outer windows.</p>
<h4><strong>Step 9</strong>: Quit your job</h4>
<p>That&#8217;s it, quit the job.</p>
<h4><strong>Step 10</strong>: Scary legal stuff</h4>
<p>Name registration, company creation, accountant, bla, bla, bla&#8230;</p>
<h4><strong>Step 11</strong>: Buy stuff :D</h4>
<p>This is the coolest part. Buy the desks, pens, macs, some nice paintings, comfortable chairs, maybe a service car&#8230; whatever you stated you needed in the &#8220;Plan ahead&#8221; part.</p>
<h4><strong>Step 12</strong>: Get to work ;)</h4>
<p>Well, this is it, get up early, make some exercise, go to work.<br />
Don&#8217;t work too much, don&#8217;t piss people off, get some air once in while, get social every couple of days, take care of your family.</p>
<p>You&#8217;ll be fine :)</p>
]]></content:encoded>
			<wfw:commentRss>http://techtrouts.com/how-to-create-a-company/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
