Erik Pohl ErikPohl-Lot49-Projects

## code_standards_checklist.csv

          
            Task
             Status

            
              Unit tests added for any new development

            
              Build regression tests if they don't already exist

            
              100% passing of regression tests

            
              Meaningful exceptions and exception-handling coverage

            
              Thoughtful & self-documenting variable/property/method and function names

            
              Adequate output to permit users to understand the results and assist in the self-documenting nature of the code

            
              Actual docstring comments at all levels of the code

            
              Linting the code for PEP 8 standardization and other linters

            
              Applying a PEP formatter to the code

## Bridge.py
"""
Decouple the implementation from its abstract class
so that the abstraction can only be loosely coupled to an otherwise independent implementation
"""

import abc


class dinner_abstraction:
    """

## buider.py
from abc import ABCMeta, abstractmethod


class Chair(object):
    def __init__(self, legs=3, material='Wood', color='Oak'):
        self.legs = legs
        self.material = material
        self.color = color

    def __str__(self):

## project_planning_pattern.csv

          
            Action
            Owner
            Time

            
              Collaborate with all stakeholders and participants on an initial plan
              PM and team
              Before the project

            
              Are there any questions or doubts? encourage the team to ask and ask them as PM
               PM and team
               Before the project

            
              Encourage this up to project start
              PM and team
               Before the project

            
              During the execution record any deviations from plan
              PM and team
               During the project

            
              Hold a retrospective review a couple of days later and revise the plan
               PM and team
               After the project

## checklist_checklist_pattern.csv

          
            Action
             Owner
             Action day/time

            
              Build a first checklist before doing a thing
               Team
               Before doing a thing

            
              Do the thing using the checklist-- use best judgement when altering the plan and document changes
               Team
               While doing a thing

            
              Conduct a retrospective after doing the thing and refine the checklist
               Team
               After doing the thing

## abstract_factory.py
"""
This is an interface to make dependent or logically related objects
without the need up-front to specify the classes
so you can make multiple grouping of classes with this one abstract
factory

"""

import abc

## prototype.py
"""
Create one prototypical instance, then create new objects using those instances
"""

import copy


class Kambucha:
    """
    This is an example class which is the source and can be copied

## ChainOfResponsibility.py
"""
Class design benefits from decoupling senders of requests from receivers
This pattern allows you to do this by designing a series
"if this doesn't work, try this" objects to handle the request.
The request gets passed along until an object handles it.
"""

import abc


## command.py
"""
Encapsulate a request as an object, thereby letting you parameterize
clients with different requests, queue or log requests, and support
undoable operations.
"""

import abc


class Invoker:

## state.py
"""
This pattern permits an object to alter its behavior when its internal state changes.
The object will appear to change its class.
"""

import abc


class TrafficLight:
    """
	Task	Status
	Unit tests added for any new development
	Build regression tests if they don't already exist
	100% passing of regression tests
	Meaningful exceptions and exception-handling coverage
	Thoughtful & self-documenting variable/property/method and function names
	Adequate output to permit users to understand the results and assist in the self-documenting nature of the code
	Actual docstring comments at all levels of the code
	Linting the code for PEP 8 standardization and other linters
	Applying a PEP formatter to the code
	"""
	Decouple the implementation from its abstract class
	so that the abstraction can only be loosely coupled to an otherwise independent implementation
	"""

	import abc


	class dinner_abstraction:
	"""
	from abc import ABCMeta, abstractmethod


	class Chair(object):
	def __init__(self, legs=3, material='Wood', color='Oak'):
	self.legs = legs
	self.material = material
	self.color = color

	def __str__(self):
Action	Owner	Time
Collaborate with all stakeholders and participants on an initial plan	PM and team	Before the project
Are there any questions or doubts? encourage the team to ask and ask them as PM	PM and team	Before the project
Encourage this up to project start	PM and team	Before the project
During the execution record any deviations from plan	PM and team	During the project
Hold a retrospective review a couple of days later and revise the plan	PM and team	After the project
Action	Owner	Action day/time
Build a first checklist before doing a thing	Team	Before doing a thing
Do the thing using the checklist-- use best judgement when altering the plan and document changes	Team	While doing a thing
Conduct a retrospective after doing the thing and refine the checklist	Team	After doing the thing
	"""
	This is an interface to make dependent or logically related objects
	without the need up-front to specify the classes
	so you can make multiple grouping of classes with this one abstract
	factory

	"""

	import abc
	"""
	Create one prototypical instance, then create new objects using those instances
	"""

	import copy


	class Kambucha:
	"""
	This is an example class which is the source and can be copied
	"""
	Class design benefits from decoupling senders of requests from receivers
	This pattern allows you to do this by designing a series
	"if this doesn't work, try this" objects to handle the request.
	The request gets passed along until an object handles it.
	"""

	import abc
	"""
	Encapsulate a request as an object, thereby letting you parameterize
	clients with different requests, queue or log requests, and support
	undoable operations.
	"""

	import abc


	class Invoker:
	"""
	This pattern permits an object to alter its behavior when its internal state changes.
	The object will appear to change its class.
	"""

	import abc


	class TrafficLight:
	"""