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

Re: How to Interpret Ridiculous Web Design Job Posts

#11

Post by dwaltrip » Sun, Mar 09, 2014, 2:25 AM UTC

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!

Re: How to Interpret Ridiculous Web Design Job Posts

#12

Post by avalaunch » Sun, Mar 09, 2014, 2:33 AM UTC

codr wrote: post #9

phantomb wrote: post #4

"Excellent communication skills and the ability to work well with others" The author added this in the rewrite, but I think this is exactly the kind of filler that needs to be avoided. These things are mandatory for basically all jobs, and people who can't communicate and work with others don't think they lack these skills anyway.

+1 Every job I've gotten has that line, or something similar.. and yet there are people there that can barely communicate, much less work well with others.

...the presence of those people might have been what prompted the person crafting the job posting to include that line.

Re: How to Interpret Ridiculous Web Design Job Posts

#13

Post by bilalq » Sun, Mar 09, 2014, 3:09 AM 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'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...

Re: How to Interpret Ridiculous Web Design Job Posts

#14

Post by underwater » Sun, Mar 09, 2014, 3:51 AM UTC

bilalq wrote: post #13

dwaltrip wrote: post #11

Earlier quoted context omitted.

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

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.

Re: How to Interpret Ridiculous Web Design Job Posts

#15

Post by vinceguidry » Sun, Mar 09, 2014, 4:14 AM UTC

phantomb wrote: post #4

"Excellent communication skills and the ability to work well with others" The author added this in the rewrite, but I think this is exactly the kind of filler that needs to be avoided. These things are mandatory for basically all jobs, and people who can't communicate and work with others don't think they lack these skills anyway.

That line might not mean a lot to you, but it says a lot to me. They could have left it out, but decided it was important enough to leave in.

My job is an example of such where it was left out. I only have to communicate with people on my team. I do not attend meetings, my work has so little to do with the actual business the company is in I'm effectively in my own little world.

In my interviews, my future boss asked about communication, but emphasized that all of my tasks were going through him. There was concern about the programmer getting mad at people asking me for stuff that they don't understand. Apparently that's happened before. What was important was my independence and ability to solve problems, because nobody else is going to be able to help me. Suited me just fine.

What this requirement tells me is that my work is going to intersect significantly with other people who don't do what I do and I'll be a part of planning meetings and such. I might also be called upon to give reports to people who don't know what I do.

Re: How to Interpret Ridiculous Web Design Job Posts

#16

Post by einhverfr » Sun, Mar 09, 2014, 6:33 AM 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!

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.

Re: How to Interpret Ridiculous Web Design Job Posts

#17

Post by pearjuice » Sun, Mar 09, 2014, 9:51 AM UTC

    Knowledge of Java/JavaScript

Re: How to Interpret Ridiculous Web Design Job Posts

#18

Post by hkmurakami » Sun, Mar 09, 2014, 10:55 AM UTC

vinceguidry wrote: post #15

phantomb wrote: post #4

"Excellent communication skills and the ability to work well with others" The author added this in the rewrite, but I think this is exactly the kind of filler that needs to be avoided. These things are mandatory for basically all jobs, and people who can't communicate and work with others don't think they lack these skills anyway.

That line might not mean a lot to you, but it says a lot to me. They could have left it out, but decided it was important enough to leave in. My job is an example of such where it was left out. I only have to communicate with people on my team. I do not attend meetings, my work has so little to do with the actual business the company is in I'm effectively in my own little world. In my interviews, my future boss asked…

Maybe that's best put in the "Job Description" section, rather than in the Qualifications section?

Re: How to Interpret Ridiculous Web Design Job Posts

#19

Post by nawitus » Sun, Mar 09, 2014, 11:37 AM UTC

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.

Re: How to Interpret Ridiculous Web Design Job Posts

#20

Post by james-skemp » Sun, Mar 09, 2014, 11:50 AM 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.

I would keep 'version control' in (and looked for it on their resume during my last two searches).

It's surprising how many people don't use source control, but they do tend to work in smaller shops (one or two developers) or places with little change.