# LIRI Bot ### Overview In this assignment, you will make LIRI. LIRI is like iPhone's SIRI. However, while SIRI is a Speech Interpretation and Recognition Interface, LIRI is a _Language_ Interpretation and Recognition Interface. LIRI will be a command line node app that takes in parameters and gives you back data. ### Before You Begin 1. LIRI will search Spotify for songs, Bands in Town for concerts, and OMDB for movies. 2. Make a new GitHub repository called liri-node-app and clone it to your computer. 3. To retrieve the data that will power this app, you'll need to send requests to the Bands in Town, Spotify and OMDB APIs. You'll find these Node packages crucial for your assignment. * [Node-Spotify-API](https://www.npmjs.com/package/node-spotify-api) * [Request](https://www.npmjs.com/package/request) * You'll use Request to grab data from the [OMDB API](http://www.omdbapi.com) and the [Bands In Town API](http://www.artists.bandsintown.com/bandsintown-api) * [Moment](https://www.npmjs.com/package/moment) * [DotEnv](https://www.npmjs.com/package/dotenv) ## Submission Guide Make sure you use the normal GitHub. Because this is a CLI App, there will be no need to deploy it to Heroku. This time, though, you need to include screenshots, a gif, and/or a video showing us that you got the app working with no bugs. You can include these screenshots or a link to a video in a `README.md` file. * Include screenshots (or a video) of typical user flows through your application (for the customer and if relevant the manager/supervisor). This includes views of the prompts and the responses after their selection (for the different selection options). * Include any other screenshots you deem necessary to help someone who has never been introduced to your application understand the purpose and function of it. This is how you will communicate to potential employers/other developers in the future what you built and why, and to show how it works. * Because screenshots (and well-written READMEs) are extremely important in the context of GitHub, this will be part of the grading. If you haven't written a markdown file yet, [click here for a rundown](https://guides.github.com/features/mastering-markdown/), or just take a look at the raw file of these instructions. ### Submission on BCS * Please submit the link to the Github Repository! ### Instructions 1. Navigate to the root of your project and run `npm init -y` &mdash; this will initialize a `package.json` file for your project. The `package.json` file is required for installing third party npm packages and saving their version numbers. If you fail to initialize a `package.json` file, it will be troublesome, and at times almost impossible for anyone else to run your code after cloning your project. 2. Make a `.gitignore` file and add the following lines to it. This will tell git not to track these files, and thus they won't be committed to Github. ``` node_modules .DS_Store .env ``` 3. Make a JavaScript file named `keys.js`. * Inside keys.js your file will look like this: ```js console.log('this is loaded'); exports.spotify = { id: process.env.SPOTIFY_ID, secret: process.env.SPOTIFY_SECRET }; ``` 4. Next, create a file named `.env`, add the following to it, replacing the values with your API keys (no quotes) once you have them: ```js # Spotify API keys SPOTIFY_ID=your-spotify-id SPOTIFY_SECRET=your-spotify-secret ``` * This file will be used by the `dotenv` package to set what are known as environment variables to the global `process.env` object in node. These are values that are meant to be specific to the computer that node is running on, and since we are gitignoring this file, they won't be pushed to github &mdash; keeping our API key information private. * If someone wanted to clone your app from github and run it themselves, they would need to supply their own `.env` file for it to work. 5. Make a file called `random.txt`. * Inside of `random.txt` put the following in with no extra characters or white space: * spotify-this-song,"I Want it That Way" 6. Make a JavaScript file named `liri.js`. 7. At the top of the `liri.js` file, add code to read and set any environment variables with the dotenv package: ```js require("dotenv").config(); ``` 8. Add the code required to import the `keys.js` file and store it in a variable. * You should then be able to access your keys information like so ```js var spotify = new Spotify(keys.spotify); ``` 9. Make it so liri.js can take in one of the following commands: * `concert-this` * `spotify-this-song` * `movie-this` * `do-what-it-says` ### What Each Command Should Do 1. `node liri.js concert-this <artist/band name here>` * This will search the Bands in Town Artist Events API (`"https://rest.bandsintown.com/artists/" + artist + "/events?app_id=codingbootcamp"`) for an artist and render the following information about each event to the terminal: * Name of the venue * Venue location * Date of the Event (use moment to format this as "MM/DD/YYYY") 2. `node liri.js spotify-this-song '<song name here>'` * This will show the following information about the song in your terminal/bash window * Artist(s) * The song's name * A preview link of the song from Spotify * The album that the song is from * If no song is provided then your program will default to "The Sign" by Ace of Base. * You will utilize the [node-spotify-api](https://www.npmjs.com/package/node-spotify-api) package in order to retrieve song information from the Spotify API. * The Spotify API requires you sign up as a developer to generate the necessary credentials. You can follow these steps in order to generate a **client id** and **client secret**: * Step One: Visit <https://developer.spotify.com/my-applications/#!/> * Step Two: Either login to your existing Spotify account or create a new one (a free account is fine) and log in. * Step Three: Once logged in, navigate to <https://developer.spotify.com/my-applications/#!/applications/create> to register a new application to be used with the Spotify API. You can fill in whatever you'd like for these fields. When finished, click the "complete" button. * Step Four: On the next screen, scroll down to where you see your client id and client secret. Copy these values down somewhere, you'll need them to use the Spotify API and the [node-spotify-api package](https://www.npmjs.com/package/node-spotify-api). 3. `node liri.js movie-this '<movie name here>'` * This will output the following information to your terminal/bash window: ``` * Title of the movie. * Year the movie came out. * IMDB Rating of the movie. * Rotten Tomatoes Rating of the movie. * Country where the movie was produced. * Language of the movie. * Plot of the movie. * Actors in the movie. ``` * If the user doesn't type a movie in, the program will output data for the movie 'Mr. Nobody.' * If you haven't watched "Mr. Nobody," then you should: <http://www.imdb.com/title/tt0485947/> * It's on Netflix! * You'll use the request package to retrieve data from the OMDB API. Like all of the in-class activities, the OMDB API requires an API key. You may use `trilogy`. 4. `node liri.js do-what-it-says` * Using the `fs` Node package, LIRI will take the text inside of random.txt and then use it to call one of LIRI's commands. * It should run `spotify-this-song` for "I Want it That Way," as follows the text in `random.txt`. * Edit the text in random.txt to test out the feature for movie-this and concert-this. ### BONUS * In addition to logging the data to your terminal/bash window, output the data to a .txt file called `log.txt`. * Make sure you append each command you run to the `log.txt` file. * Do not overwrite your file each time you run a command. ### Reminder: Submission on BCS * Please submit the link to the Github Repository! - - - ### Minimum Requirements Attempt to complete homework assignment as described in instructions. If unable to complete certain portions, please pseudocode these portions to describe what remains to be completed. Adding a README.md as well as adding this homework to your portfolio are required as well and more information can be found below. - - - ### Create a README.md Add a `README.md` to your repository describing the project. Here are some resources for creating your `README.md`. Here are some resources to help you along the way: * [About READMEs](https://help.github.com/articles/about-readmes/) * [Mastering Markdown](https://guides.github.com/features/mastering-markdown/) - - - ### Add To Your Portfolio After completing the homework please add the piece to your portfolio. Make sure to add a link to your updated portfolio in the comments section of your homework so the TAs can easily ensure you completed this step when they are grading the assignment. To receive an 'A' on any assignment, you must link to it from your portfolio. - - - ### One More Thing If you have any questions about this project or the material we have covered, please post them in the community channels in slack so that your fellow developers can help you! If you're still having trouble, you can come to office hours for assistance from your instructor and TAs. **Good Luck!**

Portfolio website for Kristine Baffo, Project Manager and Rutgers Alumni. - http://kristinebaffo.github.io |

Overview In this assignment, you will make LIRI. LIRI is like iPhone's SIRI. However, while SIRI is a Speech Interpretation and Recognition Interface, LIRI is a Language Interpretation and Recognition Interface. LIRI will be a command line node app that takes in parameters and gives you back data. Before You Begin LIRI will search Spotify for songs, Bands in Town for concerts, and OMDB for movies. Make a new GitHub repository called liri-node-app and clone it to your computer. To retrieve the data that will power this app, you'll need to send requests to the Bands in Town, Spotify and OMDB APIs. You'll find these Node packages crucial for your assignment. Node-Spotify-API Request You'll use Request to grab data from the OMDB API and the Bands In Town API Moment DotEnv Submission Guide Make sure you use the normal GitHub. Because this is a CLI App, there will be no need to deploy it to Heroku. This time, though, you need to include screenshots, a gif, and/or a video showing us that you got the app working with no bugs. You can include these screenshots or a link to a video in a README.md file. Include screenshots (or a video) of typical user flows through your application (for the customer and if relevant the manager/supervisor). This includes views of the prompts and the responses after their selection (for the different selection options). Include any other screenshots you deem necessary to help someone who has never been introduced to your application understand the purpose and function of it. This is how you will communicate to potential employers/other developers in the future what you built and why, and to show how it works. Because screenshots (and well-written READMEs) are extremely important in the context of GitHub, this will be part of the grading. If you haven't written a markdown file yet, click here for a rundown, or just take a look at the raw file of these instructions. Submission on BCS Please submit the link to the Github Repository! Instructions Navigate to the root of your project and run npm init -y — this will initialize a package.json file for your project. The package.json file is required for installing third party npm packages and saving their version numbers. If you fail to initialize a package.json file, it will be troublesome, and at times almost impossible for anyone else to run your code after cloning your project. Make a .gitignore file and add the following lines to it. This will tell git not to track these files, and thus they won't be committed to Github. node_modules .DS_Store .env Make a JavaScript file named keys.js. Inside keys.js your file will look like this: console.log('this is loaded'); exports.spotify = { id: process.env.SPOTIFY_ID, secret: process.env.SPOTIFY_SECRET }; Next, create a file named .env, add the following to it, replacing the values with your API keys (no quotes) once you have them: # Spotify API keys SPOTIFY_ID=your-spotify-id SPOTIFY_SECRET=your-spotify-secret This file will be used by the dotenv package to set what are known as environment variables to the global process.env object in node. These are values that are meant to be specific to the computer that node is running on, and since we are gitignoring this file, they won't be pushed to github — keeping our API key information private. If someone wanted to clone your app from github and run it themselves, they would need to supply their own .env file for it to work. Make a file called random.txt. Inside of random.txt put the following in with no extra characters or white space: spotify-this-song,"I Want it That Way" Make a JavaScript file named liri.js. At the top of the liri.js file, add code to read and set any environment variables with the dotenv package: require("dotenv").config(); Add the code required to import the keys.js file and store it in a variable. You should then be able to access your keys information like so var spotify = new Spotify(keys.spotify); Make it so liri.js can take in one of the following commands: concert-this spotify-this-song movie-this do-what-it-says What Each Command Should Do node liri.js concert-this <artist/band name here> This will search the Bands in Town Artist Events API ("https://rest.bandsintown.com/artists/" + artist + "/events?app_id=codingbootcamp") for an artist and render the following information about each event to the terminal: Name of the venue Venue location Date of the Event (use moment to format this as "MM/DD/YYYY") node liri.js spotify-this-song '<song name here>' This will show the following information about the song in your terminal/bash window Artist(s) The song's name A preview link of the song from Spotify The album that the song is from If no song is provided then your program will default to "The Sign" by Ace of Base. You will utilize the node-spotify-api package in order to retrieve song information from the Spotify API. The Spotify API requires you sign up as a developer to generate the necessary credentials. You can follow these steps in order to generate a client id and client secret: Step One: Visit https://developer.spotify.com/my-applications/#!/ Step Two: Either login to your existing Spotify account or create a new one (a free account is fine) and log in. Step Three: Once logged in, navigate to https://developer.spotify.com/my-applications/#!/applications/create to register a new application to be used with the Spotify API. You can fill in whatever you'd like for these fields. When finished, click the "complete" button. Step Four: On the next screen, scroll down to where you see your client id and client secret. Copy these values down somewhere, you'll need them to use the Spotify API and the node-spotify-api package. node liri.js movie-this '<movie name here>' This will output the following information to your terminal/bash window: * Title of the movie. * Year the movie came out. * IMDB Rating of the movie. * Rotten Tomatoes Rating of the movie. * Country where the movie was produced. * Language of the movie. * Plot of the movie. * Actors in the movie. If the user doesn't type a movie in, the program will output data for the movie 'Mr. Nobody.' If you haven't watched "Mr. Nobody," then you should: http://www.imdb.com/title/tt0485947/ It's on Netflix! You'll use the request package to retrieve data from the OMDB API. Like all of the in-class activities, the OMDB API requires an API key. You may use trilogy. node liri.js do-what-it-says Using the fs Node package, LIRI will take the text inside of random.txt and then use it to call one of LIRI's commands. It should run spotify-this-song for "I Want it That Way," as follows the text in random.txt. Edit the text in random.txt to test out the feature for movie-this and my-tweets BONUS In addition to logging the data to your terminal/bash window, output the data to a .txt file called log.txt. Make sure you append each command you run to the log.txt file. Do not overwrite your file each time you run a command. Reminder: Submission on BCS Please submit the link to the Github Repository! Minimum Requirements Attempt to complete homework assignment as described in instructions. If unable to complete certain portions, please pseudocode these portions to describe what remains to be completed. Adding a README.md as well as adding this homework to your portfolio are required as well and more information can be found below. Create a README.md Add a README.md to your repository describing the project. Here are some resources for creating your README.md. Here are some resources to help you along the way: About READMEs Mastering Markdown Add To Your Portfolio After completing the homework please add the piece to your portfolio. Make sure to add a link to your updated portfolio in the comments section of your homework so the TAs can easily ensure you completed this step when they are grading the assignment. To receive an 'A' on any assignment, you must link to it from your portfolio. One More Thing If you have any questions about this project or the material we have covered, please post them in the community channels in slack so that your fellow developers can help you! If you're still having trouble, you can come to office hours for assistance from your instructor and TAs. Good Luck!

A portfolio that allows hiring managers to browse a collection of my recent projects, resume and bio. Also, navigate to my profiles on LinkedIn and GitHub.

Responsive Portfolio created with gh-pages and 100% SEO optimization. Tech Stacks, tools and features used are Reactjs, Chakra-UI, HTML 5, CSS 3, Recaptcha-v2, Typewriter-Effect, GitHub Stats, Formspree, Google Analytics, Google Tag Manager, light-theme, dark-theme.

# Unit 10 OOP Homework: Template Engine - Employee Summary One of the most important aspects of programming is writing code that is readable, reliable, and maintainable. Oftentimes, *how* we design our code is just as important as the code itself. In this homework assignment, your challenge is to build a Node CLI that takes in information about employees and generates an HTML webpage that displays summaries for each person. Since testing is a key piece in making code maintainable, you will also be ensuring that all unit tests pass. ## Instructions You will build a software engineering team generator command line application. The application will prompt the user for information about the team manager and then information about the team members. The user can input any number of team members, and they may be a mix of engineers and interns. This assignment must also pass all unit tests. When the user has completed building the team, the application will create an HTML file that displays a nicely formatted team roster based on the information provided by the user. Following the [common templates for user stories](https://en.wikipedia.org/wiki/User_story#Common_templates), we can frame this challenge as follows: ``` As a manager I want to generate a webpage that displays my team's basic info so that I have quick access to emails and GitHub profiles ``` How do you deliver this? Here are some guidelines: * Use the [Inquirer npm package](https://github.com/SBoudrias/Inquirer.js/) to prompt the user for their email, id, and specific information based on their role with the company. For instance, an intern may provide their school, whereas an engineer may provide their GitHub username. * Your app will run as a Node CLI to gather information about each employee. * Below is an example of what your application may look like. Remember, the styling is completely up to you so try to make it unique.   In the `Develop` folder, there is a `package.json`, so make sure to `npm install`. The dependencies are, [jest](https://jestjs.io/) for running the provided tests, and [inquirer](https://www.npmjs.com/package/inquirer) for collecting input from the user. There are also unit tests to help you build the classes necessary. It is recommended that you follow this workflow: 1. Run tests 2. Create or update classes to pass a single test case 3. Repeat 🎗 Remember, you can run the tests at any time with `npm run test` It is recommended that you start with a directory structure that looks like this: ``` lib/ // classes and helper code output/ // rendered output templates/ // HTML template(s) test/ // jest tests Employee.test.js Engineer.test.js Intern.test.js Manager.test.js app.js // Runs the application ``` ### Hints * Create multiple HTML templates for each type of user. For example, you could use the following templates: * `main.html` * `engineer.html` * `intern.html` * `manager.html` * You will want to make your methods as pure as possible. This means try to make your methods simple so that they are easier to test. * The different employee types should all inherit some methods and properties from a base class of `Employee`. * In your HTML template files, you may want to add a placeholder character that helps your program identify where the dynamic markup begins and ends. ## Minimum Requirements * Functional application. * GitHub repository with a unique name and a README describing the project. * User can use the CLI to generate an HTML page that displays information about their team. * All tests must pass. ### Classes The project must have the these classes: `Employee`, `Manager`, `Engineer`, `Intern`. The tests for these classes in the `tests` directory must all pass. The first class is an `Employee` parent class with the following properties and methods: * name * id * email * getName() * getId() * getEmail() * getRole() // Returns 'Employee' The other three classes will extend `Employee`. In addition to `Employee`'s properties and methods, `Manager` will also have: * officeNumber * getOfficeNumber() * getRole() // Overridden to return 'Manager' In addition to `Employee`'s properties and methods, `Engineer` will also have: * github // GitHub username * getGithub() * getRole() // Overridden to return 'Engineer' In addition to `Employee`'s properties and methods, `Intern` will also have: * school * getSchool() * getRole() // Overridden to return 'Intern' ### User input The project must prompt the user to build an engineering team. An engineering team consists of a manager, and any number of engineers and interns. ### Roster output The project must generate a `team.html` page in the `output` directory, that displays a nicely formatted team roster. Each team member should display the following in no particular order: * Name * Role * ID * Role-specific property (School, link to GitHub profile, or office number) ## Bonus * Use validation to ensure that the information provided is in the proper expected format. * Add the application to your portfolio. ## Commit Early and Often One of the most important skills to master as a web developer is version control. Building the habit of committing via Git is important for two reasons: * Your commit history is a signal to employers that you are actively working on projects and learning new skills. * Your commit history allows you to revert your codebase in the event that you need to return to a previous state. Follow these guidelines for committing: * Make single-purpose commits for related changes to ensure a clean, manageable history. If you are fixing two issues, make two commits. * Write descriptive, meaningful commit messages so that you and anyone else looking at your repository can easily understand its history. * Don't commit half-done work, for the sake of your collaborators (and your future self!). * Test your application before you commit to ensure functionality at every step in the development process. We would like you to have well over 200 commits by graduation, so commit early and often! ## Submission on BCS You are required to submit the following: * The URL of the GitHub repository * A video demonstrating the entirety of the app's functionality - - - © 2019 Trilogy Education Services, a 2U, Inc. brand. All Rights Reserved.

cs480---course-project-portfolio_manager created by GitHub Classroom

The ultimate portfolio site manager for your github projects

Portfolio Manager API rebuilt with GitHub Copilot SDK (exploring as alternative to LangGraph)

Manager + configurator for different portfolio variations, check out my github pages for an example variation

Experimenting with ChatGPT as a micro cap portfolio manager. Inspired by https://github.com/LuckyOne7777/ChatGPT-Micro-Cap-Experiment.

A professional portfolio website for Priyank Garg, a Senior Product Manager specializing in Fintech and AI. The site will showcase his experience at IndusInd Bank, Prefr, and NeoGrowth, along with his GitHub projects and resume.

My Portfolio highlights my journey from a computer engineering graduate and IT manager back to software development. Showcasing Full Stack projects, it demonstrates my skills in React.js, JavaScript, HTML/CSS, SQL, MongoDB, GitHub, problem-solving, teamwork, and continuous learning.

# 3 Levels of Portfolio Projects This is a compilation of the three different types of portfolio projects you can create. The explanation for the different types are contained in [this](https://youtu.be/RYE0QQKJI9o) YouTube video. P.S. If you're interested in contributing go ahead and create a pull request :-)  ## Level 1: Basic ### Examples: - Static website - Personal Website - Website for Local Business (Real or Create a Fake Business) - Digital Clock - Todo App - Expense Tracker - Vowel Counter - Pig Latin Generator - Weight Tracker App - Recipes App - Rock, Paper, Scissors Game - [Note Taking App](https://andysterks.github.io/note-taking-app/) ## Level 2: Intermediate ### Examples: - Space Invaders Game - Snake Game - Tetris Game - Pong Game - Calculator - Web Scraper - Flash Card App - Address Book (Contact Manager) ## Level 3: Capstone ### Examples - Facebook Clone - Twitter Clone - LinkedIn Clone - Instagram Clone - Online Forum - "Fake" E-Commerce Store - Crypto Tracker - Airline/Hotel Reservation System - WYSIWG (What you see is what you get) Editor ## Projects Idea References - [A list of sample Web App Ideas](https://flaviocopes.com/sample-app-ideas/) from Flavio Copes - [Martyr2'S Mega Project Ideas List!](https://www.dreamincode.net/forums/topic/78802-martyr2s-mega-project-ideas-list/?utm_source=pocket_mylist) from dreamincode.net - [40 Side Project Ideas for Software Engineers](https://www.codementor.io/@npostolovski/40-side-project-ideas-for-software-engineers-g8xckyxef?utm_source=pocket_mylist) from codementor.io - [30 Developer Portfolio Project Ideas](https://dev.to/allthecode/30-developer-portfolio-project-ideas-3kh5?utm_source=pocket_mylist) from Simon Barker

Node.js & MySQL Overview In this activity, you'll be creating an Amazon-like storefront with the MySQL skills you learned this week. The app will take in orders from customers and deplete stock from the store's inventory. As a bonus task, you can program your app to track product sales across your store's departments and then provide a summary of the highest-grossing departments in the store. Make sure you save and require the MySQL and Inquirer npm packages in your homework files--your app will need them for data input and storage. Submission Guide Make sure you use the normal GitHub. Because this is a CLI App, there will be no need to deploy it to Heroku. This time, though, you need to include screenshots, a gif, and/or a video showing us that you got the app working with no bugs. You can include these screenshots or a link to a video in a README.md file. Include screenshots (or a video) of typical user flows through your application (for the customer and if relevant the manager/supervisor). This includes views of the prompts and the responses after their selection (for the different selection options). Include any other screenshots you deem necessary to help someone who has never been introduced to your application understand the purpose and function of it. This is how you will communicate to potential employers/other developers in the future what you built and why, and to show how it works. Because screenshots (and well-written READMEs) are extremely important in the context of GitHub, this will be part of the grading. If you haven't written a markdown file yet, click here for a rundown, or just take a look at the raw file of these instructions. Instructions Challenge #1: Customer View (Minimum Requirement) Create a MySQL Database called bamazon. Then create a Table inside of that database called products. The products table should have each of the following columns: item_id (unique id for each product) product_name (Name of product) department_name price (cost to customer) stock_quantity (how much of the product is available in stores) Populate this database with around 10 different products. (i.e. Insert "mock" data rows into this database and table). Then create a Node application called bamazonCustomer.js. Running this application will first display all of the items available for sale. Include the ids, names, and prices of products for sale. The app should then prompt users with two messages. The first should ask them the ID of the product they would like to buy. The second message should ask how many units of the product they would like to buy. Once the customer has placed the order, your application should check if your store has enough of the product to meet the customer's request. If not, the app should log a phrase like Insufficient quantity!, and then prevent the order from going through. However, if your store does have enough of the product, you should fulfill the customer's order. This means updating the SQL database to reflect the remaining quantity. Once the update goes through, show the customer the total cost of their purchase. If this activity took you between 8-10 hours, then you've put enough time into this assignment. Feel free to stop here -- unless you want to take on the next challenge. Challenge #2: Manager View (Next Level) Create a new Node application called bamazonManager.js. Running this application will: List a set of menu options: View Products for Sale View Low Inventory Add to Inventory Add New Product If a manager selects View Products for Sale, the app should list every available item: the item IDs, names, prices, and quantities. If a manager selects View Low Inventory, then it should list all items with an inventory count lower than five. If a manager selects Add to Inventory, your app should display a prompt that will let the manager "add more" of any item currently in the store. If a manager selects Add New Product, it should allow the manager to add a completely new product to the store. If you finished Challenge #2 and put in all the hours you were willing to spend on this activity, then rest easy! Otherwise continue to the next and final challenge. Challenge #3: Supervisor View (Final Level) Create a new MySQL table called departments. Your table should include the following columns: department_id department_name over_head_costs (A dummy number you set for each department) Modify the products table so that there's a product_sales column and modify the bamazonCustomer.js app so that this value is updated with each individual products total revenue from each sale. Modify your bamazonCustomer.js app so that when a customer purchases anything from the store, the price of the product multiplied by the quantity purchased is added to the product's product_sales column. Make sure your app still updates the inventory listed in the products column. Create another Node app called bamazonSupervisor.js. Running this application will list a set of menu options: View Product Sales by Department Create New Department When a supervisor selects View Product Sales by Department, the app should display a summarized table in their terminal/bash window. Use the table below as a guide. department_id department_name over_head_costs product_sales total_profit 01 Electronics 10000 20000 10000 02 Clothing 60000 100000 40000 The total_profit column should be calculated on the fly using the difference between over_head_costs and product_sales. total_profit should not be stored in any database. You should use a custom alias. If you can't get the table to display properly after a few hours, then feel free to go back and just add total_profit to the departments table. Hint: You may need to look into aliases in MySQL. Hint: You may need to look into GROUP BYs. Hint: You may need to look into JOINS. HINT: There may be an NPM package that can log the table to the console. What's is it? Good question :) Minimum Requirements Attempt to complete homework assignment as described in instructions. If unable to complete certain portions, please pseudocode these portions to describe what remains to be completed. Create a README.md Add a README.md to your repository describing the project. Here are some resources for creating your README.md. Here are some resources to help you along the way: About READMEs Mastering Markdown Add To Your Portfolio After completing the homework please add the piece to your portfolio. Make sure to add a link to your updated portfolio in the comments section of your homework so the TAs can easily ensure you completed this step when they are grading the assignment. To receive an 'A' on any assignment, you must link to it from your portfolio. One More Thing If you have any questions about this project or the material we have covered, please post them in the community channels in slack so that your fellow developers can help you! If you're still having trouble, you can come to office hours for assistance from your instructor and TAs. Good Luck!

A high-fidelity GitHub profile analyzer that sequences technical DNA, extracts AI-driven archetype insights, and visualizes developer trajectories with neural precision

Professional GitHub Portfolio Management System | Sistema Profesional de Gestión de Portfolio GitHub - Automated auditing, classification, and transformation of repositories for career development | Auditoría automatizada, clasificación y transformación de repositorios para desarrollo profesional

Automated MCP server for GitHub portfolio management

Console Task Manager in Python for GitHub portfolio

AI-SDLC pipeline that audits GitHub repos for Engineering Manager portfolio value

PMP® | CSM — Project Manager portfolio: case studies, templates & GitHub Pages site.

Flask Task Manager with S3, Lambda, Apache2, Docker, GitHub Actions CI/CD — AWS DevOps Portfolio Project

A user friendly real-time trading simulator & portfolio manager — live at sudonils42.github.io/simple-trade/

# Task Manager Simple Team Name: Simple Portfolio website This is a simple task manager project that demonstrates basic GitHub collaboration, branching, pull requests, and JavaScript notifications.

Simple Written RP manager/Showoff portfolio with possible voting and admin system via codephrase setted in github secret

A simple task manager written in Python that utilizes a command line interface. Cloned for professional portfolio. Original repository: https://github.com/VoidKeeperNull/Python-CLI-Task-Manager

A modern and minimal Link manager app to organise your needy article, websites, portfolio, social, github repo in one place.

This is a visual stock portfolio analyzer. It helps portfolio managers make trade recommendations for their clients. This project is a part of https://criodo.github.io/Crio-Accelerate-May-2020-haywire2207/.

PHP/MySQL exchange rate tracker and portfolio manager. Scrapes live currency rates from Turkish banks (starting with Dünya Katılım), auto-updates when source tables change, and supports portfolio tracking. Self-updates via GitHub releases.

Personal Web3 portfolio showcasing my work as a Community Manager, Content Creator, and Research Enthusiast. Built with HTML, CSS & JavaScript and hosted on GitHub Pages