Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This misses out some important parts. The original job description had:

  * Proficient with javascript, good knowledge of jQuery and
    creating/debugging jQuery plugins
  * Understanding of OO principles, especially with regard to
    HTML/CSS/JS and creating reusable UI components
  * Expert knowledge of browser quirks and creating web apps that
    are consistent across all major browsers
  * Experience optimizing front end code for performance/speed
  * Experience optimizing front end code for SEO
  * Ability to code detailed, functional pages from mockups in
    collaboration with web designers
All of these are diluted down to:

  * Solid understanding of front-end languages and frameworks
    (primarily HTML, CSS, JavaScript, and jQuery)
... and misses the specifics entirely. Some developers are good with JavaScript and jQuery, but don't have the mindset to be able to debug jQuery plugins, or build reusable components vs. hacking a quick and dirty one-off implementation, or understand different quirks between browsers ("Doesn't jQuery do that for me?"), or have to deal with performance, or have any knowledge of SEO work, or is only able to take existing HTML and tweak it but is unable to output polished HTML, CSS, and JavaScript from design mockups.

For small companies who need someone to hit the ground running, it's a disservice to themselves to not ask for specific skillsets. They'll end up wasting time interviewing unqualified candidates. If you're part of a larger company or you're willing to train someone who is smart, gets things done, and can learn on their feet then it's fine to be vague about what you're looking for since you're willing to accept that any hire you make may take several months to get up to speed (and possibly never grok some skills) with what you actually want them to have been doing from day one.



I personally wish the job description would have elaborated on OO principles for HTML and CSS. Sounds interesting!


This.

To me that reads very much like the posting I saw that had as a skill requirement (and I quote):

"Postgre PLEASE CHECK GOOGLE FOR CORRECT SPELLING"

Personally when I see stuff like that it is a sure sign that the person writing the job listing has no clue what the job entails.


I'm not sure if you were being sarcastic or not (text is poor medium for conveying such things), but OOCSS is very much a real thing. I love writing SASS in such a way.

See this post for more info: http://ianstormtaylor.com/oocss-plus-sass-is-the-best-way-to...


OOCSS is poorly named and has nothing at all to do with object oriented programming.


The first part of the name before the underscore is the CSS superclass name. The next part after the underscore is the CSS subclass name. And the properties in the style tag are the CSS instance variables.


I think that boils down to: "Oo! Oo! Look at this pretty page I just made. Oooooo!"




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: