The Reasons To Attend PHP Conferences

Recently, php|architect announced that they were extending the early bird pricing for the TEK-X conference being held this year in Chicago, IL. As someone who has been and will be going this year, this conference represnts a great opportunity for anyone who hasn’t gone to a PHP conference to attend one.

There are some good reasons that you should be attending.


Thursday, February 4th, 2010 @ 1:00 am | Comment (7) | Categories: Community, Technology
Tags: , ,

Painless Spec and Schedule Development

In the time that I have developed software, I don’t know that I’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’s not that they’re lazy, or that they don’t want to be held accountable; most of the time it’s because developers prefer to express themselves via code, or because developers are afraid that if they set a schedule, and then reality doesn’t match up, they’ll be forced to produce sub-standard code. Neither of these is an ideal situation.

This is directly at odds with the business need of specifications and schedules. Businesses need schedules to know when products will be finished and schedule things like trade shows, product launches, and write contracts with clients who need or want a particular product. It’s not as if businesses want to push their developers to insanity by forcing them to schedule and then stick to it; more often than not thousands of dollars hinges on the schedule, and it simply must be met.


Wednesday, December 16th, 2009 @ 1:00 am | Comment (4) | Categories: Business Management, Best Practices, Technology
Tags: , , , ,

On Code Commenting And Technical Debt

If you’ve been in development for any length of time, you’ve probably come across a project or a company that doesn’t take the time to incorporate comments into its code. The argument is often made that “our code is self-documenting” and that commenting is just a waste of time, especially if you write clear, clean code. But I disagree.

Some people take a different view of commenting than others. Most recently, Eli White wrote an article called “Commenting on Commenting” in which he argued for commenting virtually every single line of code. He talked about working for a company where they stripped the code out and turned the comments into line-by-line documentation. But commenting to me is important for a different reason:


Wednesday, April 29th, 2009 @ 12:30 pm | Comment (12) | Categories: Best Practices
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: Best Practices, Business Management
Tags: , , ,

Note To Clients: Please Tell Me More Than “It’s broken!”

Ever have that one client who says “it’s broken” and can’t give you any more information than that?

I’ve been there.

Before I get into it, let me put a disclaimer out there:


Saturday, August 30th, 2008 @ 4:29 pm | Comments (0) | Categories: Contract Work, Business Management
Tags: , , , , ,

Newer Entries »

Copyright © 2024 by Brandon Savage. All rights reserved.