Mixing
Server side UI vs. Client side UI [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
-4
down vote
favorite
I'm reading a job description which reads...
You are an experienced front-end developer with expertise in Javascript,HTML,CSS & server side UI frameworks (PHP/Python/Node.js).
I've always felt that it's best to render on the client side so I use AngularJS for this. Not PHP/Python/Node.js. This makes me wonder if the job description is wrong; server-side UI doesn't sound right to me.
Should I ask them about it or just apply anyway? If I apply and get an interview, should I try to explain why that approach doesn't sound right?
job-description
edited Dec 9 '14 at 21:59
Monica Cellio♦
43.7k17114191
asked Dec 9 '14 at 19:28
fauverism
180513
closed as off-topic by Joe Strazzere, Chris E, IDrinkandIKnowThings, gnat, DJClayworth Dec 9 '14 at 21:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – Joe Strazzere, gnat
suggest improvements |Â
up vote
-4
down vote
favorite
I'm reading a job description which reads...
You are an experienced front-end developer with expertise in Javascript,HTML,CSS & server side UI frameworks (PHP/Python/Node.js).
I've always felt that it's best to render on the client side so I use AngularJS for this. Not PHP/Python/Node.js. This makes me wonder if the job description is wrong; server-side UI doesn't sound right to me.
Should I ask them about it or just apply anyway? If I apply and get an interview, should I try to explain why that approach doesn't sound right?
job-description
edited Dec 9 '14 at 21:59
Monica Cellio♦
43.7k17114191
asked Dec 9 '14 at 19:28
fauverism
180513
closed as off-topic by Joe Strazzere, Chris E, IDrinkandIKnowThings, gnat, DJClayworth Dec 9 '14 at 21:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – Joe Strazzere, gnat
I think it could fit here if it could be made more generic, though I think the author is asking the wrong question (which I've explained in my answer). When considering the underlying issue, it's quite a bit more on topic for this site (which I've addressed in my answer).
– Shauna
Dec 9 '14 at 20:03
2
This question appears to be off-topic because it is about job functions and not about navigating the workplace as described in the help center
– IDrinkandIKnowThings
Dec 9 '14 at 20:12
I'm not arguing that it isn't offtopic as it's currently worded. If the asker did actually intend to ask about front end languages vs backend languages, then there's no question that it's better suited to programmers.SE. However, if it's more about the job description vs actual duties, then I think that it can fit here if reworded.
– Shauna
Dec 9 '14 at 20:16
@fauverism I made an edit to your question to try to make it fit The Workplace better. You might ask your question about client-side versus server-side approaches elsewhere on Stack Exchange (maybe Programmers). I focused this question on the job description and application process. If I've failed to capture your intentions or put too many words in your mouth you can edit further. Thanks for understanding.
– Monica Cellio♦
Dec 9 '14 at 22:02
suggest improvements |Â
up vote
-4
down vote
favorite
up vote
-4
down vote
favorite
I'm reading a job description which reads...
You are an experienced front-end developer with expertise in Javascript,HTML,CSS & server side UI frameworks (PHP/Python/Node.js).
I've always felt that it's best to render on the client side so I use AngularJS for this. Not PHP/Python/Node.js. This makes me wonder if the job description is wrong; server-side UI doesn't sound right to me.
Should I ask them about it or just apply anyway? If I apply and get an interview, should I try to explain why that approach doesn't sound right?
job-description
edited Dec 9 '14 at 21:59
Monica Cellio♦
43.7k17114191
asked Dec 9 '14 at 19:28
fauverism
180513
I'm reading a job description which reads...
You are an experienced front-end developer with expertise in Javascript,HTML,CSS & server side UI frameworks (PHP/Python/Node.js).
I've always felt that it's best to render on the client side so I use AngularJS for this. Not PHP/Python/Node.js. This makes me wonder if the job description is wrong; server-side UI doesn't sound right to me.
Should I ask them about it or just apply anyway? If I apply and get an interview, should I try to explain why that approach doesn't sound right?
job-description
edited Dec 9 '14 at 21:59
Monica Cellio♦
43.7k17114191
asked Dec 9 '14 at 19:28
fauverism
180513
edited Dec 9 '14 at 21:59
Monica Cellio♦
43.7k17114191
edited Dec 9 '14 at 21:59
Monica Cellio♦
43.7k17114191
edited Dec 9 '14 at 21:59
Monica Cellio♦
43.7k17114191
43.7k17114191
asked Dec 9 '14 at 19:28
fauverism
180513
asked Dec 9 '14 at 19:28
fauverism
180513
asked Dec 9 '14 at 19:28
fauverism
180513
180513
closed as off-topic by Joe Strazzere, Chris E, IDrinkandIKnowThings, gnat, DJClayworth Dec 9 '14 at 21:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – Joe Strazzere, gnat
closed as off-topic by Joe Strazzere, Chris E, IDrinkandIKnowThings, gnat, DJClayworth Dec 9 '14 at 21:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – Joe Strazzere, gnat
I think it could fit here if it could be made more generic, though I think the author is asking the wrong question (which I've explained in my answer). When considering the underlying issue, it's quite a bit more on topic for this site (which I've addressed in my answer).
– Shauna
Dec 9 '14 at 20:03
2
This question appears to be off-topic because it is about job functions and not about navigating the workplace as described in the help center
– IDrinkandIKnowThings
Dec 9 '14 at 20:12
I'm not arguing that it isn't offtopic as it's currently worded. If the asker did actually intend to ask about front end languages vs backend languages, then there's no question that it's better suited to programmers.SE. However, if it's more about the job description vs actual duties, then I think that it can fit here if reworded.
– Shauna
Dec 9 '14 at 20:16
@fauverism I made an edit to your question to try to make it fit The Workplace better. You might ask your question about client-side versus server-side approaches elsewhere on Stack Exchange (maybe Programmers). I focused this question on the job description and application process. If I've failed to capture your intentions or put too many words in your mouth you can edit further. Thanks for understanding.
– Monica Cellio♦
Dec 9 '14 at 22:02
suggest improvements |Â
I think it could fit here if it could be made more generic, though I think the author is asking the wrong question (which I've explained in my answer). When considering the underlying issue, it's quite a bit more on topic for this site (which I've addressed in my answer).
– Shauna
Dec 9 '14 at 20:03
2
This question appears to be off-topic because it is about job functions and not about navigating the workplace as described in the help center
– IDrinkandIKnowThings
Dec 9 '14 at 20:12
I'm not arguing that it isn't offtopic as it's currently worded. If the asker did actually intend to ask about front end languages vs backend languages, then there's no question that it's better suited to programmers.SE. However, if it's more about the job description vs actual duties, then I think that it can fit here if reworded.
– Shauna
Dec 9 '14 at 20:16
@fauverism I made an edit to your question to try to make it fit The Workplace better. You might ask your question about client-side versus server-side approaches elsewhere on Stack Exchange (maybe Programmers). I focused this question on the job description and application process. If I've failed to capture your intentions or put too many words in your mouth you can edit further. Thanks for understanding.
– Monica Cellio♦
Dec 9 '14 at 22:02
I think it could fit here if it could be made more generic, though I think the author is asking the wrong question (which I've explained in my answer). When considering the underlying issue, it's quite a bit more on topic for this site (which I've addressed in my answer).
– Shauna
Dec 9 '14 at 20:03
I think it could fit here if it could be made more generic, though I think the author is asking the wrong question (which I've explained in my answer). When considering the underlying issue, it's quite a bit more on topic for this site (which I've addressed in my answer).
– Shauna
Dec 9 '14 at 20:03
2
2
This question appears to be off-topic because it is about job functions and not about navigating the workplace as described in the help center
– IDrinkandIKnowThings
Dec 9 '14 at 20:12
This question appears to be off-topic because it is about job functions and not about navigating the workplace as described in the help center
– IDrinkandIKnowThings
Dec 9 '14 at 20:12
I'm not arguing that it isn't offtopic as it's currently worded. If the asker did actually intend to ask about front end languages vs backend languages, then there's no question that it's better suited to programmers.SE. However, if it's more about the job description vs actual duties, then I think that it can fit here if reworded.
– Shauna
Dec 9 '14 at 20:16
I'm not arguing that it isn't offtopic as it's currently worded. If the asker did actually intend to ask about front end languages vs backend languages, then there's no question that it's better suited to programmers.SE. However, if it's more about the job description vs actual duties, then I think that it can fit here if reworded.
– Shauna
Dec 9 '14 at 20:16
@fauverism I made an edit to your question to try to make it fit The Workplace better. You might ask your question about client-side versus server-side approaches elsewhere on Stack Exchange (maybe Programmers). I focused this question on the job description and application process. If I've failed to capture your intentions or put too many words in your mouth you can edit further. Thanks for understanding.
– Monica Cellio♦
Dec 9 '14 at 22:02
@fauverism I made an edit to your question to try to make it fit The Workplace better. You might ask your question about client-side versus server-side approaches elsewhere on Stack Exchange (maybe Programmers). I focused this question on the job description and application process. If I've failed to capture your intentions or put too many words in your mouth you can edit further. Thanks for understanding.
– Monica Cellio♦
Dec 9 '14 at 22:02
suggest improvements |Â
1 Answer
1
active
oldest
votes
up vote
-1
down vote
accepted
Simply put -- most companies suck at writing job postings. (Also, I think you're asking the wrong question, given you've posted the question on workplace.SE, as opposed to programmers.SE.)
The sad truth is that a large portion of companies run their job postings through just about everyone but the people that actually know how to do the job (this is especially the case for highly skilled positions). The group needing the person might send their requirements to HR, then HR writes the actual job description for the posting. As a result, you end up with things like requiring server side technologies for front end devs or designers, more years of experience than a technology has been around, "entry level" positions that require ludicrous amounts of knowledge, and other such oddities.
This example job description isn't about whether one should use Node to render client side UI (by the way, it would all ultimately get converted to HTML, anyway), but rather whether what they say they want is what they actually need. It says nothing about whether their requirement of a front end developer needing to know server side languages is actually an accurate or reasonable expectation.
Personally, I ignore such job postings entirely unless I have internal contacts. Odds are, your resume will go through HR's game of buzzword bingo and get tossed before it ever sees anyone who actually knows anything about the job, and if it does make it through, the odds are higher that it won't be a good match than a job with a more reasonable/accurate posting.
answered Dec 9 '14 at 20:01
Shauna
3,53621524
suggest improvements |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
-1
down vote
accepted
Simply put -- most companies suck at writing job postings. (Also, I think you're asking the wrong question, given you've posted the question on workplace.SE, as opposed to programmers.SE.)
The sad truth is that a large portion of companies run their job postings through just about everyone but the people that actually know how to do the job (this is especially the case for highly skilled positions). The group needing the person might send their requirements to HR, then HR writes the actual job description for the posting. As a result, you end up with things like requiring server side technologies for front end devs or designers, more years of experience than a technology has been around, "entry level" positions that require ludicrous amounts of knowledge, and other such oddities.
This example job description isn't about whether one should use Node to render client side UI (by the way, it would all ultimately get converted to HTML, anyway), but rather whether what they say they want is what they actually need. It says nothing about whether their requirement of a front end developer needing to know server side languages is actually an accurate or reasonable expectation.
Personally, I ignore such job postings entirely unless I have internal contacts. Odds are, your resume will go through HR's game of buzzword bingo and get tossed before it ever sees anyone who actually knows anything about the job, and if it does make it through, the odds are higher that it won't be a good match than a job with a more reasonable/accurate posting.
answered Dec 9 '14 at 20:01
Shauna
3,53621524
suggest improvements |Â
up vote
-1
down vote
accepted
Simply put -- most companies suck at writing job postings. (Also, I think you're asking the wrong question, given you've posted the question on workplace.SE, as opposed to programmers.SE.)
The sad truth is that a large portion of companies run their job postings through just about everyone but the people that actually know how to do the job (this is especially the case for highly skilled positions). The group needing the person might send their requirements to HR, then HR writes the actual job description for the posting. As a result, you end up with things like requiring server side technologies for front end devs or designers, more years of experience than a technology has been around, "entry level" positions that require ludicrous amounts of knowledge, and other such oddities.
This example job description isn't about whether one should use Node to render client side UI (by the way, it would all ultimately get converted to HTML, anyway), but rather whether what they say they want is what they actually need. It says nothing about whether their requirement of a front end developer needing to know server side languages is actually an accurate or reasonable expectation.
Personally, I ignore such job postings entirely unless I have internal contacts. Odds are, your resume will go through HR's game of buzzword bingo and get tossed before it ever sees anyone who actually knows anything about the job, and if it does make it through, the odds are higher that it won't be a good match than a job with a more reasonable/accurate posting.
answered Dec 9 '14 at 20:01
Shauna
3,53621524
suggest improvements |Â
up vote
-1
down vote
accepted
up vote
-1
down vote
accepted
Simply put -- most companies suck at writing job postings. (Also, I think you're asking the wrong question, given you've posted the question on workplace.SE, as opposed to programmers.SE.)
The sad truth is that a large portion of companies run their job postings through just about everyone but the people that actually know how to do the job (this is especially the case for highly skilled positions). The group needing the person might send their requirements to HR, then HR writes the actual job description for the posting. As a result, you end up with things like requiring server side technologies for front end devs or designers, more years of experience than a technology has been around, "entry level" positions that require ludicrous amounts of knowledge, and other such oddities.
This example job description isn't about whether one should use Node to render client side UI (by the way, it would all ultimately get converted to HTML, anyway), but rather whether what they say they want is what they actually need. It says nothing about whether their requirement of a front end developer needing to know server side languages is actually an accurate or reasonable expectation.
Personally, I ignore such job postings entirely unless I have internal contacts. Odds are, your resume will go through HR's game of buzzword bingo and get tossed before it ever sees anyone who actually knows anything about the job, and if it does make it through, the odds are higher that it won't be a good match than a job with a more reasonable/accurate posting.
answered Dec 9 '14 at 20:01
Shauna
3,53621524
Simply put -- most companies suck at writing job postings. (Also, I think you're asking the wrong question, given you've posted the question on workplace.SE, as opposed to programmers.SE.)
The sad truth is that a large portion of companies run their job postings through just about everyone but the people that actually know how to do the job (this is especially the case for highly skilled positions). The group needing the person might send their requirements to HR, then HR writes the actual job description for the posting. As a result, you end up with things like requiring server side technologies for front end devs or designers, more years of experience than a technology has been around, "entry level" positions that require ludicrous amounts of knowledge, and other such oddities.
This example job description isn't about whether one should use Node to render client side UI (by the way, it would all ultimately get converted to HTML, anyway), but rather whether what they say they want is what they actually need. It says nothing about whether their requirement of a front end developer needing to know server side languages is actually an accurate or reasonable expectation.
Personally, I ignore such job postings entirely unless I have internal contacts. Odds are, your resume will go through HR's game of buzzword bingo and get tossed before it ever sees anyone who actually knows anything about the job, and if it does make it through, the odds are higher that it won't be a good match than a job with a more reasonable/accurate posting.
answered Dec 9 '14 at 20:01
Shauna
3,53621524
edited Dec 9 '14 at 20:23
answered Dec 9 '14 at 20:01
Shauna
3,53621524
answered Dec 9 '14 at 20:01
Shauna
3,53621524
answered Dec 9 '14 at 20:01
Shauna
3,53621524
3,53621524
suggest improvements |Â
suggest improvements |Â
I think it could fit here if it could be made more generic, though I think the author is asking the wrong question (which I've explained in my answer). When considering the underlying issue, it's quite a bit more on topic for this site (which I've addressed in my answer).
– Shauna
Dec 9 '14 at 20:03
2
This question appears to be off-topic because it is about job functions and not about navigating the workplace as described in the help center
– IDrinkandIKnowThings
Dec 9 '14 at 20:12
I'm not arguing that it isn't offtopic as it's currently worded. If the asker did actually intend to ask about front end languages vs backend languages, then there's no question that it's better suited to programmers.SE. However, if it's more about the job description vs actual duties, then I think that it can fit here if reworded.
– Shauna
Dec 9 '14 at 20:16
@fauverism I made an edit to your question to try to make it fit The Workplace better. You might ask your question about client-side versus server-side approaches elsewhere on Stack Exchange (maybe Programmers). I focused this question on the job description and application process. If I've failed to capture your intentions or put too many words in your mouth you can edit further. Thanks for understanding.
– Monica Cellio♦
Dec 9 '14 at 22:02