stevenakp:


well, with mozilla MDN docs by my side I can do stuffs.

I just have a good understanding of how JavaScript works.

Afolabi6046:
that means you have prior knowlegde of HTML and CSS...i'm a java learner, so i don't find JS stress-free

stevenakp:


JS is not really difficult, you can make the switch.....but the way JS works is quite different from other languages.

but since you've done some programming before, you are good to go.
bro, make the switch fast. I thought I knew JavaScript not until I went to the bootcamp.

stevenakp:


JS is not really difficult, you can make the switch.....but the way JS works is quite different from other languages.

but since you've done some programming before, you are good to go.
bro, make the switch fast. I thought I knew JavaScript not until I went to the bootcamp.

Afolabi6046:
the JS test we have to take...what does it entail?

stevenakp:


it is just some challenges you will need to solve using JS.....they are not really advanced.

you could visit codewars.com

Afolabi6046:
Hello informed ones, from what i've seen while reading the thread, it seems python is the language used for the home study test. Is that right? or can we choose to take the test in JS instead?

Afolabi6046:
Hello informed ones, from what i've seen while reading the thread, it seems python is the language used for the home study test. Is that right? or can we choose to take the test in JS instead?

Afolabi6046:
thanks a lot man... you've been very resourceful

GoodBoi1:
If you want to have a feel of the kind of stuff you'll be doing at BootCamp, check this out http://s000.tinyupload.com/index.php?file_id=96624571953161514320

collinic:
I was invited twice last year to Andela interview, I went just once and couldn't scale through the interview. I never knew much about the interview until I got there and received a we are sorry to take you at this time mail from Andela.

It was painful because I came from Port Harcourt to Lagos and did not make it, but at the interview I discovered that Andela is more focused on Its EPIC (Excellence Passion Integrity and Collaboration) value than any other thing, at the interview your technical challenge is about 30%.

Again I discovered Andela lied to us, on its website when signing up, they made it clear that you don't need any previous coding experience which I think is a BIG lie because even if you scale through the interview, at the bootcamp it's more rigorous.

Scaling through the Andela bootcamp you need to understand Vanilla Javascrip, ReactJS, NodesJS, PostgresSQL, SequelizeJS and this technology is not for people that have not coded before.

For me, I think the truth is Andela need people with at least an understanding of programming so the second interview invitation I go, I didn't go because I was preparing for the bootcamp.

I have reapplied again this year and am waiting for the text. If you have Andela in mind as I do, then to be sincere you need to work your ass out and immerse yourself with learning before the time else this circle may not be your turn because thousands of youths are just as interested in Andela as you and believe me to some of them sleeping is a crime until they achieve it.

Most person come here to write but they have never received an invite from Andela, most of them can't even layout a website using CSS flexbox or CSS grid but the claim to be good. Please spend you time and prepare because if you read the Andela timetable by 9th of March people that will make it to the interview will be know.

Please don't take it to serious, I was bored and decided to write, the truth is Andela is becoming tougher because more people are becoming interested so you need to prove your awesomeness to be able to make it.

Thanks

Darey00:


PS: that being said, I'm seeing some Javascript Frameworks mentioned a lot here, does this mean that Andela uses the MEAN stack??

benedictuyi:
please wats the link to hook up wit andela

collinic:
I was invited twice last year to Andela interview, I went just once and couldn't scale through the interview. I never knew much about the interview until I got there and received a we are sorry to take you at this time mail from Andela.

It was painful because I came from Port Harcourt to Lagos and did not make it, but at the interview I discovered that Andela is more focused on Its EPIC (Excellence Passion Integrity and Collaboration) value than any other thing, at the interview your technical challenge is about 30%.

Again I discovered Andela lied to us, on its website when signing up, they made it clear that you don't need any previous coding experience which I think is a BIG lie because even if you scale through the interview, at the bootcamp it's more rigorous.

Scaling through the Andela bootcamp you need to understand Vanilla Javascrip, ReactJS, NodesJS, PostgresSQL, SequelizeJS and this technology is not for people that have not coded before.

For me, I think the truth is Andela need people with at least an understanding of programming so the second interview invitation I go, I didn't go because I was preparing for the bootcamp.

I have reapplied again this year and am waiting for the text. If you have Andela in mind as I do, then to be sincere you need to work your ass out and immerse yourself with learning before the time else this circle may not be your turn because thousands of youths are just as interested in Andela as you and believe me to some of them sleeping is a crime until they achieve it.

Most person come here to write but they have never received an invite from Andela, most of them can't even layout a website using CSS flexbox or CSS grid but the claim to be good. Please spend you time and prepare because if you read the Andela timetable by 9th of March people that will make it to the interview will be know.

Please don't take it to serious, I was bored and decided to write, the truth is Andela is becoming tougher because more people are becoming interested so you need to prove your awesomeness to be able to make it.

Thanks

UncleJJ:

Do you guys use Angular?

UncleJJ:

Do you guys use Angular?

SoftDev:

Gbam, pm me, I am in Port Harcourt let's prepare together, and Sequelize is very simple hahahaha

tippyboy:
Nobody should come to Andela bootcamp without having any idea about what the bootcamp is all about. As someone who has been to the bootcamp once, Here's something I wished someone had told me:

They are not going to teach you programming from scratch like most people thought. You own your own learning at Andela, you will be given some resources like three days before the bootcamp, and big project to work on within two weeks. You are encouraged to collaborate with your selves at the bootcamp . The project is very big and overwhelming (I will modify this comment and post the project very soon) and the first time I saw it I was like how the heck am supposed to finish this within two weeks, not knowing that I am supposed to focus more on the backend and leave the front end(react and co) for now. Bootcamp was fun, I met a lot different people, the funny ones, cool dudes, crazy niggaz, those that have finished all their routes, those that are still trying to wrap their head around the mvc concept, those that the longest line of code they've ever written in their life was:
console. log('Hello World!')...lol
I remember a guy once wrote in his bootcamp experience article: HA! WHO BROUGHT A KNIFE NTOO A GUNFIGHT BATTLE. lol!

tippyboy:
Bootcamp Cycle LOS/26 Project

Build A Product: More-Recipes


Contents

Overview    1

What You Need to Know Already                                                                                                          2

Build A Product    3

Challenge 1    3

Challenge 2    6

Challenge 3    8

Challenge 4    9


Requirements Checklist    10


Appendix    15

Project Assessment Guide    15   





OVERVIEW


What?

More-Recipes provides a platform for users to share the awesome and exciting  recipe ideas they have invented or learnt.  Suppose a user comes up with a food recipe,  he/she can post it on More-Recipes and  get feedback in form of reviews and votes from other users who explore that recipe. Users can also keep a list of their favorite recipes on the application.


How?

This project is broken down into challenges and completion of all phases would contribute greatly to your learning towards becoming a full-stack developer. Upon completion, you would have built a world-class full-stack JS application (front-end and back-end).


Why?

Andela distributes opportunities. We disseminate Learning and catalyse Technology leadership. The project is founded on the premise that aspiring Technology Leaders learn programming whilst building things that matter and that the best way to learn is by building a complete product.  

This project has one objective: create opportunities for learning where learners build products that do real stuff. In this way, we will inspire change in African tech landscape.

What You Need to Know Already


Html/CSS

http://github.andela.com/homestudy/modules/9

Javascript / ES6

https://www.codecademy.com/learn/learn-javascript

http://ccoenraets.github.io/es6-tutorial/

GIT and Version Control

https://vimeo.com/216470563

https://vimeo.com/221242881

https://try.github.io/


https://www.youtube.com/watch?v=73I5dRucCds



























BUILD A PRODUCT

Challenge 1 - Create Pivotal Tracker Board and HTML/CSS Templates

Timelines

Expected Length to Complete: 1 week

Due Date: 28th of August

Helpful Links & Tips

To get started with Pivotal Tracker, use Pivotal Tracker quick start.

Here is an sample template for creating Pivotal Tracker user stories.

Use the recommended Git Workflow, Git branch, Commit Message and Pull Request (PR) standards. Also adhere to the GitHub Flow guidelines to facilitate code reviews.

Guidelines

Create a Pivotal Tracker Board  

Use the Pivotal Tracker Board to create a roadmap for the following client-side and server-side features.
NB: you’re not implementing these yet, just create a roadmap. Remember to review the guidelines for how to go about creating your pivotal tracker board.


Templates for the following:

User registration/login pages.

A page that shows top recipes and allows viewers to search for recipes

A page that shows details of a recipe and allows logged in users to do the following:

Post reviews for a recipe

Upvote recipe

Downvote recipe

A page that shows the favorite recipes of a registered user

A page where a registered user can see his/her profile

A page where a registered user can do the following:

Add recipe

Modify the recipe he/she added

Delete the recipe he/she added


Basic API routes that do the following:

Allow users to create accounts and login to the application

Allow a logged in user to add a recipe

Allow a logged in user to modify a recipe he/she added

Allow a logged in user to delete a recipe he/she added

Allow a logged in user to get all recipes in the application

Allow a logged in user to get all his/her favorite recipes

Allow a logged in user to post a review for a recipe

Allow a logged in user to get just recipes with the most upvotes


Other features

On both the server-side and client-side, replace the implementation for authentication with JSON Web Tokens.

Registered user should get notifications (either in-app or email notification)

When his or her recipe gets a review

When a favorite recipe of his or hers gets modified

Registered users should be able to create categories for his/her favorite recipes

Registered users should be able to search for recipes in the application (implement pagination).


Extra Credits:
NB: executing one or more features from the extra credits means you have exceeded expectations.

Users should be able to see the number of times a recipe has been viewed.

Registered user should be able to find recipes based on a list of ingredients inputted



Create a Github Repository and clone it to your computer

Tip: find how to create a Github Repository here.

Create three directories in your local git repo

template - this will contain the UI template for the front-end in HTML/CSS

server -this will house your back-end implementation in NodeJS-Express

client - this will house your front-end implementation in ReactJS and Redux

Build out the below specified templates into the template directory

In the template directory, build out all the pages (with HTML, CSS, JS, and any other CSS framework (N.B You are to use either Bootstrap 4 or Materialize CSS framework. Do not download and use any UI template!!! )) and the necessary UI elements that will allow your application perform the following functions:


User registration/login to the application.

This would contain a basic form that allows people create accounts and login to the system.

The submit button is not expected to be functional here.

A page that shows top recipes and allows viewers to search for recipes

A page that shows details of a recipe and allows logged in users to do the following:

Post reviews for a recipe

Upvote recipe

Downvote recipe

A page that shows the favorite recipes of a registered user

A page where a registered user can see his/her profile

A page where a registered user can do the following:

Add recipe

Modify the recipe he/she added  

Delete the recipe he/she added


NB: you’re not implementing the core functionality yet, you’re only working on the User Interface!

NB:  you are to create a pull request for the templates when you are done working on them locally

Targeted Skills

After completing this challenge, you should have learnt and be able to demonstrate the following skills:


Agile

Use a project management tool (Pivotal Tracker) to manage your progress on the tasks


Github

Create a GitHub repository and clone it locally.


Use Git Workflow, Git branch, Commit Message and Pull Request (PR) standards.

Also adhere to the GitHub Flow guidelines to facilitate code reviews.

HTML/CSS

Create all the templates specified above


Frontend Design
- Material Design Frameworks

- Bootstrap 4

Use a Material Design Framework (Material UI or Materialize CSS recommended) and read through Google design spec for your reference or Bootstrap 4.  


You are not to download and use any website template. You are to code the HTML, and apply your own CSS and any necessary stylesheets or CSS classes provided by the UI framework of your choice( fe.g Bootstrap 4 or MaterializeCSS).



Challenge 2: Setup Server-Side and Create API Endpoints

Timelines

Expected Length to Complete: 1 week

Due Date: 31st of August

Helpful Links & Tips

Use the recommended Git Workflow, Git branch, Commit Message and Pull Request (PR) standards. Also adhere to the GitHub Flow guidelines to facilitate code reviews.

All Javascript MUST be written in >=ES6 and should use Babel to transpile down to ES5

Classes/modules MUST respect the SRP (Single Responsibility Principle) and MUST use the >=ES6 methods of module imports and exports.

Adhere strictly to the Airbnb style guide for ES6.
NB: A good place to start would be ensuring that eslint has been setup and is working!

You can use this link as a guide to using Sequelize ORM.

Install PostgreSQL to your local computer and connect to PostgreSQL database server from a client application such as psql or pgAdmin.

Before you begin this section, ensure to review this materials

Guide to Restful API design

Best Practices for a pragmatic RESTful API



Guidelines

In the server directory:

Setup the back-end (server side) of the application
Ensure that you use NodeJS - Express to do this.

Setup eslint for linting
Ensure you have the style guide rules configured properly.

Write the server-side code to power the front-end built in challenge 1.

Use Postgresql for relational data persistence and Sequelize as your ORM.

At minimum, you should have the following API routes working:

API routes for users to create accounts and login to the application:

   POST: /api/users/signup

   POST: /api/users/signin

An API route that allows logged in user to add a recipe:

   POST: /api/recipes

An API route that allows logged in user to modify a recipe that he/she added
    PUT: /api/recipes/<recipeId>

An API route that allows logged in user to delete a recipe that he/she added
    DELETE: /api/recipes/<recipeId>

An API route that allows logged in user to gets all the recipes in the application
    GET: /api/recipes

An API route that allows logged in user to post a review for a recipe
    POST: /api/recipes/<recipeId>/reviews

An API route that allows a logged in user to get all his/her favorite recipes

                 GET: /api/users/<userId>/recipes

An API route that allows a logged in user to get just recipes with the most upvotes

    GET: /api/recipes?sort=upvotes&order=ascending


Ensure to test all routes and see that they work using Postman.

Write tests for all functions, models, middleware and API routes using Mocha or Jasmine.

Integrate TravisCI for Continuous Integration in your repository (with ReadMe badge).

Integrate test coverage reporting (e.g. Coveralls) with badge in the ReadMe.

Obtain CI badges from Code Climate and Coveralls. These should be in the ReadMe.

Integrate HoundCI for style checking commits in your PRs according to the ESLint configuration.

Deploy your server-side application on Heroku.

Use API Blueprint, slate or swagger to document your API. Docs should be via your application’s URL.

Version your API using url versioning starting, with the letter “v”. A simple ordinal number would be appropriate and avoid dot notation such as 2.5.
Sample - https://somewebapp.com/api/v1/users


NB:  you are to create a pull request for the api routes when you are done working on them locally


Targeted Skills

After completing this challenge, you should have learnt and be able to demonstrate the following skills:


ES6 + Babel

All Javascript MUST be written in ES6 or higher and should use Babel to transpile down to ES5

OOP + SRP

Classes/modules MUST respect the SRP (Single Responsibility Principle) and MUST use the >=ES6 methods of module imports and exports.


.eslint
- Airbnb style guides

Use a .eslint in your root directory of your project as your eslint configuration (in your IDE) to expose Javascript syntax errors / nitpicks. Make sure to extend the airbnb styleguide.

Continuous Integration

Integrate HoundCI for style checking commits in your PRs


Integrate a CI tool(e.g. TravisCI) to also run tests and report pass/fail state with badge in readme and also test coverage reporting(e.g. coveralls)with badge in the readme.


Obtain CI badges from Code Climate and Coveralls. p.s this should be in the readme


NodeJS

You were required to create a server directory in your repository and project directory in challenge 1. The“server” directory would contain the server-side implementation you come up with in this challenge required to power the front-end.


Setup the back-end (server side) of the application with NodeJS - Express.

Databases

Implement data persistence using Postgresql with Sequelize ORM


Build API

Download and install the Google Chrome app Postman. This would be used to test the API you are building.



Challenge 3: Implement Front-end using React and Redux

Timelines

Expected Length to Complete:

Due Date:

Helpful Links & Tips

Use the recommended Git Workflow, Git branch, Commit Message and Pull Request (PR) standards. Also adhere to the GitHub Flow guidelines to facilitate code reviews.

All Javascript MUST be written in >=ES6 and should use Babel to transpile down to ES5

Classes/modules MUST respect the SRP (Single Responsibility Principle) and MUST use the >=ES6 methods of module imports and exports.

Adhere to the Airbnb style guide for ES6. A good place to start would be ensuring that eslint has been setup and is working

Use SASS/SCSS to implement all custom styling.

Guidelines

In your client directory, setup your front-end application (ReactJS-Redux).

Ensure Webpack is setup for running mundane tasks
NB: At minimum, configure it to convert SCSS  => CSS) and transpiling.

Implement the client-side application in React and Redux

This should contain all the features pre-designed in challenge 1.

The implementation should make use of the APIs built in challenge 2.

Write tests for all actions, reducers and components using Enzyme, Jest or any relevant testing utility.

Write End-to-End tests for all features implemented using Protractor, Nightwatch or any Selenium-based libraries.

Ensure your front-end is also hosted on Heroku.


NB:  you are to create a pull request  when you are done with this challenge



Targeted Skills

After completing this challenge, you should have learnt and be able to demonstrate the following skills:

.eslint
- Airbnb style guides

Use a .eslint in your root directory of your project as your eslint configuration (in your IDE) to expose Javascript syntax errors / nitpicks. Make sure to extend the airbnb style guide.

Continuous Integration

Integrate HoundCI for style checking commits in your PRs


Integrate a CI tool(e.g. TravisCI) to also run tests and report pass/fail state with badge in readme and also test coverage reporting(e.g. coveralls)with badge in the readme.


Obtain CI badges from Code Climate and Coveralls. p.s this should be in the readme



Github

Use Git Workflow, Git branch, Commit Message and Pull Request (PR) standards.

Also adhere to the GitHub Flow guidelines to facilitate code reviews.

HTML/CSS

Use SASS/SCSS to implement all custom styling


ES6 + Babel

All Javascript MUST be written in >=ES6 and should use Babel to transpile down to ES5

OOP + SRP

Classes/modules MUST respect the SRP (Single Responsibility Principle) and MUST use the >=ES6 methods of module imports and exports.


Testing

Install libraries required for component/unit tests eg Mocha, Jasmine,, Enzyme, Jest


Install libraries required for integration/e2e tests eg Protractor or other Selenium based libraries

Agile

Use a project management tool (Pivotal Tracker) to manage your progress on the tasks


ReactJS

- Redux

- Webpack

- Task-runners

Use ReactJS with the Redux architecture for your implementation


Install and configure Webpack to run mundane tasks like convert SCSS  -> CSS, run your tests(Integration and unit).


A task runner should be setup to handle the various tasks that the application requires which include serving the app, and testing the app






















Challenge 4: Implement other Features listed in Pivotal Tracker

Timelines

Expected Length to Complete:

Due Date:

Helpful Links & Tips

Use the recommended Git Workflow, Git branch, Commit Message and Pull Request (PR) standards. Also adhere to the GitHub Flow guidelines to facilitate code reviews.

All Javascript MUST be written in >=ES6 and should use Babel to transpile down to ES5

Classes/modules MUST respect the SRP (Single Responsibility Principle) and MUST use the >=ES6 methods of module imports and exports.

Adhere to the Airbnb style guide for ES6. A good place to start would be ensuring that eslint has been setup and is working

Guidelines

Maintaining all standards set in all previous challenges (tests, API documentation etc.), implement the other features (server-side and client-side) in the roadmap defined in Pivotal Tracker.

Ensure your  full-stack application is hosted on Heroku.


NB:  you are to create a pull request  when you are done with this challenge


Targeted Skills

After completing this challenge, you should have learnt and be able to demonstrate the following skills:


Github

Use Git Workflow, Git branch, Commit Message and Pull Request (PR) standards.

Also adhere to the GitHub Flow guidelines to facilitate code reviews.

HTML/CSS

Use SASS/SCSS to implement all custom styling


ES6 + Babel

All Javascript MUST be written in >=ES6 and should use Babel to transpile down to ES5

OOP + SRP

Classes/modules MUST respect the SRP (Single Responsibility Principle) and MUST use the >=ES6 methods of module imports and exports.


Testing

Install libraries required for component/unit tests eg Mocha, Jasmine,, Enzyme, Jest


Install libraries required for integration/e2e tests eg Protractor or other Selenium based libraries

Agile

Use a project management tool (Pivotal Tracker) to manage your progress on the tasks


ReactJS

- Redux

- Webpack

- Task-runners

Use ReactJS with the Redux architecture for your implementation


Install and configure Webpack to run mundane tasks like convert SCSS  -> CSS, run your tests(Integration and unit).


A task runner should be setup to handle the various tasks that the application requires which include serving the app, and testing the app
















APPENDIX



Project Assessment Guide


Criterion

Does not Meet Expectation

Meets Expectations

Exceed Expectations

Code Functionality

The code does not work in accordance with the ideas in the problem definition.

The code meets all the requirements listed in the problem definition.

The code handles more cases than specified in the problem definition.

Comments

Solution is not commented.

Solution contains adequate comments.

Solution uses doc style comments and is self documenting.

Code Readability

Code is not easily readable or is not commented.


The names for variables, classes, and procedures are inconsistent and/or not meaningful.


Negligence of style guides.

Code is easily readable and necessarily commented.


The names for variables, classes, and procedures are consistent and/or meaningful.


Style Guides are adhered to.


OOP Usage

Solution did not use OOP or does not use OOP properly by not modelling required objects as required.

Solution made use of OOP according to the requirement of the assignment and does so in the appropriate fashion.


Test Coverage

Solution did not attempt to use TDD

70% test coverage

100% test coverage or 0% test coverage like a Bawse.

Load time optimization (client side only)

Did not bundle JS files and has multiple script includes in index.html(or whatever entry point is)

Bundled all files and has just one include declaration for both JS and CSS

Minifies bundle(s) and has sourcemaps available

UI/UX

Page is non responsive, elements are not proportional, color scheme is not complementary and uses alerts to display user feedback

Page is responsive (at least across mobile, tablet and desktops), color scheme is complementary, and uses properly designed dialog boxes to give user feedback