Coding naming convention

CSS Ids Or Classes
good: my-id-or-class (always lower case)
bad: myIdOrClass, my_id_or_class, myIDOrClass

JavaScript, Java, PHP, Etc … Vars
good: myVar, getMyData()
bad: anything else then camel case

Acronyms:
Ex: HUD AMI

Function And Vars
good: hudAmi, getHudAmi();
bad:HUDAMI, getHUDAMI()

Class Names:
good: Ami
bad: AMI

MySql Column Names:
good: my_column_name
bad: myColumnName, mycolumn

Html Code:
bad: Do not use ‘tables’, use div

Styling:
Do not write a class or inline style until all the generic tags having coded in css file. From there write with the highest possible level of obfuscation.

Default Coding Conventions:
http://framework.zend.com/manual/1.12/en/coding-standard.overview.html

Development Setup Convention

Project Naming:
ex: client = blink-tech.com then project repository will be blink-tech
Your local VirtualHost must have the line for the site to work: SetEnv APPPLICATION_ENV localhost

IDE – Subversion
good: Integrated SVN, make sure to not include local files.
bad: Don’t use 3rd party tools (i.e. SVN Tortoise) will surely lead to errors.

Note:
Local projects are expected to behave exactly as production servers. You will need your local smtp to work and have all the required PHP extensions.

It is with both sadness and gratitude that we announce the official closing of Blink;Tech.

After the loss last year of Paul, our leader and the founder of Blink;Tech, we have made the difficult decision to bring our business operations to a close. After over 20 years in business, we feel both his and the Blink;Tech legacy will continue through the relationships and impact he leaves behind.

We want to express our deepest gratitude for your support and partnership over the years. It has been a privilege to serve you.

Sincerely,

The Blink;Tech Team