About Archive Tag Cloud Translations RSS

You are writing a comment about Skew, The Frontend Engineer's Misery, here is a quick summary:

A look at the frontend engineer's primary pain point: product skew. While skew impacts everyone, it beats on the frontend engineer early and frequently. Think frontend engineer's have the easy half of engineering? Well, let's talk about that.


You are responding to this comment written by David Mosher on April 29th 2009, 17:24.

I work in a relatively small team (7 developers) and we still have these problems. Regardless of team size I think the common factor here is, as you put it Will, "[giving] the frontend team greater ownership of their product."

The frustration I run into as a FE engineer is almost 100% attributable to the fact that I don't design what I have to implement.


Please be aware that comment forms go stale after one hour.





Comments may make use of LifeFlow MarkDown. Raw html will be escaped.


Quick Introduction to LifeFlow MarkDown Syntax

A highlighted code block:

@@ ruby
def a (b, c):
  b * c
end
@@

Other common languages work as well: scheme, python, java, html, etc.

Other markdown syntax:

 ### This is an h3 title
#### This is an h4 title
**this is bold**
*this is italics*

1. This is an
2. ordered list

* And an unordered
* list too

[this is a link](http://www.lethain.com/ "Lethain")