Work in pairs: Miyesier & Pia
Testing with Jest, Enzyme (unit testing) and Cypress (equivilent of cucumber).
Do the whole thing in React, add styling iwth SemanticUI for React. Use it like a kitchensink for experimenting with React. Will do it monday and tuesday.
When done and re-read the coursematerial and reflected over it - add as much as possible to this application.
BDD & TDD in React, interacting with the back-end.
We're gonna build our own API - read the course-material properly!
Need to understand how a client talks to the backend.
- More advanved usage of stateful/stateless componens
- Interaction with API's - getting data - writing data
- Manage state - intro to Redux
Testing: acceptance test - is the app doing what we want. Component test - are each indivdual ocmponeten doing what we want?
Acceptance unit test cycle.
Shortcuts: imp - import moduleNAme from module imn est cdm
GITPONGING: One pers does their repo and writes the code, push that to their own repo. Other person creates a new repo, clones that down, then add the other person as a remote, pull down the code from other pers, add as collaborator.
get a lower version of node! Maybe do yarn install nvm, then install a lower Node version. We need to use 11.10.1 version of Node. nvm use 11.10.1
Need to: display results, saved button, find past results, associate data to a user, bmi-converter.
Back-end in Rails Front-end/Client in React.
Read through documentation carefully!
Think about MVC pattern! Model - view - controller This week the Client will be the view the API will be the model and the controller part.
We're adding user class, user registration Adds performance data model - where we save the result from the user to the back-end.
Spend a lot of time understanding the API part!
AUT-cycle way: So start of with testing!
Don't fork each others repos: Pers1 creates application, commits it, creates a repository on Github, push it up. Pers2 can Clone down the same repository to their computer, creates their own repository on Github, pushes it there. No need to add collaborations!
Change is the only constant.
-
It is impossible to gather all the requirements at the beginning of a project
-
Whatever requirements you do gather - are guaranteed to change.
-
There will always be more to do than time and money will allow.
Accepting the first truth means you're not afraid to begin your journey without knowing everything up front.
Accepting the second truth means you no longer fear or avoid change - you know it's coming.
By accepting the third truth, you no longer get stressed when your todo list exceeds your time and resources to deliver.
The I want to do more feeling - time is a resource we cannot make more of. If we want to do more we can a) surround ourselves with people who share our values in how we work and what we work with. b) work in the smartest way - good tools (helpfull extensions, frameworks, libraries), automated test. c) scope your features in small managable chunks. Finish off the tiny pieces one by one.