Giter Site home page Giter Site logo

ux-ui's People

Contributors

afeeeling avatar frenchris avatar

Watchers

 avatar  avatar  avatar

Forkers

riamon-v

ux-ui's Issues

The UX piscine exercises

I will use the first exercise as example to point some problems of the exercises:

1 - The exercises needs a proper name not something like (ux-1-1).
2 - The readme is set up wrongly, you need to remove the interviews to another .md file because this way the readme seams endless.(avoid endless readmes)
3 - The deliverables need to be more specific, the type of doc would be nice for example.
4 - You should give only a general context about the quest in the first exercise to avoid repetition in every other exercise.
5 - The instructions must be clear and direct, it must be specified in the readmes what you ask in the audits.

Some more aspects:

  • You need to find a way to not give the solutions for the exercise in the audits, as the students have access to them.
  • The examples that you give on the audit files need to be given in the readme and not on the audit, the audit should only contain the Questions.(i advise to give less examples, and the examples should not be the actual solutions).

Caution:

In ux-2-2 you should not advise People to go outside to talk with strangers, specially in the schools where we cant know the age of the students. (Conduct the interview inside the schools only or at home)

Projects 1,2,3,4

General Project review:

  • The projects need new audits, it has the same problem as inside the piscines, wrong structure, no Yes/NO questions
  • One project is divided in two parts the UI and the UX i suppose, but:
    • The readmes are the same in both parts so it needs some changes as its not relevant to have two readmes with the same info.
    • The structure of the readme is not the same as ours as well, we can accept some of the changes but the part of the presentations we need to think about a solution for that. We don't have the concept of presentations in the curriculum so we need to check if it is possible to have it or not.

Audits in the UX piscine

What we want you to do is create a per-quest audit on the UX piscine.
Basically, you need to create an audit that covers all exercises within the quest at once, to avoid problems for students to always be looking for auditors

1 - The audit format is wrong. We have a specific way to create audits in order for them to work.
The structure is :

#### Functional ( where you add your mandatory questions)
#### Basic (Where you can add bonus questions)
#### Social  (Where you can add social questions)

You can check it here: https://github.com/01-edu/public/blob/master/subjects/push-swap/audit/README.md

2 - The audit questions must be of the type (YES or NO) where the students passes only if the mandatory questions are answered YES. If any of those are answered as NO the audit will finish there and the student fails the project. Again you can check it on the example above.

3 - In some audits you are giving the answers to the student, what makes the audit itself a cheat, you should not do that.

4 - You need to avoid text in the audits that are not questions and answers.

The Global file structure needs to be fixed.

  • Naming the quests properly (instead of ux-1 you need to give a global name for the quest) for example:

ux-1 --> "global-name-that-involves-all-exercises"

  • Naming the exercises properly:

    ux-1-1 --> user-interviews
    ux-1-2 --> analytics

Th UI piscine needs to be divided in orther to become Projects

This piscine will become a bunch of projects: (in order to avoid a long piscine experience)

1 - Each of the Quests will be one project with a lot of tasks which are the exercises themselves. The piscine has 5 quests now, so it will become 5 projects in the future.

2 - This piscine has the same problems as the UX piscine as well so when you do the necessary changes you need to have in mind that:

  • The naming the files
  • The audit structure needs to be fixed
  • The questions in the audit must be YES/NO

So for this piscine you will need to:

  • Rename the quests in order for them to become projects
  • Join every exercise in each quest in order to create projects.
  • Join all the audits in the "Quest" that is now a project and create only one audit for the project.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.