 course, Unit 6 enables students to apply the skills they have learned in a large-scale, individualized project setting. Cutting this unit would deprive students of the opportunity to experience a close approximation of a real-world development setting. Earlier units should be condensed or cut as necessary to ensure that Unit 6 is still included in the curriculum.
Most lesson plans in this curriculum are designed to represent a single 55-minute class period with average pacing. Each class will have slightly different needs, possibly including different period length, student capabilities, classroom interruptions, and more. Teachers and volunteers are encouraged to consider the lesson plans as guidance for one possible use of time to present the material, and to feel free to adapt the lesson plans as necessary to fit the needs of the particular class in which the plans are being applied.
Five minutes are allotted at the beginning of each day for administrative tasks such as taking attendance, giving announcements, returning work, or other necessary actions. During this time, teachers are encouraged to assign "bell work" (sometimes called "do now" activities) for students to work on.
These activities aim to engage students with the subject immediately upon entering the room, and should be short, clear, and able to be completed by all students.
Specific "do now" activities are not given in the lesson plans, as they should be chosen by the teacher to reinforce or preview the specific topics with which students have or are expected to struggle most.
Most lessons begin with a brief period of instruction on the topic of the day. These sections should be kept as brief as possible—the primary means of student learning in most lessons will be the lab activities.
The goals of the instruction section of the lesson should be to motivate the concepts being exercised in the lab and to provide a short demonstration to help students find the necessary parts of Snap! the first time.
Teaching teams should vary the ways in which the instruction is presented throughout the course, including class discussions, kinesthetic activities, demonstrations, Socratic seminars, occasional lectures, and other approaches.
The largest portion of time in each lesson is dedicated to a guided activity that allows students to explore and practice with the day's key topics. Each activity is broken down into several parts, each of which consists of several steps. In general, the steps in a single section build on each other, and each section covers a new topic or new application.
It is intended that the labs be well enough structured for students to work through on their own, but teachers should feel free to interject at appropriate points to assess student progress and provide additional guidance as necessary.
On occasion, steps 3 and 4 are repeated for multi-part activities.
After each activity has concluded, time is allotted for teachers to review and debrief the activities with students. In general, there is not enough time, nor is there necessarily the need, to go through the lab step-by-step. Students should be able to at least partially assess their own progress by verifying that their programs function as specified in the lab.
Rather than presenting solutions to each step of the lab, teachers are encouraged to use the debrief time to focus on particularly tricky or noteworthy parts of the lab or to discuss areas in which students struggled.
Debrief time can also be used to compare and contrast different possible approaches to some of the problems, emphasizing that, in most cases, there is more than one valid solution.
Whenever possible, use examples of student work rather than instructor-created solutions during the debrief—this is an excellent chance to showcase students who solve problems in elegant, creative, or canonical ways.
The curriculum includes a few special lesson plans that are intended to be applied at multiple times during the semester. These lesson plans are templates for a particular type of lesson, though the specific topics will vary each time the plan is used.
This lesson plan provides structure for a typical "lab day" (a class day in which students are primarily working on a larger-scale project).
The lab day lesson plan will most often be used during the culminating project of each unit, but can also occasionally be used for larger lab activities that require being split over multiple days.
The lab day lesson provides a basic structure for reviewing and reinforcing important concepts before providing time for students to work independently.
The lesson also provides recommendations for how to deal with questions and struggling students, and how to gauge student progress over the course of a project.
These lesson plans provide the basic outline for possible types of "culture days" (class days in which cultural, social, societal, or other topics not directly related to programming are covered).
These days are vital to the experience of this course, as they provide opportunities for students to connect the skills and concepts they are learning to real-world problems, view their society and culture through the lens of technology, and get glimpses of the types of problems and applications that they could encounter in further study of computer science.
These lessons also provide an outstanding opportunity for students to bring their own personal experiences or knowledge into the classroom.
Each culture day lesson plan provides a high-level structure for conducting one of several different forms of a culture day.
Suggested topics are provided, but teaching teams are encouraged to choose topics that are both of interest to their students and that play to the strengths of the instructors.
These lessons may require more preparation than the typical lesson to adapt the plan to the particular topic chosen.
This curriculum does not assign homework as part of its typical lessons. Because this curriculum is intended to be used in a wide variety of classrooms, some of which may include students that do not have regular access to an internet-enabled computer at home, all work is done during class time. In some circumstances, assigning some lab activities as homework can enable the teaching team to regain in-class time for additional lessons or activities, but this must be done with care. In particular, if homework is assigned, arrangements must be made so that any students who do not have the ability to complete the homework at home do not fall behind. Further, it should be expected that some students will not complete the assigned homework and teaching teams must have a way to both assess that homework was completed and ensure the material is reinforced briefly in class.
To gauge student understanding, the addition of Unit quizzes has been added. These are intended as low stakes formative assessments that allow students to visit topics at the end of the unit to reinforce learning. They are open book giving students incentive to take good notes. Ideally the quizzes are non-graded and students would reflect on the answers they got wrong in order to learn from their mistakes.
Student work consists of class participation, daily labs, end of unit projects, and final project. Each classroom teacher is responsible for determining the grading breakdown for their classes. TEALS recommends the following as a starting point as grading guidelines for the introductory computer science course.
Participation, Notebooks, etc.
This curriculum is considered a living document and is intended to be updated regularly both by the TEALS team and with contributions from the TEALS community. In particular, feedback on teaching teams' experiences in conducting the lessons in this curriculum is always welcome. Teaching teams are also encouraged to share ideas for additional activities, lessons, or projects that can be incorporated into the curriculum guide. Please see the Contributing page for more information about how to contribute to the curriculum.
click on the document to enable the pdf menu to show and clicking the down arrow or "Save as Copy"
right click on the.pdf document and select "Save As"Custom P2P Lending Marketplace
Explore how Cuspy created a large and secure peer-lending website.
Screenshots
Dedicated Engineers
Challenge
The Customer wanted to build a P2P lending marketplace and hence was looking for dedicated web developers to scale their team.
Solution
Web developers from Cuspy joined the Customer’s dev team at an early stage of the project and thus contributed to both the architecture and the actual functionality of the peer-lending platform.
The P2P lending marketplace was delivered on time and equipped with all the must-have features:
• Admin tools that were convenient for non-tech-savvy users and included reports on updates and applicant, payment, loans, and appointment management;
• Lender dashboards with personal data and a feature for managing loans;
• Borrower dashboards with a handy lender search engine, personal and credit status data;
• Integrations with SSL (for security) and the needed 3rd-party tools and APIs (for billing and notification purposes);
• Loan calculator;
• Blog with useful advice for lenders and borrowers.
Tech Stack
Results
Dedicated web developers at Cuspy built a P2P lending marketplace that can also run on mobile. The modular architecture of the solution allows the Customer to safely introduce changes to the platform without harming its overall performance. Thanks to detailed documentation and maintainable code, there is no vendor lock-in.I have one that may not ever pass 93:20 but it's the most recent of mine. I have a very pleasant memory of this season's win against Tottenham, it had the whole Christmas vibe around it and we played really good. And I think it was our fans best display this season, right after pep asked for the fans to give their best support at his press conference, with the squad being very exhausted because of the tight schedule. Also, can't forget the nasty fouls on our players and KDB being one of them, only to be followed by his banger and a beautiful 4-1 at the end. And the cherry in the top was the broadcasting showing a picture of a blue moon on a big screen at the last minutes... felt magical indeed.What. It’s not simply a place to work from, it’s a place to belong to.
Fresh, new look
From the welcoming reception right