5 tips for Cheaper Web Development

1. Requests for Proposals pay for themselves

The RFP document will be how the development team provides an estimate on both the work described in the document and the risk you represent as a client. Better RFP documents will result in a higher response rate, more accurate estimates, less time in meetings talking about the RFP, and less padding to account for risk.

The customer acquisition process is the most expensive operation for a custom development shop. Every lead that comes in the door represents a mix of opportunity, risk, and expense that development teams work very hard to mitigate. The good news is that you are the one with the money to spend, but to get the most for your money, you need to maximize your vendors’ opportunity and minimize their risk and expense.

Start your RFP with the the project working name, who to contact with questions, and how and where to submit the RFP to. Next, write a short, high-level project summary that includes what you want to do and how you will define success. Follow the project summary with a project timeline with a deadline for submitting proposals, a start time, and when you need the project completed. If you have any specific technical requirements, include them. If parts of the project are already completed or will be sourced to other vendors, make that clear as well.

Make sure each page of the RFP has a page number; this will save you time when going over the document in phone calls. Section headings also help to quickly steer conversations to the relevant portion of the document.

Focus the RFP on what needs to be done and avoid how it is going to get done. Sometime there is a temptation to get into details, but a decent web development team will quickly figure that out on their own. There are exceptions, but focusing on what to do and not how to do it is a good rule of thumb.

Pro Tip: A good RFP document can replace about half of the scope of work document your development team will write, which translates to even more cost savings for you.

Continue reading “5 tips for Cheaper Web Development”

symfony 1.3 Book by Tim Bowler & Wojciech Bancer

Symfony 1.3 Web Application Development is the latest book on the symfony PHP web framework and the first not written by the authors of the framework.

This allows the authors to adopt a more pragmatic style that favors 3rd party plugins.  This is a good thing because IMHO the most important thing about a framework is it’s library of extensions. Continue reading “symfony 1.3 Book by Tim Bowler & Wojciech Bancer”

Internationalized (i18n) Admin Generator CRUD’s in Symfony 1.2.9 + Doctrine

I was having some trouble finding documentation on how to i18n generated CRUD’s, so once I figured (most) of it out I thought I’d share it

The Example Application

Content Block CRUD with French langage selected

Since I have to create a feature in my one of my current work projects to store random bits of content, like privacy policies and such, in multiple languages. I thought I’d double dip and use that for this example.  I’m calling the feature content blocks.  It will have a backend CRUD that will facilitate translations.  The UI I needed was to have the default language show up as well as one of the many languages this information would be translated into.  My app has the possibility of having more than 20 language options so putting them all in the CRUD at once was unreasonable. Continue reading “Internationalized (i18n) Admin Generator CRUD’s in Symfony 1.2.9 + Doctrine”