[jaspero]

I felt that the author kind of mixed up front-end engineer and graphic designer. Good front-end engineers(developers) are not necessarily good graphic designers and vice versa.

I am a computer science graduate and front-end developer with four years of industry experience and I started it around 10 years back as a hobby. I do some graphic designing too but my strong domains are html,css and javascript. All of them are self-learned as the author has mentioned.

Wherever I worked, I hated the fact that people kind of undermine the importance of front-end. They bring in some software engineers and make them work with me. Everyone thinks they know html and css and its pretty easy.

Since there are no way of measuring the quality of their code, I get really frustrated seeing people undermine my domain. Even with this much of experience I feel there is so much to learn and so much improvements can be made.

[sudont]

What's even worse is when the engineers usurp everything, from front-end to UX and design.

As a designer, it pains me to see some interfaces that directly represent the back-end model, not the user's task.

[Dylanlacey]

The reverse is just as bad.

Dear GDs: Let's not fight anymore, lets work together to make beautiful web-babies.

Love, the Engineers.

PS: Did you lose weight? You look great! Lose the hipster hat.

[sudont]

On second glance, my post was a bit troll-ish.

It was more in reference to large enterprise apps, the one in mind combines 4 formerly separate, disparate apps, a mail server and a file manager into a single install, and doesn’t have any bearing at all to what an actual workflow is. Each Ext tab basically dumps the contents of a database out, or loads an iframe that contains a different install’s instance.

[Tyrant505]

why yes, thank you. Did you get a tan?

[BillSaysThis]

are you suggesting I was not working during sunlight hours every damn day for the last three months?

[Stormbringer]

As an front-end engineer, it pains me to see some pixel perfect thing of beauty that a graphic designer has whipped up in Macromedia, with the most $deity-awful pile of auto-generated crud backing it up, with no considerations for usability, or feasibility of making it work on multiple different browsers.

Even getting something close to looking the same across multiple browsers and resolutions is a herculean task.

So yeah, you pooped out something pretty. Well done and all that. Now the hard work begins, polishing that turd until it is dynamic (i.e. loads the appropriate data), usable and accessible.

Get yourself some potty training (e.g. roll the html by hand) and then we'll talk about respect.

[sudont]

I am a front-end, and know Cocoa and deal with back-end systems in my working capacity, so I think I can comment on both sides.

When I said "As a designer," I meant "in the eyes of a designer." Most people here like to wear enough hats that it makes sense.

Try to be a little less condescending next time.

[Tyrant505]

I agree with how you assumed he got the two "fields" messed up. I learned adobe first, then html and css, now im learning ruby(programming in general too) and rails / javascript. There is so much to learn. I am learning the "stack" out of necessity in the "do it or shut up" startup world but I really am amazed how a small amount of others seem to tackle all of this with a high quality level. There really is so much to learn. Not to say that serious coders don't have their work cut out for them but the depth and time and SKILL necessary for even less than great mastery is astonishing. I salute you all who seem to flow gracefully in this "expect everything" world.

[NHQ]

I think it was pretty clear he was not talking about graphic designers. Why would a writer or musician make a good graphic designer? They may or may not, which is not the point. What makes your artist types good at front end are the things that come with the practice of any art: rhythm, composition, juxtaposition, etc.