new backend challenge draft #15
Conversation
hidalgofdz
requested review from
bitcero,
jpintor52,
GabrielDzul,
jerolan,
juankuquintana,
migdonio1,
rejonpardenilla and
ricardogamboa
| ## Actors | ||
|
|
||
| ### Visitor | ||
| Is any person that wants to read the articles published in the API. It doesn't have to authenticate herself to do it. |
There was a problem hiding this comment.
It doesn't have to authenticate herself => It doesn't have to be authenticated
|
|
||
| ### Writer | ||
|
|
||
| Is a person that have the permission to create new articles in our API. It has to authenticate herself in order to create, edit and publish articles. |
There was a problem hiding this comment.
It has to authenticate herself => It has to be authenticated
back_end/README.md
Outdated
| - [ ] Add a view to list all the URLs and their short versions. | ||
| - [ ] Update the list of user stories, and the API documentation if we add a new actor called Admin that is the only one with the permission to publish articles but only when an article is "ready to review". Think about how that new actor will change your current implementation and what changes you will need to do. | ||
| - [ ] Deploy the API in a Platform as a Service (Heroku, Blue Ocean, AWS, GCloud, etc) | ||
| - [ ] Dockerize the development environment so the database, programming language version, etc lives in a container. The idea is that when a new developer starts on the project she will not have to configure the development environment by hand. |
There was a problem hiding this comment.
when a new developer starts on the project she will not => when new developers starts on the project they will not
|
|
||
| We want to create an API that allow us to handle articles that could be shown in many clients like mobile apps, websites, text to speech apps, etc. | ||
|
|
||
| For this challenge assume that the writers are already store in the application database. You don't need to create a registration endpoint. |
There was a problem hiding this comment.
It's already stored doesn't it?
|
|
||
| ## API Specification | ||
|
|
||
| We want to create an API that allow us to handle articles that could be shown in many clients like mobile apps, websites, text to speech apps, etc. |
There was a problem hiding this comment.
I had a challenge like this a couple of months ago and it what I like about the introduction is that they give me a lot of bussiness context.
For example: Yellowme runs a web blog where the developers like to upload all sort of articles like "10 common backend issues" and "Personas: A great UX technique". Now it needs a backend API that....
I think this could help the candidate understand the requirements and the interviewer see the candidate problem solving in context.
What do you think? I could help you write this introduction if you like 😄
|
|
||
| ### Article | ||
|
|
||
| An article can be on two possible states. The first one is **drafted** that means that only the writer can see it. The second one is "published" that means that everyone can see it. |
There was a problem hiding this comment.
Just for consistency: Maybe use quotes or bold text on the status names.
| - first name | ||
| - last name | ||
|
|
||
| ## User Stories |
There was a problem hiding this comment.
I like this a lot. Writing this as user stories makes them easier to write better tests.
How much time the candidate have to complete this challenge?
|
|
||
| ## Bonus | ||
| Take 1 or 2, we don't expect for you to do everyone of them. |
There was a problem hiding this comment.
I think this everyone should be separated. "we don't expect for you to do every one of them" but I'm not that sure. 🤔
back_end/README.md
Outdated
| - [ ] Deploy the API in a Platform as a Service (Heroku, Blue Ocean, AWS, GCloud, etc) | ||
| - [ ] Dockerize the development environment so the database, programming language version, etc lives in a container. The idea is that when a new developer starts on the project she will not have to configure the development environment by hand. | ||
| - [ ] Write down every tool or methodology that you know for improving backend developer happiness explaining why you think they are necessary. | ||
| - [ ] Create a deployment pipeline that runs linters, tests, ect every time any branch is push it to the repository. In addition, when a PR is merged to master(main) branch then the app should be deployed. |
|
|
||
| - title | ||
| - body | ||
| - published date |
There was a problem hiding this comment.
this should be on underscore?
Primer draft del nuevo challenge de backend
Notion del challenge (aún sin actualizar): https://www.notion.so/yellowme/Backend-Project-Challenge-1541f42fe92d487f8f2db932d0f22bc8