My Office Job Taught Me…
…a college degree does not guarantee a job, just a ticket to compete for one.
…a college degree does not ensure better pay, only better working conditions.
…it is the perks, not the pay, that keep me working here.
…no matter how much you love the work you do, there will be bad days.
…not everything you do will be fun, but if you love the work you do, it makes the boring projects bearable.
My Fast Food Job Taught Me…

…there are very intelligent, kind people working the humblest of jobs.
…to value grace and appreciate generosity.
…how to cut through corporate red tape and complete the important projects.
…that everyone has a story to tell.
…what a strong work ethic means to those who count on you.
…how to own up to my mistakes.
…to leave my problems at the door.
…that how you handle the bad events in your life is what gives you character.
![]()
Preflight: Preparing GoLive files for Dreamweaver
To prevent a bumpy ride when using the GL2DW migration tool, try these preflight tips:
- Duplicate or back up your site. Experiencing the pain of irretrievable data is unnecessary. Why inflict more pain upon yourself?
- Open your site file and make an assessment. Remove any unused files. Forcing the migration tool to copy the folder where you stashed your favorite LOL cat images and never used them only makes the conversion take longer.
- Check the Extras tab for any unused Smart Objects, Components or Templates. Be ruthless and delete anything you aren’t using. Scary, I know. You did remember to make a copy of your site before attempting this stunt, right?
- Rename Library to Snippets while you are there
- Convert as many Smart Objects to regular images as possible
- Remove the <head> information from Components
- Do the find and replace to your Extras Tab. If no results show up, that’s great! It means your code is clean by GoLive standards.
Excessive use of components (more than 3 for a site) will mean a longer converting time. Expect a 1,000 page site with 6 components to churn away for 30 minutes before giving up on the GL2DW Extension Tool.
Anyone else have some preflight tips that help lessen the pain? Post in the comments!
Essential Reading for Future Web Designers & Developers
“It’s back to school time!” blares every tacky, family-oriented commercial. And so it is.
Real Hackers don’t use CSS a walk through the design process, from tables and frames to CSS.
Getting Things Done When You’re Only a Grunt or, cutting through the stupid B.S. in office politics/bad group projects so you don’t get dragged down with it. Do read the comments afterward, the discussion adds a great deal of insight to the article.
50 Designers x 6 Questions with many gems of truths to be found:
One Typical Myth, that isn’t true: It’s simple, and anybody can do it.
Myth: Web development is for boys. Truth: Web development is for Spartan warriors. People still underestimate the amount of effort that goes into creating a great site or application. The various components are easy, but putting them together in the right way takes time and experience.
The Design Process – Behind the Scenes, Part 2 Redux
You can read The Design Process from the Client’s View and The Design Process – Behind the Scenes, Part 1 if you want to start from the beginning, or read the summary below. Any italicized or emphasized words are jargon used at my company.
An Overview
From the Client’s View
The client decides they need a web site and call Rich. Rich explains why it is important to their business that they have it. They pick a look and their domain name, then supply us with their content. We contact them with a proof on the test site. If they approve it, the site goes live. If not, corrections are made and proofed again.
The Other Departments
Supporting the Web Department with their expertise: Photo Department and Proofreader.
The Web Department – Technical and Design Process
Rich builds a work order or a packet, gathering all the necessary materials – the content, the look, contact information, specific requested items, and directions. He gives the new text to the proofreader, a photo order or purple sheet to the Photo Department, and the packet to the web developer (that’s me or Tim).
Now that I have a packet in my hands, I can check the Web Marketing mac server for my directions. First step to a brand new site is to take the Photoshop file and turn it into a CSS layout. On a good day, this takes me about 4 hours:
- Slice up the Photoshop file and save the images, making sure the images are optimized for dial-up users.
- Open my master site file. The grand scheme consists of a folder with two items: an HTML document, the aptly named template.html, and a Cascading Style Sheet, main.css.1
- Take the template.html into Dreamweaver and define the editable regions.
- Create the new pages with Dreamweaver and upload it all to the test site.
The client is e-mailed a notice that their design is now available to view online. If they are diligent, they have already submitted their content, and the notice informs them that their content will be on the test site soon.
The rest of the time is spent putting their content into the site. This includes building an animated flash intro (if they insist on it), building slideshows, adding text and photos, and incorporating small bits of AJAX where needed.
What happens next?
When they have new information they would like added to their site, they contact one of our Web Coordinators (Sara or Doneta) and give them the directions for changes. Sara or Doneta then types up the client’s directions, gather the necessary materials and order photos.2
Footnotes
1. Kaizen. These files are signs of our progress. When I first started, there was no specific folder where all the designs were saved. Each artist who had created the design had the Photoshop file saved on their computer, wherever they liked. That same artist would find and open that particular Photoshop file, slice it up for a table design, then open up GoLive and cram the design into nested tables. On a good day, this took me 8 hours to create (but only 1 hour for Tim).
A year later, we have centralized our materials. All Photoshop files are housed on the Web Marketing server in their own folder, with backups on the individual artist’s machine as well; the CSS layouts take less time to build (3-4 hours for the layout/presentation) than tables; an HTML file and CSS file supply a skeleton and works as a guideline to stop errors before they happen (such as incomplete doctype declarations in the HTML). Our efforts have been rewarded with less stress: either of us can build the new site, they are no longer dependent on any one particular person. That means while Tim is gone, I can handle building new sites that he originally designed, and vice versa. It also means if one of us is overloaded with packets, the other can easily take on some of these assignments and pick up where the other left off without difficulty.
2. The Web Coordinators’ responsibilities are much more involved than this, but it is outside of the scope of the Design Process. For the record: they coordinate the updates to the Sale Almanac page, compile the materials for the Upcoming Events e-List, obtain new photos from the clients and/or other agencies possessing updated photos, post the Angus Journal magazine to the Angus Journal web site, bill out the hours for each packet, field client calls, and create Sale Reports among many other things.

