<?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/" xmlns:series="http://unfoldingneurons.com/" ><channel><title>BrandonSavage.net &#187; Business Management</title> <atom:link href="http://www.brandonsavage.net/category/business-management/feed/" rel="self" type="application/rss+xml" /><link>http://www.brandonsavage.net</link> <description>The personal blog of Brandon Savage. Contains entries of a personal and professional nature focusing on PHP, Apple, LAMP, MySQL and Washington, DC.</description> <lastBuildDate>Wed, 28 Jul 2010 15:28:37 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <item><title>Painless Spec and Schedule Development</title><link>http://www.brandonsavage.net/painless-spec-and-schedule-development/</link> <comments>http://www.brandonsavage.net/painless-spec-and-schedule-development/#comments</comments> <pubDate>Wed, 16 Dec 2009 06:00:09 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Best Practices]]></category> <category><![CDATA[Business Management]]></category> <category><![CDATA[development]]></category> <category><![CDATA[schedule writing]]></category> <category><![CDATA[scheduling]]></category> <category><![CDATA[spec]]></category> <category><![CDATA[specification]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=1094</guid> <description><![CDATA[In the time that I have developed software, I don&#8217;t know that I&#8217;ve ever met a developer who got excited about writing specs for anything. In fact, most developers loathe writing specs, or developing schedules of any kind. It&#8217;s not that they&#8217;re lazy, or that they don&#8217;t want to be held accountable; most of the [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/painless-spec-and-schedule-development/feed/</wfw:commentRss> <slash:comments>4</slash:comments> <series:name><![CDATA[Applying The Joel Test In The Real World]]></series:name> </item> <item><title>Announcing Blueprint DC</title><link>http://www.brandonsavage.net/announcing-blueprint-dc/</link> <comments>http://www.brandonsavage.net/announcing-blueprint-dc/#comments</comments> <pubDate>Mon, 30 Nov 2009 06:00:54 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Business Management]]></category> <category><![CDATA[blueprint dc]]></category> <category><![CDATA[business development]]></category> <category><![CDATA[new ventures]]></category> <category><![CDATA[starting a company]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=1062</guid> <description><![CDATA[Since being laid off last month, I&#8217;ve thought long and hard about what I wanted to do next. After consulting with my fiancee and with friends and colleagues, I decided that the best approach would be to begin working towards my own consulting company. And so, several weeks into the process, I&#8217;ve laid the groundwork [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/announcing-blueprint-dc/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> <item><title>Pair Programming: Where Teamwork Comes Out</title><link>http://www.brandonsavage.net/pair-programming-where-teamwork-comes-out/</link> <comments>http://www.brandonsavage.net/pair-programming-where-teamwork-comes-out/#comments</comments> <pubDate>Wed, 30 Sep 2009 05:00:03 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Business Management]]></category> <category><![CDATA[pair programming]]></category> <category><![CDATA[teamwork]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=783</guid> <description><![CDATA[The New York Times did a profile on the topic of pair programming, the art of writing software with a partner. They looked at it through the eyes of an individual who does pair programming every day. The profile is pretty good, and makes a strong case for pair programming. While I&#8217;m not fully prepared [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/pair-programming-where-teamwork-comes-out/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>Train Your Employees</title><link>http://www.brandonsavage.net/train-your-employees/</link> <comments>http://www.brandonsavage.net/train-your-employees/#comments</comments> <pubDate>Fri, 11 Sep 2009 05:00:30 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Business Management]]></category> <category><![CDATA[investment]]></category> <category><![CDATA[Microsoft]]></category> <category><![CDATA[R&D]]></category> <category><![CDATA[training]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=683</guid> <description><![CDATA[Last week, Cal Evans retweeted James McGovern, who originated this tweet: I&#8217;m not a fan of catchy sayings and one-line wonders, but this tweet got me thinking. How many companies, especially in the economic world we&#8217;re in, think about training as something that they don&#8217;t want to do, or an investment they can&#8217;t afford? There [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/train-your-employees/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Count The Costs</title><link>http://www.brandonsavage.net/count-the-costs/</link> <comments>http://www.brandonsavage.net/count-the-costs/#comments</comments> <pubDate>Fri, 07 Aug 2009 04:00:31 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Best Practices]]></category> <category><![CDATA[Business Management]]></category> <category><![CDATA[Employment]]></category> <category><![CDATA[Friday Inspirations]]></category> <category><![CDATA[changing jobs]]></category> <category><![CDATA[employer]]></category> <category><![CDATA[leaving politely]]></category> <category><![CDATA[new job]]></category> <category><![CDATA[unemployment]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=523</guid> <description><![CDATA[Imagine that you&#8217;ve just been offered a brand new job. That&#8217;s fantastic! Now, make sure you do the math and find out what it will cost you. &#8220;Cost me?&#8221; you ask. Yes. Accepting a new job is exciting and often beneficial, but there are costs associated with it that you must consider before you sign [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/count-the-costs/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Stop Sacrificing Readability For Efficiency!</title><link>http://www.brandonsavage.net/stop-sacrificing-readability-for-efficiency/</link> <comments>http://www.brandonsavage.net/stop-sacrificing-readability-for-efficiency/#comments</comments> <pubDate>Thu, 26 Mar 2009 12:32:29 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Best Practices]]></category> <category><![CDATA[Business Management]]></category> <category><![CDATA[Debugging]]></category> <category><![CDATA[System Architecture]]></category> <category><![CDATA[optimization]]></category> <category><![CDATA[PHP]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=289</guid> <description><![CDATA[Much was made last week over the topic of micro optimization in PHP. Most of these argued that micro optimization was a bad idea, from the perspective of unit testing, the idea that &#8220;premature optimization is the root of all evil&#8221;, the fact that it takes too much time, and that it violates the rules [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/stop-sacrificing-readability-for-efficiency/feed/</wfw:commentRss> <slash:comments>20</slash:comments> </item> <item><title>Paying Down Technical Debt</title><link>http://www.brandonsavage.net/paying-down-technical-debt/</link> <comments>http://www.brandonsavage.net/paying-down-technical-debt/#comments</comments> <pubDate>Mon, 23 Mar 2009 12:30:42 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Best Practices]]></category> <category><![CDATA[Business Management]]></category> <category><![CDATA[application architecture]]></category> <category><![CDATA[development]]></category> <category><![CDATA[PHP]]></category> <category><![CDATA[technical debt]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=270</guid> <description><![CDATA[Much has been written about technical debt, and the way it&#8217;s both accrued and paid off. For the uninitiated, here&#8217;s the definition of technical debt: The amount of time, money, or effort it takes to work around, manage, and fix bad decision/implementation decisions. (CaseySoftware) Put another way, technical debt is the sum total of all [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/paying-down-technical-debt/feed/</wfw:commentRss> <slash:comments>6</slash:comments> </item> <item><title>Scaling Up: Baby Steps (a.k.a. Asking The Right Questions)</title><link>http://www.brandonsavage.net/scaling-up-baby-steps-aka-asking-the-right-questions/</link> <comments>http://www.brandonsavage.net/scaling-up-baby-steps-aka-asking-the-right-questions/#comments</comments> <pubDate>Mon, 16 Feb 2009 11:30:13 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Best Practices]]></category> <category><![CDATA[Business Management]]></category> <category><![CDATA[System Architecture]]></category> <category><![CDATA[Web Architecture]]></category> <category><![CDATA[efficiency]]></category> <category><![CDATA[preparation]]></category> <category><![CDATA[project management]]></category> <category><![CDATA[scaling]]></category><guid isPermaLink="false">http://www.brandonsavage.net/?p=174</guid> <description><![CDATA[Before we actually get started hacking on our code, let&#8217;s make sure we&#8217;ve got the right questions asked and answered. We&#8217;re going to need some resources, the help of others in our organization, and probably some understanding of the current system structure before we&#8217;re successful in our goal. Some of these questions may seem mundane, [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/scaling-up-baby-steps-aka-asking-the-right-questions/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <series:name><![CDATA[Scaling Up]]></series:name> </item> <item><title>Attention Developers: The Problem Isn&#8217;t Technical</title><link>http://www.brandonsavage.net/attention-developers-the-problem-isnt-technical/</link> <comments>http://www.brandonsavage.net/attention-developers-the-problem-isnt-technical/#comments</comments> <pubDate>Sun, 14 Dec 2008 19:35:45 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Business Management]]></category> <category><![CDATA[clients]]></category> <category><![CDATA[customer service]]></category><guid isPermaLink="false">http://dev.brandonsavage.net/?p=101</guid> <description><![CDATA[How many times have we heard it? Our bosses, colleagues, everyone, it seems, reminds us time and time again that we&#8217;re actually customer service professionals, as well as developers. Seems we&#8217;d get it, right? The subject may have been flogged to death, but I&#8217;m going to bring it up one more time. Why? Two reasons: [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/attention-developers-the-problem-isnt-technical/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Hosting Made for PHP Developers</title><link>http://www.brandonsavage.net/hosting-made-for-php-developers/</link> <comments>http://www.brandonsavage.net/hosting-made-for-php-developers/#comments</comments> <pubDate>Tue, 11 Nov 2008 10:19:06 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Business Management]]></category><guid isPermaLink="false">http://dev.brandonsavage.net/?p=88</guid> <description><![CDATA[A few months ago I switched over to Slicehost for web hosting. I have to say, I don&#8217;t think I could have made a better choice. I&#8217;m not sure what I was expecting, but what I got was pretty amazing. Slicehost works by offering virtual servers for each account &#8211; that is, for each account [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/hosting-made-for-php-developers/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Note To Clients: Please Tell Me More Than &#8220;It&#8217;s broken!&#8221;</title><link>http://www.brandonsavage.net/note-to-clients-please-tell-me-more-than-its-broken/</link> <comments>http://www.brandonsavage.net/note-to-clients-please-tell-me-more-than-its-broken/#comments</comments> <pubDate>Sat, 30 Aug 2008 21:29:52 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Business Management]]></category> <category><![CDATA[Contract Work]]></category> <category><![CDATA[bug fix]]></category> <category><![CDATA[client relations]]></category> <category><![CDATA[clients]]></category> <category><![CDATA[custom software]]></category> <category><![CDATA[development]]></category> <category><![CDATA[project management]]></category><guid isPermaLink="false">http://dev.brandonsavage.net/?p=46</guid> <description><![CDATA[Ever have that one client who says &#8220;it&#8217;s broken&#8221; and can&#8217;t give you any more information than that? I&#8217;ve been there. Before I get into it, let me put a disclaimer out there: I&#8217;m not calling anyone out. I&#8217;m not specifying that this happened recently or even a particular client who does this. I&#8217;m just [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/note-to-clients-please-tell-me-more-than-its-broken/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>The time versus the value</title><link>http://www.brandonsavage.net/the-time-versus-the-value/</link> <comments>http://www.brandonsavage.net/the-time-versus-the-value/#comments</comments> <pubDate>Mon, 11 Aug 2008 03:20:30 +0000</pubDate> <dc:creator>Brandon Savage</dc:creator> <category><![CDATA[Business Management]]></category> <category><![CDATA[Contract Work]]></category> <category><![CDATA[charge per hour]]></category> <category><![CDATA[charge per project]]></category> <category><![CDATA[small business]]></category><guid isPermaLink="false">http://dev.brandonsavage.net/?p=32</guid> <description><![CDATA[Freelance Switch once did a blog entry on the benefits of charging by the project, rather than by the hour. They argue that the benefits outweigh the costs, including the benefit of increasing efficiency. I&#8217;ve often debated this myself, and I&#8217;ve wondered whether or not charging by the job was better than by the hour. [...]]]></description> <wfw:commentRss>http://www.brandonsavage.net/the-time-versus-the-value/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using apc (user agent is rejected)
Database Caching 46/56 queries in 0.020 seconds using disk

Served from: www.brandonsavage.net @ 2010-09-10 11:53:23 -->