Really enjoyed working with my partner on the Javascript TV remote task, would have had it working sooner, if not for the typo's that the testing uncovered. Looking at refactoring the code together and how we can improve the solution further, tomorrow.
Thanks again to the TR team for the book and the delicious sweets
Andy managed to get the user login and social login to work in frontend and Claudina got our MongoDb setup on the backend using Heroku. I started to create food items in the backend and test my functionality with Item View and Listing Pages.
Worked on the Login and Register page, making changes to support state changes.
Started reading about and trying the tutorials on using Google Firebase for the authentication, to retrieve the JWT token and storing it in Firebase, with the returned user UID to be stored in MongoDB. Andy had spent time working on this while I worked on the Item Listing, Item view pages.
Over the weekend I read the "Food App Reduction" spec and created a mind map of it to use on Monday with the team to refine our understanding, ideas and thoughts about the creating a solution.
On Monday morning, the mind map on Miro proved useful in making sure everyone understood the specification for the "Food App Reduction" app, differing points could be discussed and corrections/additions could be made real-time with everyone involved.
We also discussed each others skillsets, ideas on which frontend/ backend technology to use. We discussed which scrum tools to use (decided on Trello), and general admin of hours people could work and when we should get together for our daily standups (9:30am)
Based on the refined mind map specification, we started to build the wireframe in Miro too. The team began to enjoy designing screen layouts, input text fields and buttons.
Ideas flowed about extending the brief, which were marked most down as advance features that we'd like to implement, if we got time.
Really enjoyed the exciting work being done at Blackrock and the scope of development for people to make a real difference. Impressed with the work culture and ethos at the company and their commitment to improving the environment.
Resolved the Java issue on my partners computer, seems she has a different compiler setting than I have, but we managed to refactor the code and make it work, so happy days!
Copied and pasted the code into her copy of the git repository and she uploaded the code successfully.
Used Tuesday to organise ourselves for our first Sprint Review, organising each members discussion points, things about the design we should complete.
Continuing our great week of collaborating as a team, getting to grips differences between Material UI Kit and Bootstrap, researching both the pros and cons of each. Had team discussion with our findings and decided on Material UI, based on it having a low-memory footprint.
Started in earnest on Wednesday to convert the design pages from our wireframe into html.
Lots of learning about how Material UI works and its different components and how we could incorporate that into our designs.
Rest of the week spent working on our html pages, using scrum meetings to highlight issues and concerns and how collectively we could solve problems
Over the weekend, had a look at the capabilities of Xmind vs Miro, and noticed Xmind was not as rich in terms of templates as Miro, nor as interactive when team members are designing or planning an idea all at the same time. Decided to use Miro and create a mind map of the spec ready for Monday morning's team meeting with something concrete to discuss to generate ideas and form a base for the way forward.
Had a group discussion on what backend to use, we decided to go with NodeJS using express and MongoDB with a mongoose frontend for the data validation. Others in the team seemed to have used these mongoose and Express before, so I took time to read up and learn about them
Great start today going over Java and Java OO concepts followed by a pair programming exercise in the afternoon using java abstract classes and interfaces.
Since my partner had never programmed in Java, I needed to be patient and help her come on board my letting her program while I conceptualised the way to implement the solution. That led us to use git in a more collaborative way, where her repository was the origin and mine became the remote, so I could make little changes and test things when things weren't compiling!, especially when the tests ran on my computer but not on hers!. That maybe a Java installation issue on my part or hers, will investigate later.
Refactored the Database DB schema on the backend to avoid confusion of field names and field functionality behaviour between each other's definition of a food item and user as used on our React pages.
Added a Map to show where users items are for collection.
Spent time learning about Triggers and testing ability on scheduling them on the back end to remove a user expired items
Got the Terms and Conditions functionality to work, so Register button only showed if the check box was clicked.
Merged in code from others and resolved merging errors in development
Started building reuseable React components, such as checkboxes and pagination for the rest of the team and started adding these to some of the Pages, such as Register Page.
From our working HTML pages, we created React version of the ItemList, ItemView and Register pages, reading up on latest React trends and design approach.
Researched Geo-location functionality using Google Maps and Places API to pull the geo-location from postcodes. Started to researched displaying the items on a Map.
Really enjoyed working with my partner on the Javascript TV remote task, would have had it working sooner, if not for the typo's that the testing uncovered. Looking at refactoring the code together and how we can improve the solution further, tomorrow.
Thanks again to the TR team for the book and the delicious sweets
Andy managed to get the user login and social login to work in frontend and Claudina got our MongoDb setup on the backend using Heroku. I started to create food items in the backend and test my functionality with Item View and Listing Pages.
Worked on the Login and Register page, making changes to support state changes.
Started reading about and trying the tutorials on using Google Firebase for the authentication, to retrieve the JWT token and storing it in Firebase, with the returned user UID to be stored in MongoDB. Andy had spent time working on this while I worked on the Item Listing, Item view pages.
Over the weekend I read the "Food App Reduction" spec and created a mind map of it to use on Monday with the team to refine our understanding, ideas and thoughts about the creating a solution.
On Monday morning, the mind map on Miro proved useful in making sure everyone understood the specification for the "Food App Reduction" app, differing points could be discussed and corrections/additions could be made real-time with everyone involved.
We also discussed each others skillsets, ideas on which frontend/ backend technology to use. We discussed which scrum tools to use (decided on Trello), and general admin of hours people could work and when we should get together for our daily standups (9:30am)
Based on the refined mind map specification, we started to build the wireframe in Miro too. The team began to enjoy designing screen layouts, input text fields and buttons.
Ideas flowed about extending the brief, which were marked most down as advance features that we'd like to implement, if we got time.
Really enjoyed the exciting work being done at Blackrock and the scope of development for people to make a real difference. Impressed with the work culture and ethos at the company and their commitment to improving the environment.
Resolved the Java issue on my partners computer, seems she has a different compiler setting than I have, but we managed to refactor the code and make it work, so happy days!
Copied and pasted the code into her copy of the git repository and she uploaded the code successfully.
Used Tuesday to organise ourselves for our first Sprint Review, organising each members discussion points, things about the design we should complete.
Continuing our great week of collaborating as a team, getting to grips differences between Material UI Kit and Bootstrap, researching both the pros and cons of each. Had team discussion with our findings and decided on Material UI, based on it having a low-memory footprint.
Started in earnest on Wednesday to convert the design pages from our wireframe into html.
Lots of learning about how Material UI works and its different components and how we could incorporate that into our designs.
Rest of the week spent working on our html pages, using scrum meetings to highlight issues and concerns and how collectively we could solve problems
Over the weekend, had a look at the capabilities of Xmind vs Miro, and noticed Xmind was not as rich in terms of templates as Miro, nor as interactive when team members are designing or planning an idea all at the same time. Decided to use Miro and create a mind map of the spec ready for Monday morning's team meeting with something concrete to discuss to generate ideas and form a base for the way forward.
Had a group discussion on what backend to use, we decided to go with NodeJS using express and MongoDB with a mongoose frontend for the data validation. Others in the team seemed to have used these mongoose and Express before, so I took time to read up and learn about them
Great start today going over Java and Java OO concepts followed by a pair programming exercise in the afternoon using java abstract classes and interfaces.
Since my partner had never programmed in Java, I needed to be patient and help her come on board my letting her program while I conceptualised the way to implement the solution. That led us to use git in a more collaborative way, where her repository was the origin and mine became the remote, so I could make little changes and test things when things weren't compiling!, especially when the tests ran on my computer but not on hers!. That maybe a Java installation issue on my part or hers, will investigate later.
Started to use stricter Eslint to validation on our code.
Refactored the Database DB schema on the backend to avoid confusion of field names and field functionality behaviour between each other's definition of a food item and user as used on our React pages.
Started designing workflow and linking between pages to view items and pass user information to correctly look at my items or searched items.
Implemented Redux to manage state and props with actions to delete and sort items
Started working with Redux and used the centralised state management tool to pull item and user data into props.
Introduced Moment.js to manage the date handling within the application especially expiry date and item collection pickup dates
Got event handling to work on sorting by expiry date and category on the Listing View page
Refactored a lot the code and got event handling to work.
Added a Map to show where users items are for collection.
Spent time learning about Triggers and testing ability on scheduling them on the back end to remove a user expired items
Got the Terms and Conditions functionality to work, so Register button only showed if the check box was clicked.
Merged in code from others and resolved merging errors in development
Created the Item View Page and ensured it was fully data driven and working
Introduced a test data file to test my react pages with actual food items and shared with the rest of the team, for there development work.
Started to work on the Listing Page, adding customised Tabs, Pagination, Sorting and Add item buttons.
Started building reuseable React components, such as checkboxes and pagination for the rest of the team and started adding these to some of the Pages, such as Register Page.
We added State to our React pages, and made sure we could see changes to the pages whenever text field and layout component were being amended.
From our working HTML pages, we created React version of the ItemList, ItemView and Register pages, reading up on latest React trends and design approach.
Added Callbacks and React Hooks implemented on my Register, Listing and Item View pages.
Added to amendable 'first line of address' field to the pages and made them visible on the Listings and View Item Pages
Improved the Location Pin size and colour on the Maps
Tidied up and refactored code and resolved merge conflicts in the development branch.
Added ability to search for items and display their details and fix reserve and unreserve items broken functionality
Added functionality to remove a users' expired items from MongoDB
Researched Geo-location functionality using Google Maps and Places API to pull the geo-location from postcodes. Started to researched displaying the items on a Map.
Refactored pages to support new fields added by others.
Added functionality on the Front and Back end to support deleting, reserving and unreserving items.
Implemented redux containers and reducers on all our pages