As a designer, it pains me to see some interfaces that directly represent the back-end model, not the user's task.
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.
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.
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.
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.
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.