h5bp / Front-end-Developer-Interview-Questions

A list of helpful front-end related questions you can use to interview potential candidates, test yourself or completely ignore.

Home Page:https://h5bp.org/Front-end-Developer-Interview-Questions/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Define an editorial structure/editorial guidelines

roblarsen opened this issue · comments

This repo is basically prose. In most projects that are prose-based, there are editorial guidelines and human beings that serve as editors. I think it would help to clarify some of those things on this project.

It will be a stretch to create something like a style guide, but that would be the ultimate goal. In the interim, some words in the readme/contributing docs about creating a single editorial voice will codify that expectation. I am also anointing myself "editor" so that there's an expectation about receiving feedback on the way a question is worded.

(why me? I've interviewed hundreds of candidates on three continents, I've written five books and since I've inherited this repo I might as well make it enjoyable 😺)

I would be happy to have other folks with professional experience with words help out crafting a unified voice for the project and/or wordsmithing questions as they come in.

👍🏻 Love it. A few things I'd love to keep in mind going forward (& which were tennants of this project from the outset):

  • tone should always be open, understanding, encouraging etc. (we should all want interviews to be successful)
  • the questions/challenges should be learning opportunities & jumping off points for discussion (boolean questions & statements should be avoided if possible)
  • no answers (everyone has their own way of interpreting & potentially communicating their understanding)
commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

commented

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.