Community

February 3rd, 2010

Open source software is all about the idea of community.

 

The concept that more people contributing to small parts to one common goal will create something exceedingly better then a project created by an individual. This is the reason why at Floodlight we are PHP developers and contribute to the open source community as much as possible.

 

This week the largest PHP web application made a huge contribution to the open source community. Facebook has spent the last 2 years re-writing PHP to make it run 10x faster then it currently does. Now that they have completed the project they released the code to the open source community. They hope that all the developers that access it make their release that much better and find new ways to utilize this technology.

 

This concept applies to business as well. How are you investing in your business community? How can you help your partners?

 

Invest in your community

Protected Data

December 2nd, 2009

Region capture 1

 

How is your website protected?  Does your web developer or host create daily/weekly/monthly backups of your site files and database?  Typically clients don’t tend to ask these questions until the damage is already done.  It’s good to ask sooner rather then later.

 

Our hosting partner Rackspace, does perform daily backups, but only saves that data for 3 days.  We extend this protection by providing daily/weekly/monthly backups for all our site using a simple perl script.  When you see how simple it is you will implore your developer to implement a similar script.

 

Ready?  Here’s the quick explanation…

 

Line 2 – Sets up the timestamp for use in file names

Line 3 – Gets a MySQL dump of the database content and saves it

Line 4 – Compresses the MySQL dump file

Line 4 – Copies the full web content directory, compresses the files, and saves it

Line 6 – Finds backups that are older more then 7 days ago and deletes them.

 

This script will keep daily backups for a week and then automatically delete the older files. Pretty neat huh?

 

So the next time you have your web developer on the phone make sure you ask them about how your site is being backed up and refer him to this post for a simple perl script to do just that.

 

Happy Surfing!

Where Does my Website Live?

October 23rd, 2009

Recently I was asked by a client why they’d want to host a site with us when there are web hosts that offer hosting for 4 bucks a month.  The short reasoning I gave them was support, reliability, and time.

 

We work with Rackspace to provide clients the best possible hosting experience.  Rackspace offers their fanatical support via chat, twitter, phone, email, and now a new ticketing system.  Basically if you have a problem and need to reach out they’ve got you covered.  This is a huge difference from a host that lists an 800 number that goes directly to a messaging system.  I typically interface with them via chat and am greeted with a server engineer that I have yet to stump.  If you choose to call you won’t get long automated menus, but you will get a server specialist that works with you to solve your issue.  No scripts, no pdf manual, a real person working through your issue.

 

As far as reliability goes Rackspace offers a 100% uptime guarantee.  Thats right, no 99.999999% garbage. Fully committed and backed 100% site uptime.   I’ve yet to have to use this feature of getting a refund because of downtime and I’m glad.  They are following through on their commitment to their clients.  MediaTemple used to be our web-host of choice, but because of their repeated downtime failures we looked for better for our clients.

 

Rackspace really works hard at creating a UI for their site management that makes sense to users.  It has been refined over the last 6 months and allows new users to create sites in minutes.  This saves us time as we setup accounts for our clients and makes the overall management process extremely intuitive. Their control panel allows us to perform hosting operations on behalf of our clients as well as giving clients their own login and control. This 2-tiered administration setup gives our clients independence yet provides the security of us being able to save-the-day when necessary.

 

In addition to all this, file backups are run on a twice daily schedule and have saved our clients in multiple situations.  Working with them is like having another whole department in our company that takes care of our client’s servers.  Thats how dedicated they are.

 

Are you going to pay 4 bucks a month for this?  No. But think about what you are getting for your investment.  Not having to worry about the availability of your number one marketing tool is priceless.

Bridging the Gap

October 2nd, 2009

bridgingGap

 

So, why would I, a graphic designer, want to intern at a web development firm? My answer is this: Design and development should not be mutually exclusive. The web is, by far, the most heavily used medium for communicating, so it seems silly for one profession to avoid (or fear) the other.

 

Designers need developers to communicate their message online, and developers need designers to give them a message. But what about capabilities? A print designer probably has no idea why it would be tricky to tile a background image and throw a gradient over it, or why they can’t use a typeface other than Verdana or Georgia. Likewise, a coder sees beauty in Monaco–faultlessly tabbed, but it’s doubtful that one would see the beauty in perfect kerning and elegant leading, neither of which can be found in any coded page (they translate, respectively, into “letter-spacing” and “line-height”).

 

When I started here I had no idea what “W3C” was, much less why it’s important to be compliant with their standards, so It’s been a tremendous help to understand the web from both sides of the equation. I understand that “creatives” thinking code and coders thinking creative can sometimes, in rare cases, cause head trauma, so I recommend exercising caution. But the more these two fields can be integrated, the more streamlined and painless things will become for everyone. That is of course, excluding the dreadful IE6 with all it’s random pitfalls and senseless hurdles.

 

From my time here at Floodlight, my advice for other students, both graphic designers and developers, is to invest a little time getting to know each others’ profession. It helps a great deal even if you only know the language! If others could share my experience I believe that communication between these two “factions” would no longer be lost in translation.

Communication is Key

September 2nd, 2009

matrix

 

This past year our client’s are becoming more tech savy and more over-worked than ever. Many have elected to use twitter, SMS, or brief emails to communicate. Gone are the days of the 2hr lunches to discuss new projects.

 

This shift in communication methods as well as work whizzing by at 100 mph creates opportunity for mis-interpreting their needs. We have had the experience of creating additional work for ourselves multiple times because of an assumption or mis-read directive. Through these projects we have learned that it is better to be redundant than to be brief. Even though a client may get frustrated with additional clarifying questions it can potentially save hours of your time and theirs. Lately we’ve been focusing on writing clearer emails, asking more questions, and listening actively.

 

Hopefully our experience saves you some time and encourages you to pause and ask that one more question before launching in an off-base direction.

 
© 2010 Floodlight Design. All Rights Reserved.