How to Interpret Ridiculous Web Design Job Posts • Hacker News Board

Re: How to Interpret Ridiculous Web Design Job Posts

#31

Post by SimHacker » Mon, Mar 10, 2014, 2:46 PM UTC

dwaltrip wrote: post #11

biot wrote: post #2

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…

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

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

Re: How to Interpret Ridiculous Web Design Job Posts

#32

Post by SimHacker » Mon, Mar 10, 2014, 2:56 PM UTC

underwater wrote: post #14

bilalq wrote: post #13

Earlier quoted context omitted.

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.

Re: How to Interpret Ridiculous Web Design Job Posts

#33

Post by SimHacker » Mon, Mar 10, 2014, 3:00 PM UTC

kazagistar wrote: post #28

Myrmornis wrote: post #8

Earlier quoted context omitted.

"not an asshole".

In which jobs is this not a requirement?

Groupon sales rep: http://eater.com/archives/2013/08/19/groupon-sales-rep-alleg...

Re: How to Interpret Ridiculous Web Design Job Posts

#34

Post by SimHacker » Mon, Mar 10, 2014, 3:15 PM UTC

nawitus wrote: post #19

You could leave these two bits out: * Ability to work with a version control system (like SVN) in a team environment * using IDEs like Eclipse If someone has worked as a software engineer for more than 6 months, that someone already knows how to "use IDEs" and version control.

Tell that to the Mt. Gox Software Development Department.