Re: Tips on programming (in PHP)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



80% of development is testing.  If you only test at the end, you are in heap of trouble.


----- Original Message ----
From: Krishna Srikanth <krishna.srikanth@xxxxxxx>
To: php-objects@xxxxxxxxxxxxxxx
Sent: Wednesday, March 26, 2008 3:23:07 AM
Subject:  Tips on programming (in PHP)

Hi,

Some suggestions for new php programmers (newbies). 

DO NOT treat company websites like personal websites. They have more than 
just a blog, three four static pages and a contact form. Ofcourse many of 
the sites have onlythese, but I am talking about "PHP applications" which 
are database and task oriented. 

Develop the application in some standard. If you don't know any standard, 
do some research on google. Follow consistent variable namings and write 
comments on what the code block will do. Validate all inputs and before 
sending the data to databases, properly escape the strings. 

SQL injection is the biggest attack. Know about it. Send least important 
data in cookies and place everything else in Sessions or in database, but 
not in text files, because they will be accessible through a browser. 

After developing your application, give it to your competitors to crack 
your site. If they are successful, you have to learn how to avoid the 
attacks. If they fail, go and have a party. It is all set.

Documentation is a crucial thing in PHP applications or websites developed 
for companies. There will be another person maintaining the site developed 
by you and he SHOULD understand what the site is. Three kinds of basic 
documents are needed. 

1. Requirements document: Which says why they need a website. and what is 
expected out of the site. No technical stuff here.
2. Prototype document: The document explaining the site functionally, It 
is a rough layout with dummy data plus some reasons why the content is 
placed on particular page.
3. Coding document: Completely technical. A list of classes, their 
properties or methods, etc. Functions or frameworks used. Database tables 
and their descriptions etc.

While preparing a manual include as many screenshots as possible by naming 
them sequentially, because a picture is worth a hundred words.

I strongly recommend reading "PROFESSIONAL PHP" book by Wrox Publications

Regards,
Manda Krishna Srikanth
http://www.krishnas rikanth.com
=====-----== ===-----= ====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

[Non-text portions of this message have been removed]


 


      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

[Non-text portions of this message have been removed]


[Index of Archives]     [PHP Home]     [PHP Users]     [PHP Soap]     [Kernel Newbies]     [Yosemite]     [Yosemite Campsites]

  Powered by Linux