Skip to content

ThirdAndjel/Pisello

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 

Repository files navigation

Pisello - A pomodoro style pea counting app

Like a Pomodoro, Pisello will time work sessions and break sessions. Pisellos are measured in buckets, pea pods and peas, instead of minutes and seconds. Just like peas in a pod, Pisellos vary in time slightly every run.

With a Pomodoro type timer, a person could start stressing, knowing that their time is running out or could start procrastinating towards the end of the timer, reducing their productivity. An approximate timer would emulate another person telling them to stop at an approximate/slightly unexpected time (more human, less machine-like).

Pisello v.1: Single .rb that runs once, and must be started again to perform another Pisello. This version will provide near 20 minutes of work, and near 5 minutes of break. A visual indication of bucket/pea pod/pea counting will be displayed.

Pisello v.2: The user will be able to specify how long the work session and break should be in a Pisello. Another Pisello can be started without exiting the app. The number of Pisellos performed will be tracked.

Pisello v.3: Pisello will now provide audio reminders to tell the user when it is time to break and start work again.

Relative Week 1 and 2 Learning Goals

-Github usage
-Pairing
-Memorize the syntax for creating classes, functions, and common ruby data structures
-Basic troubleshooting
-Understand classes, returns, and variables
-Use instance and local variables
-Use instance and class methods
-Us if, booleans, loops, and each.
-Understand the difference between a Hash and an Array
-Use ruby debugger or pry
-Memorize common iterators and conditional statements
-Run tests and understand their output
-Use autotest/watchr to automate test running
-Memorize common test patterns
-Memorize the boilerplate for creating tests and test cases
-Be able to create tests for existing code
-Be able to write code to satisfy existing tests
-Be able to fix bugs uncovered by tests
-Memorize the common assertions and refutations

Measures for success

-Create a basic, functional version of the program that can be improved upon later.
-Create the application through test driven development.
-This is our first time working together, so focus on teamwork.
-Take turns driving and navigating.
-All research will be done as a group.
-Review our teamwork after version 1 of the program.
-All research to be placed on 3x5 note cards.
-Review individual strengths and weaknesses.
-Review what we think we are (Driver/Navigator).
-Each team member able to manage project through Github.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages