<?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>Technical stuff &#187; Resources</title>
	<atom:link href="http://www.tekkie.ro/category/resources/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tekkie.ro</link>
	<description>Requirements are like water. They&#039;re easier to build on when they&#039;re frozen.</description>
	<lastBuildDate>Fri, 11 Jun 2010 11:33:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Checklist for the Agile Manager</title>
		<link>http://www.tekkie.ro/resources/checklist-for-the-agile-manager/</link>
		<comments>http://www.tekkie.ro/resources/checklist-for-the-agile-manager/#comments</comments>
		<pubDate>Thu, 28 May 2009 09:26:37 +0000</pubDate>
		<dc:creator>Georgiana</dc:creator>
				<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[presentation]]></category>
		<category><![CDATA[Software development processes]]></category>

		<guid isPermaLink="false">http://www.tekkie.ro/?p=171</guid>
		<description><![CDATA[To be a leader is not the next step for managers. It is the manager&#8217;s job to leave room to leaders.
Checklist for the Agile Manager
View more OpenOffice presentations from Jurgen Appelo.

]]></description>
			<content:encoded><![CDATA[<blockquote><p>To be a leader is <em>not</em> the next step for managers. It is the manager&#8217;s job to <em>leave room</em> to leaders.</p></blockquote>
<div id="__ss_1476474" style="width: 425px; text-align: left;"><a style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;" title="Checklist for the Agile Manager" href="http://www.slideshare.net/jurgenappelo/checklist-for-the-agile-manager?type=powerpoint">Checklist for the Agile Manager</a><object width="425" height="355" data="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=checklistfortheagilemanager-090522153628-phpapp01&amp;stripped_title=checklist-for-the-agile-manager" type="application/x-shockwave-flash"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=checklistfortheagilemanager-090522153628-phpapp01&amp;stripped_title=checklist-for-the-agile-manager" /><param name="allowfullscreen" value="true" /></object></p>
<div style="font-size: 11px; font-family: tahoma,arial; height: 26px; padding-top: 2px;">View more <a style="text-decoration:underline;" href="http://www.slideshare.net/">OpenOffice presentations</a> from <a style="text-decoration:underline;" href="http://www.slideshare.net/jurgenappelo">Jurgen Appelo</a>.</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.tekkie.ro/resources/checklist-for-the-agile-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The PHP code conventions I use</title>
		<link>http://www.tekkie.ro/resources/the-php-code-conventions-i-use/</link>
		<comments>http://www.tekkie.ro/resources/the-php-code-conventions-i-use/#comments</comments>
		<pubDate>Fri, 22 May 2009 13:42:57 +0000</pubDate>
		<dc:creator>Georgiana</dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[code conventions]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.tekkie.ro/?p=166</guid>
		<description><![CDATA[

&#60;?php
// Did you notice the full-style opening PHP tags?

/**************************************************************
 * Variable Naming conventions
 *************************************************************
 * - Use data type as prefix inside the name
 *          Eg: $sName instead of just $name
 * - Try to use as descriptive names as possible
 *     [...]]]></description>
			<content:encoded><![CDATA[<pre class="brush: php">

&lt;?php
// Did you notice the full-style opening PHP tags?

/**************************************************************
 * Variable Naming conventions
 *************************************************************
 * - Use data type as prefix inside the name
 *          Eg: $sName instead of just $name
 * - Try to use as descriptive names as possible
 *         Eg: $arProductList instead of just $arList
 **************************************************************/

/**************************************************************
 * Basic Datatypes conventions
 **************************************************************/

// Strings
$sName = &quot;tekkie.ro&quot;;

// Integers
$iYear = 2004;

// Floats
$fAccountValue = 12.34;

// Booleans
$bCheck = true;

// Objects
$oProduct = new Product( $iProductId );

// Arrays
$aProperties = array (&#039;1&#039;, &#039;2&#039;, &#039;3&#039;);

/**************************************************************
* Spacing convention
**************************************************************/

$iSum = $iNumber1 + $iNumber2;
$sSum = $iNumber1 . $iNumber2; // space dot space before and after a variable
$sSum = &#039; Here we add a number &#039; . $iNumber1; // quote space dot space after a string
$sSum = $iNumber2 . &#039; Here we add a number &#039;; // space dot space quote before a string

/*
* Function definition convention
*
* A comment describing the function should precede its declaration.
* Begin with a slash followed by two stars.
* Give a one-line function synopsis, then a brief explanation.
*/

/**
 * bool hasPrices (obj oProduct [, bool bAlwaysTrue])
 *
 * @param Product the product we chack for prices
 * @param boolean
 * @return true if the Product has prices, false otherwise
*/

function hasPrices( $oProduct, $bAlwaysTrue = false ) {
    if ($bAlwaysTrue) return true;
    foreach ($oProduct-&gt;aProperties as $sProperty ) {
        if( &#039;price&#039; === $sProperty ) {  // use === as often as possible; put the string first for speed reasons
            return( true );
        } // .. if
    }
    return( false );
} // END func hasPrices()

/*
 * echo tag
 */

define (CR, &quot;\n&quot;);

echo 

	CR, &#039;Line1&lt;br /&gt;&#039;,

	CR, &#039;Line2&lt;br /&gt;&#039;,

	CR, &#039;Line3&lt;br /&gt;&#039;
;

/**************************************************************
 * Spacing convention
 **************************************************************/

// Code like this:

$sText = &#039;Time flies like an arrow.&#039;;
$sText .= &#039; Fruit flies like bananas.&#039;;

// Should be done in one statement instead of two:

$sText =
    &#039;Time flies like an arrow.&#039; .
    &#039; Fruit flies like bananas.&#039;
;

?&gt;
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.tekkie.ro/resources/the-php-code-conventions-i-use/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>PHP on Hormones: Rasmus Lerdorf talk</title>
		<link>http://www.tekkie.ro/resources/php-on-hormones-rasmus-lerdorf-talk/</link>
		<comments>http://www.tekkie.ro/resources/php-on-hormones-rasmus-lerdorf-talk/#comments</comments>
		<pubDate>Thu, 18 Dec 2008 10:26:09 +0000</pubDate>
		<dc:creator>Georgiana</dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[tekkies]]></category>

		<guid isPermaLink="false">http://www.tekkie.ro/?p=78</guid>
		<description><![CDATA[Rasmus Lerdorf from Yahoo! talks at MySQL Conference &#38; Expo 2007. Starts with the beginning of PHP and continues to more advances stuff.
Make sure you have the slides handy, too.

Spaghetti code, otherwise known as Drupal.
]]></description>
			<content:encoded><![CDATA[<p><a title="Rasmus Lerdorf resume" href="http://lerdorf.com/resume/">Rasmus Lerdorf</a> from Yahoo! talks at MySQL Conference &amp; Expo 2007. Starts with the beginning of PHP and continues to more advances stuff.</p>
<p>Make sure you <a title="PHP on Hormones: MySQL Conference slides" href="http://talks.php.net/show/mysql07key">have the slides handy</a>, too.</p>
<p><object width="320" height="270" data="http://blip.tv/play/AaGUe4a8EA" type="application/x-shockwave-flash"><param name="src" value="http://blip.tv/play/AaGUe4a8EA" /><param name="allowfullscreen" value="true" /></object></p>
<blockquote><p>Spaghetti code, otherwise known as Drupal.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.tekkie.ro/resources/php-on-hormones-rasmus-lerdorf-talk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Writing code is an art, not a simple day-job</title>
		<link>http://www.tekkie.ro/resources/writing-code-art-not-simple-day-job/</link>
		<comments>http://www.tekkie.ro/resources/writing-code-art-not-simple-day-job/#comments</comments>
		<pubDate>Mon, 01 Dec 2008 18:09:57 +0000</pubDate>
		<dc:creator>Georgiana</dc:creator>
				<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Resources]]></category>

		<guid isPermaLink="false">http://www.tekkie.ro/?p=57</guid>
		<description><![CDATA[If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.
Gerald Weinberg
Copy and paste is a design error.
David Parnas
 
Think about how you develop your own code.
Do you rush into writing a piece of code and use comments later, if you have any time left? Or do you [...]]]></description>
			<content:encoded><![CDATA[<blockquote><p>If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.</p></blockquote>
<p>Gerald Weinberg</p>
<blockquote><p>Copy and paste is a design error.</p></blockquote>
<p>David Parnas<br />
 </p>
<p>Think about how you develop your own code.</p>
<p>Do you rush into writing a piece of code and use comments later, if you have any time left? Or do you use a pseudocode approach by writing comments n the first place and then developing functionality to implement that?</p>
<p>Do you develop code in such a way that it can be later tested and mainained? Or do you write it, prove &#8220;it works&#8221; and think about it next time you have to adjust functionality?</p>
<p>Do you favor speed for maintainability?</p>
<p>These are the lessons one learns while reading <a title="Code Complete, A Practical Handbook of Software Construction" href="http://www.amazon.com/Code-Complete-Practical-Handbook-Construction/dp/0735619670">Code Complete</a>, a book which aims to learn you how to do stuff <strong>right</strong>, not &#8220;just do it&#8221;. I like it more and more while I&#8217;m reading it. Most of the examples present common-sense development, yet I&#8217;ve seen so much poor code which does the job that I would like to reccommend it to all software developers. If you do read it, I can only promise it&#8217;ll make you a better colleague than you already might be.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tekkie.ro/resources/writing-code-art-not-simple-day-job/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JavaScript for PHP developers</title>
		<link>http://www.tekkie.ro/resources/javascript-for-php-developers/</link>
		<comments>http://www.tekkie.ro/resources/javascript-for-php-developers/#comments</comments>
		<pubDate>Wed, 29 Oct 2008 18:54:42 +0000</pubDate>
		<dc:creator>Georgiana</dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.tekkie.ro/?p=44</guid>
		<description><![CDATA[If you're a PHP developer and you find it difficult to get used to all the insides of JavaScript, you might need PHP.JS, developed by Kevin van Zonneveld.]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re a PHP developer and you find it difficult to get used to all the insides of JavaScript, I think you need to take a look at <a href="http://phpjs.org/">PHP.JS</a>. It&#8217;s a brilliant tool initially developed by <a href="http://kevin.vanzonneveld.net/about/">Kevin van Zonneveld</a>, and which aims to port most of the usual PHP functions into equivalent JavaScript ones.</p>
<p>There are two ways of using this excellent codebase:</p>
<ul>
<li>grab all the <a title="one file containing all the available PHP.Js functions" href="http://kevin.vanzonneveld.net/code/php_equivalents/php.js">available PHP.JS functions</a> and use them as you need them</li>
<li>take each function you really need and put it into your JS codebase for the project</li>
</ul>
<p>The advantage of the second method is that you don&#8217;t have code you don&#8217;t need included all over the place, but it also means you will search each time the codebase to discover the code you need. Meanwhile, the first solution seems appropriate for the ones in a hurry, you just try to use one function like you&#8217;re accustomed in PHP and it&#8217;s there already included, you&#8217;re developing fast and safe, with just a small performance issue you can always address later.</p>
<p>Let&#8217;s say you&#8217;ve using the <a title="PHP long2ip function manual page" href="http://php.net/long2ip">long2ip</a> and <a title="PHP ip2long function manual page" href="http://www.php.net/ip2long">ip2long</a> PHP functions for storing IPs as numbers, and have a strong preference for using them for performance reasons, as all your IPs are stored as numbers in the database. What if you need similar functionality in JavaScript? Well, just <a title="PHP.JS long2ip function" href="http://phpjs.org/functions/long2ip:48e4b52c-c26c-4ba7-84f0-2d6486a786ee">take the code</a> <a title="PHP.JS ip2long function" href="http://phpjs.org/functions/ip2long:48e4b52b-3860-4f6c-830b-2d6486a786ee">you need</a> and use it! It&#8217;s that simple <img src='http://www.tekkie.ro/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.tekkie.ro/resources/javascript-for-php-developers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Collaborative online task tracker &#8211; free</title>
		<link>http://www.tekkie.ro/resources/collaborative-online-task-tracker-free/</link>
		<comments>http://www.tekkie.ro/resources/collaborative-online-task-tracker-free/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 14:39:16 +0000</pubDate>
		<dc:creator>Georgiana</dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[online tools]]></category>

		<guid isPermaLink="false">http://www.tekkie.ro/?p=20</guid>
		<description><![CDATA[free online issue tracking system, with minimal set of features: No Kahuna]]></description>
			<content:encoded><![CDATA[<p>Every project, be it small, medium or large, needs tracking down its status and pieces of work / research. A team of people will bring the project to completion, so even if the team has only one member, a way of tracking down its status and work left is extremely important for having always a quick and accurate overview.</p>
<p>For managing small projects, I have found a nice <a href="http://nokahuna.com/" alt="Website of No Kahuna">collaborative task tracker</a> with minimal features. It allows for setting up projects, creating tasks, distributing them and tracking them down for completion.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tekkie.ro/resources/collaborative-online-task-tracker-free/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to be a programmer</title>
		<link>http://www.tekkie.ro/resources/how-to-be-a-programmer/</link>
		<comments>http://www.tekkie.ro/resources/how-to-be-a-programmer/#comments</comments>
		<pubDate>Sat, 27 Sep 2008 15:22:08 +0000</pubDate>
		<dc:creator>Georgiana</dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[personal skills]]></category>

		<guid isPermaLink="false">http://www.tekkie.ro/?p=18</guid>
		<description><![CDATA[Resource: "How to be a Programmer" by Robert Read]]></description>
			<content:encoded><![CDATA[<p>A <a title="How to be a Programmer by Robert Read" href="http://samizdat.mines.edu/howto/HowToBeAProgrammer.html" target="_blank">good book</a> on what it means to be a programmer and how you cand improve your abilities.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tekkie.ro/resources/how-to-be-a-programmer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
