3 ms·

Don't crap on the CSS developer for honing his craft and sharing his knowledge. That's like saying the guy who developed the CSS for apple.com shouldn't share

Don't crap on the CSS developer for honing his craft and sharing his knowledge. That's like saying the guy who developed the CSS for apple.com shouldn't share his CSS knowledge because because customers want a 5mm thick iPad and Apple hasn't given that to them.

thejerz 14y ago
While I appreciate your use of colorful language (i.e., "crap"), your point is not consistent with the author or the article. The author prides himself on looking outside the CSS; he says developers should question the bigger picture into which the CSS fits, like a Rails developer is expected to do. My point is simply that he should extend that line of questioning further and ask whether constructing advanced design patterns for CSS is the best use of time given other stakeholder priorities.
- markdown 14y ago
  If you hire someone to paint your house, you don't expect him to spend time wondering about whether the house needs another room, or whether the kitchen drawers are deep enough. That's someone else's job. The house painter has single job; paint the house to the very best of his abilities. If you have a problem with the design of the house, take it up with the home-owner. He may or may not decide to accommodate your needs, but in any case, whether or not he decides to do so is irrelevant to the painter. His job is to paint the house.
  - rimantas 14y ago
    That's an extremely poor analogy.
- davidwoof1 14y ago
  You work as a development project manager, don't you? It takes a certain kind of unique mindset to encounter excellent work somebody has done and use it as an opportunity to bash them because unrelated teams with unrelated skillsets are not churning out the features you want at the rate you want them. How in the world is doing his job the best he can do it somehow not the best use of his time? What exactly is your argument here? Is it that appfolio should not hire such excellent front end developers because their backend is still lacking? Or is it that the front end developers should do worse work to mesh better with what you consider to be the failings of the back end? Even if the css author had anything to do with your complaints, your argument betrays the absolute worst mindset that one can find in software management: the idea that quality work is time-consuming rather than time-saving.

thejerz 14y ago

While I appreciate your use of colorful language (i.e., "crap"), your point is not consistent with the author or the article. The author prides himself on looking outside the CSS; he says developers should question the bigger picture into which the CSS fits, like a Rails developer is expected to do. My point is simply that he should extend that line of questioning further and ask whether constructing advanced design patterns for CSS is the best use of time given other stakeholder priorities.

markdown 14y ago
If you hire someone to paint your house, you don't expect him to spend time wondering about whether the house needs another room, or whether the kitchen drawers are deep enough. That's someone else's job. The house painter has single job; paint the house to the very best of his abilities. If you have a problem with the design of the house, take it up with the home-owner. He may or may not decide to accommodate your needs, but in any case, whether or not he decides to do so is irrelevant to the painter. His job is to paint the house.
- rimantas 14y ago
  That's an extremely poor analogy.
davidwoof1 14y ago
You work as a development project manager, don't you? It takes a certain kind of unique mindset to encounter excellent work somebody has done and use it as an opportunity to bash them because unrelated teams with unrelated skillsets are not churning out the features you want at the rate you want them. How in the world is doing his job the best he can do it somehow not the best use of his time? What exactly is your argument here? Is it that appfolio should not hire such excellent front end developers because their backend is still lacking? Or is it that the front end developers should do worse work to mesh better with what you consider to be the failings of the back end? Even if the css author had anything to do with your complaints, your argument betrays the absolute worst mindset that one can find in software management: the idea that quality work is time-consuming rather than time-saving.