Giter VIP home page Giter VIP logo

Tony Byamungu's Projects

coding-assistant icon coding-assistant

As beginner sometime you just need to get more details about the program or task you're working on in order to write it, and you end up spending more time googling instead of learning I've noticed that students who search for learning content can be overwhelmed and discouraged by too many search results that do not meet their needs. Students need to use their time learning, not searching for learning content. I believe that Hyperiondev has great content and therefore students here must become self-service. this can decrease the need for Human resource and allow mentors to focus on students who really need that direct human attention.

dae-of-fast-food-restaurant-accross-usa icon dae-of-fast-food-restaurant-accross-usa

In this Data Analysis and Exploration we're using the list of over 10,000 Fast Food restaurants provided by Datafiniti's Business Database. The dataset includes the restaurant's address, city, latitude and longitude coordinates, name, and more. Note that this is a sample of a large dataset The dataset contains 8 Columns and 10000 rows, the columns are mostly of Categorical variables except for longitude and latitude columns which are Continuous variables. See that the Dataset did not come with a Land Area Column I have decided to bring in another Dataset that has Land Area data and join it to our original Dataset this will help us to determine which state has the most Fast Food per meter or mile square.

data-understanding-and-preparation icon data-understanding-and-preparation

(by IBM)In this tutorial, we demonstrated the use of Pandas in Python to perform exploratory data analysis and do the necessary data preparations before creating predictive models. We also investigated the relationship between input variables and target variables.

discord-for-your-team icon discord-for-your-team

In this article we will have an overview of discord and how it could be benificial for teams. We're going to narrow this post to developers particularly #pythoneers, #datascientist

py-tony-tony-portfolio icon py-tony-tony-portfolio

This Repo was a beginner project I completed while doing my interview at Microverse for remote software devopers It was very basic one page webpage but I past the interview... then I decided to extend it to a more professional portfolio website (turn out to be a cool website check it out

responsive-web-design-projects---build-a-tribute-page icon responsive-web-design-projects---build-a-tribute-page

User Story #1: My tribute page should have an element with a corresponding id="main", which contains all other elements. User Story #2: I should see an element with a corresponding id="title", which contains a string (i.e. text) that describes the subject of the tribute page (e.g. "Dr. Norman Borlaug"). User Story #3: I should see a div element with a corresponding id="img-div". User Story #4: Within the img-div element, I should see an img element with a corresponding id="image". User Story #5: Within the img-div element, I should see an element with a corresponding id="img-caption" that contains textual content describing the image shown in img-div. User Story #6: I should see an element with a corresponding id="tribute-info", which contains textual content describing the subject of the tribute page. User Story #7: I should see an a element with a corresponding id="tribute-link", which links to an outside site that contains additional information about the subject of the tribute page. HINT: You must give your element an attribute of target and set it to _blank in order for your link to open in a new tab (i.e. target="_blank"). User Story #8: The img element should responsively resize, relative to the width of its parent element, without exceeding its original size. User Story #9: The img element should be centered within its parent element.

sample-survey-form-for-free-code-camp-project icon sample-survey-form-for-free-code-camp-project

User Story #1: I can see a title with id="title" in H1 sized text. User Story #2: I can see a short explanation with id="description" in P sized text. User Story #3: I can see a form with id="survey-form". User Story #4: Inside the form element, I am required to enter my name in a field with id="name". User Story #5: Inside the form element, I am required to enter an email in a field with id="email". User Story #6: If I enter an email that is not formatted correctly, I will see an HTML5 validation error. User Story #7: Inside the form, I can enter a number in a field with id="number". User Story #8: If I enter non-numbers in the number input, I will see an HTML5 validation error. User Story #9: If I enter numbers outside the range of the number input, which are defined by the min and max attributes, I will see an HTML5 validation error. User Story #10: For the name, email, and number input fields inside the form I can see corresponding labels that describe the purpose of each field with the following ids: id="name-label", id="email-label", and id="number-label". User Story #11: For the name, email, and number input fields, I can see placeholder text that gives me a description or instructions for each field. User Story #12: Inside the form element, I can select an option from a dropdown that has a corresponding id="dropdown". User Story #13: Inside the form element, I can select a field from one or more groups of radio buttons. Each group should be grouped using the name attribute. User Story #14: Inside the form element, I can select several fields from a series of checkboxes, each of which must have a value attribute. User Story #15: Inside the form element, I am presented with a textarea at the end for additional comments. User Story #16: Inside the form element, I am presented with a button with id="submit" to submit all my inputs.

technical-documentation-page-free-code-camp-project icon technical-documentation-page-free-code-camp-project

User Story #1: I can see a main element with a corresponding id="main-doc", which contains the page's main content (technical documentation). User Story #2: Within the #main-doc element, I can see several section elements, each with a class of main-section. There should be a minimum of 5. User Story #3: The first element within each .main-section should be a header element which contains text that describes the topic of that section. User Story #4: Each section element with the class of main-section should also have an id that corresponds with the text of each header contained within it. Any spaces should be replaced with underscores (e.g. The section that contains the header "JavaScript and Java" should have a corresponding id="JavaScript_and_Java"). User Story #5: The .main-section elements should contain at least 10 p elements total (not each). User Story #6: The .main-section elements should contain at least 5 code elements total (not each). User Story #7: The .main-section elements should contain at least 5 li items total (not each). User Story #8: I can see a nav element with a corresponding id="navbar". User Story #9: The navbar element should contain one header element which contains text that describes the topic of the technical documentation. User Story #10: Additionally, the navbar should contain link (a) elements with the class of nav-link. There should be one for every element with the class main-section. User Story #11: The header element in the navbar must come before any link (a) elements in the navbar. User Story #12: Each element with the class of nav-link should contain text that corresponds to the header text within each section (e.g. if you have a "Hello world" section/header, your navbar should have an element which contains the text "Hello world"). User Story #13: When I click on a navbar element, the page should navigate to the corresponding section of the main-doc element (e.g. If I click on a nav-link element that contains the text "Hello world", the page navigates to a section element that has that id and contains the corresponding header. User Story #14: On regular sized devices (laptops, desktops), the element with id="navbar" should be shown on the left side of the screen and should always be visible to the user. User Story #15: My Technical Documentation page should use at least one media query.

web-master-jean icon web-master-jean

This repos contains files, data, projects, etc. of Jean School of IT Course.

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.