Giter Club home page Giter Club logo

capstone-7.2-team2's Introduction

About Me

I am a passionate and extroverted Software Developer with dreams to start my own AR company. I am an absolute geek about the future of tech, specifically: Augmented Reality, AI, blockchain, and automated technologies like self-driving cars.

I am strengthening my coding skills through a year long intensive Fellowship at Pursuit, a NYC-based web development fellowship with a 9% acceptance rate. When I'm not reading about the tech industry, you'll find me traveling the world, reading anything I can get my hands on, or talking to strangers in an attempt to satisfy my endless curiosity about what makes the world tick.

Add me on LinkedIn!

https://www.linkedin.com/in/obaid-rustemi-0314a355/

capstone-7.2-team2's People

Contributors

bedonjonathan avatar carlo-e avatar floweraviles avatar kenia-r avatar obaidrustemi avatar

Stargazers

 avatar

Watchers

 avatar

capstone-7.2-team2's Issues

Proposal Review

DB Issues

  1. It seems we are missing a lot of columns here. I'm literally only seeing artwork but from reading your user stories it seems you should have a few more tables, particularly users, galleries, gallery_contacts, artist_contacts, etc.
  2. Your users will likely need a way to differentiate between their differentiate between their roles. For example, you may want to have booleans like is_artist or is_gallery_owner to signify whether or not they are an artist, a gallery owner, or both.
  3. On your artworks model (remember the convention is that this should be plural), I see you are adding columns for the artist information. Remember we shouldn't be doing this. An artwork instance should simply have an artist_id which points to an instance of users that will contain all that information (name, etc.). Also, once we do that we can also probably eliminate artwork_* in the naming of the columns.
  4. Overall, I feel like your database hasn't bee fully fleshed out yet. I want to take the time here to emphasize the CRIITICAL IMPORTANCE of having a well designed and thought out database, and hope you halt work on what you've started thus far and really put some effort into planning this part of your project.

Backend Routes Issues

  1. Theres a lot of columns that don't currently exist that I think we can agree probably should at this point, so clearly we should revisit this...
  2. Artwork has a delete route. Unless we are going to add a user story for someone being able to purchase a piece of art from the artist, this is probably not necessary.

Frontend Routes Issues

  1. Again a lot missing here so this is not very helpful to you yet. I would highly suggest putting some time into crafting these once you have a working model for your database and backend.
  2. Why is there a route for POST /artwork/:id ? Certainly this shouldn't exist right?
  3. Also, lets discuss why we should or would want to delete artwork....

Timeline Issues

  • Timeline seems reasonably planned out. Good job!

Wireframes
-Looks good! Excited to see the finished product.

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.