วิธีง่ายที่สุด
1. คุณวัดค่าความสามารถของคุณเองขึ้นมาก่อนง่ายๆ ว่าเดือนหนึ่งคุณอยากได้เงินเดือนที่เท่าไร แล้วเอามาหาร 20 จะได้เป็น man/day
2. ลองคิดดูว่าจะใช้เวลากี่วันจึงจะทำให้งานเสร็จ เช่น หากไม่ใช้ Ajax ใช้เวลา 20 วัน แต่ถ้าใช้ Ajax ใช้เวลา 30 วัน แค่นี้เงินมันก็ไม่เท่ากันแล้ว
3. ใส่ค่า Overhead ในการทำงานเข้าไปเช่น ค่าเดินทาง ค่าไฟ ค่าโทรศัพท์ ค่าปวดหัว ฯลฯ ส่วนมากแล้วจะคิดเป็น 30% ของ 2 ส่วนแรก
4. เอาเงินที่ได้มาคูณกับ % ที่เราคิดว่าน่าจะเป็นกำไร เช่น อยากได้กำไร 30% ก็คูณเข้าไป

เ ท่านั้นก็จะได้ราคาโดยรวม ซึ่งราคานี้ยังไม่รวม Maintain นะครับ คุณต้องคิดต่อไปด้วยว่าจะคอยช่วย Support แก้งานอีกถึงเมื่อไร อาจจะแถมให้ Maintain ให้ 3 เดือน ก็เหมือนกับการการันตีของทั่วไป แต่หลังจากนั้นคิดเงินเป็นครั้งละ xxx บาท หรือเดือนละ xxx บาท ซึ่งโดยมากแล้วหากคิด support เป็นปีจะคิดเป็น 25% ของราคารวมครับ

อันนี้ เอามาจาก forum narisa โดยคุณ bomber ครับ

เมือลองไปดู website freelance ของทางเมืองนอกดู ก็ปรากฏว่าเขามีวิธีที่เป็นมาตราฐานอยู่หลายวิธีเหมือนกัน ผมรวมๆเอามาให้ได้ดังนี้ครับ

Formula 1 - The Basic Method

Follow these steps to figure out what your hourly rate should be.

1. Subtract nonproductive time from Annual Hours to get Billable Hours.
2. Add Salary and Overhead Together
3. Multiply Total By Profit Margin (10% - 20%)
4. Add Total (1) and Total (2) Together
5. Divide Total (3) by Billable Hours (the amount from #1)

For example, if the following is true:

• Salary = $30,000
• Annual Hours = 2,080
• NonProductive Time = 500 hours
• Profit Margin = 20%
• Overhead = $15,000

Then this is how you figure out the hourly rate:

1. 2,080 - 500 = 1,580
2. $30,000 + $15,000 = $45,000
3. $45,000 X 20% = $9,000
4. $45,000 + $9,000 = $54,000
5. $54,000 / 1,580 = $34 / hour

Formula 2 - The Easy Method

This formula is the easiest of them all. However, I don’t recommend this formula unless you are a well-established professional. This isn’t the way to start out your freelance business — only very skilled freelancers can get away with this.

Ask yourself the following questions:

1. How much money do you want to make on this project?
2. How many hours do you want to work?

Now all you need to do is divide 1 by 2. It’s that simple! You now have your hourly rate.

Formula 3 - Annual Costs and Annual Hours

Use this formula if you need to set the rates for your entire business.

Add up all the costs you incur through your business on an annual basis (and don’t forget to factor into these your profit percentage), and divide this by the annual hours you work. This will give to you your pay rate.

1. Salaries + Overhead = Annual Costs
2. Divide Annual Costs by Annual Hours Worked

So for example, if the following is true:

• Salaries = $60,000
• Overhead = $50,000
• Annual Hours = 2,080

Then this is how you figure out the hourly rate:

200,000 / 2,080 = $52 per hour

Formula 4 - Pricing By Order Form

To price by order form, you’ll need to use an order form to add up the cost of each ingredient in a project. I don’t recommend using this method unless you’re only designing simple sites that all have the same basic ingredients, otherwise, there can be too many variables in the project, which can prevent you using an order form. Here is an example of an order form you might use:

Formula 5 - Estimation By Project

Most clients are going to want to hear how much the entire project is going to cost. Even if you have an hourly rate, this alone is probably not going to be acceptable to your future clients — you’ll need to justify the number of hours you plan to spend on their job. It takes practice, but you’ll need to learn how to break projects into individual tasks, in order to estimate how long the project is going to take (in hourly terms), and then charge accordingly. Be sure to find out what the client expects you to take care of — if they expect you to do everything, take this into account in your quote. Whatever the case, break the project into the following phases:

Now visualize how many hours you feel each stage of the project is going to take, and total these hours to get a final figure.

Multiply your hourly rate (figured out from one of the above formulas) by the total estimated number of hours for project. The resulting amount forms your bid for the project.

So for example, if the following is true:

• Hourly Rate = $30
• Total Estimated Project Hours = 50

Then this is how you figure out how much to bid on a project:

$30 x 50 = $1,500

Make sure that your client is very clear about the scope of the project. You should write a clear contract to make sure that the outline of the project is mutually understood, otherwise the client may take advantage of you (or feel that you are trying to take advantage of them!).

พอดีจำเว็ปที่มาไม่ได้แล้วครับ ต้องขอโทษที

read more | digg story

สิ่งสำคัญสิ่งหนึ่งที่ PHP ไม่มีเหมือน JSP หรือ .NET ก็คือ มันไม่มีมาตรฐาน framework ที่กำหนดข้อบังคับในการเขียนโปรแกรม ทำให้การ maintain application ใหญ่นั้น ยุ่งยากและซับซ้อนเป็นอย่างยิ่ง

แต่ปัจจุบันนั้น ได้มี framwork หลายตัวกำเนิดขึ้นมา ทำให้การสร้าง application ใหญ่ๆด้วย PHP นั้น สามารถทำได้ง่ายดายยิ่งกว่า การเขียนด้่วย JSP หรือ ภาษาอื่นๆนัก

Frameworks ที่ผมอยากแนะนำ เหล่าีนี้ ส่วนใหญ่มีต้นแบบมาจาก Ruby on Rails ซึ่งถือว่าเป็น web application framwork ที่โด่งดังที่สุดในโลกตอนนี้

แล้วทำไมผมไม่ใช้ Ruby เขียนเลยละ อ่ะ.. ก็ผมถนัด PHP นี่ครับ และอย่างไร PHP ก็ืถือเป็นภาษาที่นิยมที่สุดบน web และมีผู้ support มากที่สุด (ไม่เชือลองหา hosting ที่ support Ruby ในประเทศไทยดูดิ)

Frameworks ที่ผมนำมาแนะนำวันนี้ 6 ยี่ห้อ นำมาจาก web ของ H3RALD.COM ซึ่งได้เปรียบเทียบข้อดีข้อเสียของแต่ละ frameworks ได้อย่างเข้าใจง่ายมาก

CakePHP

Website: www.cakephp.org
PHP version: PHP4 and PHP5
License: MIT⁵
Download size (.tar.gz): 184KB
Supported Databases: MySQL, PostgreSQL, SQlite, MS SQL + any other supported by ADOdb or PEAR::DB database abstraction layers
Beginner’s Tutorial: Blog Tutorial

Official Description:
“Cake is a rapid development framework for PHP which uses commonly known design patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. Our primary goal is to provide a structured framework that enables PHP users at all levels to rapidly develop robust web applications, without any loss to flexibility.”

PROs:

• Lightweight, not bloated, containing only essential code
• Runs both on PHP4 and PHP5
• No configuration needed - except for a stupidly short database configuration file and a few constants which can be modified. You can literally start baking in less than five minutes
• Extended table association support, allowing the creation of complex database architechtures
• Extremely logical and functional directory structure: better than Rails, if you ask me.
• Enhanced AJAX support through the AJAX and Javascript view helpers
• useful “bake” command line script to generate parts of the code automatically
• Very active community and plenty of satellite sites
• Suitable for every kind of website, from the small personal site to the advanced e-business application.

CONs:

• No “official” internationalization support for now, but it will be included in the next milestone.
• It does not take fully advantage of PHP5 features
• Official documentation still needs some some improvement, although now it seems pretty complete and exhaustive.

Comments:
CakePHP is my personal favorite: easy to learn, easy to use,multi-purpose and not bloated. Cake’s philosophy is not to include unnecessary code in the framework unless it’s absolutely necessary for the framework itself, as a result, 3rd-party libraries are not included in the official releases, but may be seamlessly integrated with the framework if developers need them.
Cake’s success is partly determined - at least initially - by the fact that it can run fine with no limitations on PHP4, while other similar frameworks don’t. Although this may still be one of its most obvious strengths, it must be said that Cake seems to go in the right direction, taking only the best from Rails, without forcing developers into complex and pointless adaptations, and evolving into a great framework created in PHP, for PHP.

DevMonkey Comment: CakePHP เป็น framework ที่ผมใช้ทำงานอยู่เป็นประจำ ยังไงผมจะเล่ารายละเอียดของ framework นี้ใน blogs ต่อๆไปของผมครับ Symfony

Website: www.synfony.project.com
PHP version: PHP5
License: Symfony⁶
Download size (.tgz): 1255KB
Supported Databases: MySQL, PostgreSQL, SQLite, Oracle, MS SQL + any other supported by Creole database abstraction layer
Beginner’s Tutorial: My first project

Official Description:
“Based on the best practices of web development, thoroughly tried on several active websites, symfony aims to speed up the creation and maintenance of web applications, and to replace the repetitive coding tasks by power, control and pleasure. […]
Symfony is an object-oriented PHP5 framework based on the MVC model. Symfony allows for the separation of business rules, server logic and presentation views of a web application. It also contains numerous tools and classes aimed at shortening the development time of a complex web application.”

PROs:

• Fully featured framework, includes everything you might ever need (see CONs, below)
• Full native internationalization support
• Truly excellent documentation, tutorials, wiki, book, screencasts, API, real-world examples, etc. etc.
• Code generators
• Various “pre-built” modules/libraries for the most common tasks
• It was not inspired only by Rails, but borrows concepts and practices from various other frameworks
• Good community support

CONs:

• Seems too big compared to the others, too many “extras” which may not be useful to all developers
• PHP5 only
• Confusing and disorganized directory structure
• Uses too many configuration files, not suitable for simple projects
• Steep learning curve

Comments:
Symfony is really an interesting framework: it’s perhaps the most complete in terms for features and documentation. The only problem I have with it is that it just seems too complex and rather difficult to learn if compared to the others, which can do almost the same things (or will soon be able to) in a MUCH simpler way. A nice blend of MVC, pre-built components, command line generators and YAML/Propel configuration files, but perhaps a bit disorganized in its internal structure, unlike its wonderful documentation and support section.

PHP on Trax

Website: www.phpontrax.com
PHP version: PHP5
License: MIT
Download size (.tgz): 843KB
Supported Databases: Any database supported by PEAR::DB
Beginner’s Tutorial: How to create a Trax application

Official Description:
“Php On Trax (formerly Php On Rails) is a web-application and persistance framework that is based on Ruby on Rails and includes everything needed to create database-backed web-applications according to the Model-View-Control pattern of separation.”

PROs:

• Simple, logical, essential: a true RoR port to PHP5
• Code generators, like Rails
• Zero configuration (like Rails and Cake
• Easy and logical directory structure (the same as Rails)
• Supports table associations, but more in a way which is more similar to Ruby on Rails than Cake.

CONs:

• Lack of documentation compared to the others
• Trying to port Ruby on Rails to PHP, ignoring why RoR was not built in PHP in the first place⁷
• No internationalization or other advanced functionalities
• PHP5 only
• Small community
• DBO class based only on PEAR::DB

Comments:
In my opinion this project aims too much to be a Rails-clone to acquire a proper consensus. Trying to port something to another language is not good, especially in the case of Rails and Ruby. This framework looks somehow like an old version of CakePHP, which evolved slightly but always remained anchored to its beliefs of building a Rails port for PHP (even in the name!). Some may say that this is a lost battle since the beginning - or better, since before it started - but others found that PHP on Trax can be the easiest way to switch from Ruby on Rails to a PHP equivalent. Who is going to do that? Well, Ruby programmers forced to develop in PHP, maybe. Not too good, but not too bad either.

Code Igniter

Website: www.codeigniter.org
PHP version: PHP4 and PHP5
License: CodeIgniter⁸
Download size (.zip): 609KB
Supported Databases: MySQL, PostgreSQL, SQLite, MySQLi, MS SQL + ODBC
Beginner’s Tutorial: Hello World! Introduction to Code Igniter [video]

Official Description:
“Code Igniter is an Open Source Web Application Framework that makes writing kick-ass PHP programs simple as apple pie. […] Designed to enable, not overwhelm, Code Igniter is a powerful PHP framework with a very small footprint, built for PHP coders who need a simple and elegant toolkit to create full-featured web applications.
If you’re a developer who lives in the real world of shared hosting accounts and clients with deadlines, and if you’re tired of ponderously large and thoroughly undocumented frameworks that require rocket science to understand, Code Igniter might just be the right tool for you.”

PROs:

• Good and organized documentation
• Zero configuration (like Rails and Cake)
• Includes various classes and libraries for common tasks
• Compatible with PHP4 and PHP5
• Medium-sized community
• Intuitive directory structure
• Ships with the full user guide included in separate HTML files

CONs:

• No full (“written”) tutorials except the videos!
• Relatively new to the scene, but growing
• Does not seem to support table associations.

Comments:
People on the Net seem to be rather enthusiastic about this framework: where there’s a thread about the big ones (Cake and Symfony), there’s always, someone who pops in suggesting to try out Code Igniter. I personally think this can be a true bless for small/medium sized projects, however, I’d opt for CakePHP or Symfony for a large scale application: something is missing, e.g., most notably, table associations.

Biscuit

Website: biscuitproject.tigris.org
PHP version: PHP4 and PHP5
License: MIT⁵
Download size (.zip): 240KB
Supported Databases: Any database supported by PEAR::DB
Beginner’s Tutorial: Creating a simple application using the Biscuit MVC framework

Official Description:
“The mission of this project is to port Ruby on Rails to PHP5 (minus the Ruby part ”

PROs:

• Zero configuration, easy to deploy
• Runs both on PHP4 and PHP5
• Simple to learn

CONs:

• Still under development and incomplete
• Offers a limited subset of the features and functionalities offered by competitors: no internationalization, no table associations, no scaffolding…
• “Documentation coming soon”
• Almost non-existent community

Comments:
This project started as an attempt to create something simpler than CakePHP and more similar to Rails. I’m not sure whether the project is still active or not, since the last “release” on the former’s developer site is dated August 2005. Still in early stage - or dead.

Pipeline

Website: livepipe.net/pipeline/
PHP version: PHP5
License: Pipeline⁹
Download size (.zip): 288KB
Supported Databases: SQLite
Beginner’s Tutorial: none

PROs:

• Simple directory structure
• Suitable for small projects
• Comes with various ready-made components
• Supports table relationships

CONs:

• PHP5-only
• Too restrictive: only SQLite supported, kindly suggests developers to use its built-in features only
• No documentation or tutorials, just the API
• Not suitable for large projects
• Almost non-existent community

Comments:
This project mainly borrowed the MVC architecture and some basic concepts from Rails, creating a simple PHP5 framework with personal/small websites in mind: it offers various built-in components which can be handy to most of us, supports only SQLite, and basically tells developers what to do. In my opinion it’s not flexible enough to be compared to the others, and it’s simply not suitable for anything other than small websites.

Conclusions

My favorite framework still remains CakePHP, it’s simple and yet powerful, easy to learn and use, mature, well supported and continuously improving. Symfony - at the moment - seems to be the one with most features and the best documentation, and it is an excellent and well supported project. The only problem I have with it is the scary amount of configuration files necessary to create an application: CakePHP doesn’t need any and can be used for (almost?) equally complex projects.
Although I didn’t have a chance to try them out, PHP on Trax is certainly the most faithful port of Ruby on Rails to PHP, but it lacks some of the features CakePHP and Symfony offer. Code Igniter may not be as advanced as the others, but its community seems to grow and its simplicity may appeal more users in the future…

At any rate, developers should always choose the best framework for their needs: I tried to write a quick comparative analysis of these six Rails’ “PHP children”, now it’s your turn, try out some of them, if you choose wisely you won’t be disappointed.

Notes

¹ They are all distributed according to various Open Source licenses.

² Ruby on Rails - Ruby framework for web development

³ CakePHP - Rapid [PHP] Development Framework

⁴ CakePHP - A ‘tasty’ solution for PHP programming, originally published on zZine Magazine

⁵ Open Source MIT License.

Symfony License: