Train Your Employees

Last week, Cal Evans retweeted James McGovern, who originated this tweet:

Training Tweet


Friday, September 11th, 2009 @ 1:00 am | Comment (1) | Categories: Business Management
Tags: , , ,

Count The Costs

Imagine that you’ve just been offered a brand new job. That’s fantastic! Now, make sure you do the math and find out what it will cost you.

“Cost me?” 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 the offer and tell off your present employer. Some of these costs are obvious, but others are less obvious. These costs are rarely fully explored, because we have a tendency to see the grass as greener someplace else, and if the offer we receive is substantially better than our current one, we are more inclined to accept it. But not counting the costs would be a huge mistake.


Friday, August 7th, 2009 @ 12:00 am | Comment (2) | Categories: Business Management, Employment, Best Practices, Friday Inspirations
Tags: , , , , ,

Stop Sacrificing Readability For Efficiency!

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 “premature optimization is the root of all evil”, the fact that it takes too much time, and that it violates the rules of development and optimizaton.

There’s another reason that micro optimization can be a bad choice: it makes code absolutely impossible to read!

The original article by Alex Netkachov makes arguments about calling static methods, using magic methods, getting the time with $_SERVER[‘REQUEST_TIME’], output buffering, and loops. But what this article completely misses is that many of these tips would render code completely useless if you had to maintain it.

Thursday, March 26th, 2009 @ 8:32 am | Comment (20) | Categories: Best Practices, System Architecture, Debugging, Business Management
Tags: ,

Paying Down Technical Debt

Much has been written about technical debt, and the way it’s both accrued and paid off. For the uninitiated, here’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)


Monday, March 23rd, 2009 @ 8:30 am | Comment (6) | Categories: Business Management, Best Practices
Tags: , , ,

Scaling Up: Baby Steps (a.k.a. Asking The Right Questions)

Before we actually get started hacking on our code, let’s make sure we’ve got the right questions asked and answered. We’re going to need some resources, the help of others in our organization, and probably some understanding of the current system structure before we’re successful in our goal.

Some of these questions may seem mundane, and others will be extremely important. But we must ask and receive answers to all of them, so let’s get started.


Monday, February 16th, 2009 @ 6:30 am | Comments (0) | Categories: Business Management, Web Architecture, Best Practices, System Architecture
Tags: , , , ,

Attention Developers: The Problem Isn’t Technical

How many times have we heard it? Our bosses, colleagues, everyone, it seems, reminds us time and time again that we’re actually customer service professionals, as well as developers. Seems we’d get it, right?

The subject may have been flogged to death, but I’m going to bring it up one more time. Why? Two reasons: first, because we all need the reminder from time to time. And second, because I need the reminder on a daily basis.


Sunday, December 14th, 2008 @ 2:35 pm | Comment (1) | Categories: Business Management
Tags: ,

« Older Entries Newer Entries »

Copyright © 2024 by Brandon Savage. All rights reserved.