CSA Blog

Ian Wu

Sprint 1 - Review Ticket

22 Aug 2024 • Sprint 1

Sprint 1 Page

Laptop Verification or Cloud Workspace Notes:

  • Created script that runs verification commands and outputs commands to a post demonstrating successful installation
  • Verifies versions of tools, easy debugging
  • Post

GitHub Pages Actions Notes:

Hacks Tools & Equipment Play Notes:

  • Tools Installation Hack: Verification Script (see laptop verification above)
  • Answers to tools installation commands: Link
  • JavaScript: Used Leaflet to create a map
  • Utilizes geojson file with US county boundaries to display US counties
  • Colors the counties to show which ones I have been to
  • Link

Hacks GitHub Pages Playground Notes:

  • Theme: Imported Jekyll Hydeout theme
  • Different formats, modified layouts as evident by whole blog
  • Switching Blogs: Imports theme on Jekyll and therefore swapping css themes becomes more tricky
  • Solution: Store two different blog themes/layouts, in _bak folders and script changes theme of blog
  • Modifies _config.yml, as well as pages due to different labeling in blog layouts
  • Script
  • Future improvements could fetch directly from a blog’s github page

Hacks SASS Basics Notes:

  • Copied over calculator files: utilizes calculator.scss file
  • Link
  • Utilizes SASS features (@mixin, @includes, @extend, variables, etc.)
  • Reuses button code multiple times for different types of buttons

Hacks Frontend Notes:

  • Frontend wireframe knowledge is demonstrated by formatting of Emoji page
  • See Link Below

Pair Programming Notes:

  • Emoji!
  • User is provided with a canvas to draw on
    • Brush Size slider allows user to control size of brush
    • IRO Color Picker allows user to choose color
  • Page analyses drawing and compares to emojis useing Mean Squared Error to identify the closest emoji
  • Displays emoji!
  • Link

Sprint 1 - Objectives

21 Aug 2024

Issue

Project-base Learning Requirements

Each sprint there will be hacks and project-based learning requirements. It is up to the individual to develop their own plan for how they will represent work. Here are some links and tips.

  • All work, tangible artifacts, will be captured in personal GitHub Pages
  • Tools and Software Development requirements are foundational requirements for all the CompSci courses. Thus, they are shared, but listed under CSSE Projects
  • To obtain clarity on instructions you should start by picking a post in Sprint 1, then ask questions.
  • In Agile Development methodology, which we will learn throughout the course, an iteration (plans, designs, review references, coding) and questions should all be considered as part of your work.
  • Since iteraction and questions are part of your work, you should consider capturing and outlining iterations and questions in your blog.
  • Be aware, you will get more “Points” if you “Indicate” that you are progressing on a CompSci journey.
  • There are very few “Correct Answers” in this class! As you code, you will see that there is always more bugs and features.

Classroom Guidelines

It will be a very bad day when you say… “I have everything done”. This statement typically comes by students that are lacking understading.

This statement shows that the person making the statement knows very little about CompSci and the principles of iteration that are being promoted in this class. In fact, that state does not agree with Agile Development Methodologies that we will be learning in this class.

The Teacher likes behaviors that are easily viewed and interpreted as productive to CompSci learning.

  • Code, Code, Code. This is the process of making code and involves making plans, designs, reviewing references, asking questions and Code-Code-Coding.
  • No paper. We will be learning to do all work electronically.
  • Work Talk. A very high percentate 75%, 80% or more of your talk during class should be code, code, code talk.
  • Ears that can listen. 100% of time you should be available for discussion. Covered or plugged in ears restricts hearing.
  • Hands that can code. The primary coding device is assumed to be your laptop! Sprint 1 will be focused on laptop importance.

Read Learning Habits Table to understand how behaviors will impact grading.