« Flashbelt's Student Feedback Zone | Main | Recycle your Cell Phone and Support GalaxyGoo »

Why am I worried? I should be excited!

I'm trying to be positive, and think of all the things that could be possible when Macromedia is absorbed by Adobe. But I can't shake this nervous feeling in my gut. Why? I think it may have to do with the fact that I am data-centric and information-centric.

Over the years, I have come to see the beauty of well separated content and presentation. This doesn't mean that they are irrelevant to each other, it just means that when the presentation is stripped away, the information should still be useful. Over the years, I've also had encounters with that particular species of designers that doesn't understand this at all. And doesn't value it, at all. And they've always been PS users. So, much like folks burned by Flash Pop-up ads, I am very nervous of anything to do with PS imposing it's own "work flow" on my Flash, CSS, and HTML.

To illustrate my point, how many coders (HTML AS, whatever) have felt like they were beating their head against a wall explaining why text is text and not a graphic? I once actually had to talk a designer into NOT formatting text in Photoshop before importing it into Flash.

My optimistic self is starting to spark a little. What if Adobe really pays attention? What if they conduct studies to see how we all work? What if they find a way to make it easier for us all to work together? Case in point, they could add a feature to Photoshop that makes the text a guide layer, so that the Flash expert could see what the designer intended and make it more usable.

Now I wonder what I can do to make this all go in a positive direction. I issue a challenge: Macromedia and Adobe, tell me how I can help make this the best it can be!

Comments

Here here. So long as the lines of communication are left open, I figure there's plenty of pie in this poop.

I hear you! Programmers and designers think very differently.

Programmers tend to equate good design with "fitness to purpose". We consider a lot of factors. Functionality, file-size, clarity, usability, and ensuring that the whole caboodle works. If we build something, we do it from the inside out. Function first, test a prototype, and then add the sugar coating later.

Never show a designer a prototype for your new idea. They won't get it, and they'll just critisize you for your makeshift interface.

Designers just want to make things look nice, whatever the consequences. They don't understand engineering trade-offs.

You must joking Daniel.
Designers can appreciate good programmers.
We need them all the time. We have learn to talk each other. I use to make this comparison.
The programmers are the engineers and the designers are the motobike raiders.
They have to work together!
I feel that flash recently started to be a bit wrong in its philosopy. There is not need to incourage using text components when you can you can use a text field. But sometimes programmers are like chiefs at the banquets. They bring on the tables everything too many things. Red wine white wine and beer! Hmmm!
But cheer you up Kristin we need each other, all the time and here we go!
Ciao Shirley

Fear of the unknown, perhaps?

;-)

I wouldn't worry, Kristin. I have worked with Adobe products as a developer and they have the resources and capabilities to support both those who code and those who don't.

In fact, with this aquisition, I would say they now have an excellent oportunity to provide those of us who do both with a tightly integrated toolset, leading to a burst of creative oppotunities.

I welcome it. Flash has seemed a bit run down lately. This is good. I hope it makes it all the way...

Designers don't just make pretty pictures. I'm a designer but code is as much a part of my toolset as is Photoshop or Freehand. It's all just part of the mix. Let's stop having to put people into boxes.

And as for Adobe taking over Macromedia I actually welcome it. Flash is an insanley great product that has revolutionised design. But let's face it - it sucks as an application you use everyday. I have never had Photoshop crash on me. Ever. And that's in 10 years of use. Adobe software is rock solid (i'm on a Mac BTW). Flash is very flaky. Have you tried the pen tool in Flash. It's crap. Oh and the space bar to switch to the hand move tool - works when it feels like it. Photoshop never does that. So I'm not dissin Flash - I just welcome the prospect of Adobe bringing their rock solid development to the pot.

I'll shut up now.

My early nervousness has settled down, now :-)

Shirley..haha...I can't resist your comments about wine and beer. :-) I'd say it depends on what type of social event it is. When my guests arrive I offer them a choice. If it's a sit-down dinner, they bring their beverages to the table but I will usually serve what goes best with the meal. Now, if it's a less formal affair, I will of course have a selection of wines to choose from as well as beer...not to mention the non-alcoholic options.

Brendan...of course designers do more than make pretty pictures--at least the good ones do ;-) When I've run into trouble with a designer, it's when they just don't understand interactive media. I like to make the analogy of trying to paint with clay.

While it may seem that I'm trying to put people in boxes, I'm really interested in the problem sot that we can find a solution. We have a great opportunity here, to improve communication between the people who perform different tasks in our field.

i think the joining of forces of these companies could be really helpful - integrating the pure design with funtional elements. i just hope that adobe learns from macromedia's interfaces - i find them much more intuitive and much less bloated. no more palettes in photoshop, or we'll all have to work on quadruple monitor systems.

as for design and function, good designers know the message is the content and design helps make it more appealing, but also more useful.