Google Class Code
BSIT 1B Introduction to Computing Google Class Code: x2ek323
BSIT 1B Introduction to Programming Google Class Code: ofrnwdu
BSIT 1A Introduction to Programming Google Class Code: bbhh6gn
Instructor
Ric Montemayor Torregoza
rmtthorregoza15@gmail.com
Description
a brief introduction to programming and the academic interests of computer technology. Students learn excellent algorithmic problem-solving techniques in this course. Resources management, security, software engineering, and web programming are among the topics taught in this course. Among the languages that are offered are HTML, CSS, JavaScript, Python, SQL, C, C++, and Java. The social sciences, humanities, and sciences all have their own distinct problem sets. The culmination of the course is a final project.
Expectations
Your obligation is to
video lectures, which will take occur asynchronously. join class meetings using Zoom or Google Meet. completing laboratory tasks handle problem sets synchronously or asynchronously This will be done on our YouTube channel while taking assessments, quizzes, and labs. take an important exam, and, if time permits, plan and complete a final project.
Grades
These weights are used to calculate final grades:
| Problem Sets | 40% |
| Quizzes | 10% |
| Labs | 10% |
| Test | 20% |
| Final Project | 10% |
| Attendance* | 10% |
Tutorials
The complement to sections includes tutorials, opportunities for problem-set assistance by appointment, tutoring, and office hours offered by the course's teaching fellows and course assistants.
Quizzes
Quizzes are brief assignments that are due following each lesson and let you use the knowledge from the previous week to solve brand-new issues. Every quiz is open-book; you are free to utilize any non-human resources you like, but the only people you can ask for aid from or get help from are the course heads.
Test
The exam provides an opportunity to consolidate knowledge gained over several weeks and apply skills acquired to new issues. The test is open-book; you are free to utilize any non-human resources you choose, but the only people you can ask for help from or get help from are the course instructors.
Final Project
This course's final project is its high point. Your chance to put your newly acquired programming knowledge to the test and create your very own piece of software comes with the final project. The nature of your project is totally up to you, though it must receive staff permission, as long as it incorporates the principles from this course. If the staff agrees, you may execute your project in any language(s). If the staff finally has access to the gear and software your project requires, you are permitted to use any infrastructure. We just ask that you create something that interests you, that you address a real issue, that you have an impact on campus, or that you alter the course of human history. Try to build something that endures after this course.
Given that software development is rarely a solo endeavor, you are given the opportunity to work together on this final project with one or more of your peers. It goes without saying that it is expected that each student will contribute equally to the planning and carrying out of the project for any such group. Furthermore, a two- or three-person group project is anticipated to have a scope that is twice as large or three times as large as a conventional one-person project. Mind you, a one-person project should need more time and effort than each issue given in the course. You are welcome to seek guidance from others as long as you adhere to the course's guideline on soliciting help from others, even though no more than three students may develop and implement a specific project.
Lateness Policy
Your grade for the project will be reduced by 0.1% for each minute that a problem set, quiz, or lab is turned in late. Late work won't be allowed for the final project (so once a project is 3 hours late, it gets no credit at all).
Extension Policy
During the term you may grant yourself a 2 hours-day extension. That extension cannot be apportioned among multiple problem sets or be applied to any of the quizzes, labs, or the final project’s milestones. To grant yourself this extension, once must have a valid reason.
Name:
Student ID:
Reason for extension of Quiz, Activity, Lab:
Mothers name and signature:
Please send me this form in MS Word format. The extension request form must be completed on the day of the activities, quizzes, and labs; it will not be accepted if it is submitted the next day.
The request will be assessed by the IT instructors, thus it might or might not be accepted. The late policy above may also be combined with any extensions granted to you in accordance with the conditions of this policy. The work will not be accepted in any way after the original deadline has passed by two hours.
Mental Health
If you experience significant stress or worry, changes in mood, or problems eating or sleeping this semester, whether because of IT or other courses or factors, please do not hesitate to reach out immediately, at any hour to discuss. Everyone can benefit from support during challenging times. Not only are we happy to listen and make accommodations with deadlines as needed, we can also refer you to additional support structures on campus.
Academic Honesty
The course’s philosophy on academic honesty is best stated as “be reasonable.” The course recognizes that interactions with classmates and others can facilitate mastery of the course’s material. However, there remains a line between enlisting the help of another and submitting the work of another. This policy characterizes both sides of that line.
The essence of all work that you submit to this course must be your own. Collaboration on problem sets is not permitted except to the extent that you may ask classmates and others for help so long as that help does not reduce to another doing your work for you. Generally speaking, when asking for help, you may show your code to others, but you may not view theirs, so long as you and they respect this policy’s other constraints. Collaboration on the course’s quizzes and test is not permitted at all. Collaboration on the course’s final project is permitted to the extent prescribed by its specification.
Regret clause. If you commit some act that is not reasonable but bring it to the attention of the course’s heads within 72 hours, the course may impose local sanctions that may include an unsatisfactory or failing grade for work submitted, but the course will not refer the matter for further disciplinary action except in cases of repeated acts.
Below are rules of thumb that (inexhaustively) characterize acts that the course considers reasonable and not reasonable. If in doubt as to whether some act is reasonable, do not commit it until you solicit and receive approval in writing from the course’s Instructor. Acts considered not reasonable by the course are handled harshly. If the course refers some matter for disciplinary action and the outcome is punitive, the course reserves the right to impose local sanctions on top of that outcome that may include an unsatisfactory or failing grade for work submitted or for the course itself. The course ordinarily recommends exclusion (i.e., required withdrawal) from the course itself.
Reasonable
- Communicating with classmates about problem sets’ problems in English (or some other spoken language), and properly citing those discussions.
- Discussing the course’s material with others in order to understand it better.
- Helping a classmate identify a bug in their code at office hours, elsewhere, or even online, as by viewing, compiling, or running their code after you have submitted that portion of the problem set yourself.
- Incorporating a few lines of code that you find online or elsewhere into your own code, provided that those lines are not themselves solutions to assigned problems and that you cite the lines’ origins.
- Reviewing past semesters’ tests and quizzes and solutions there to.
- Sending or showing code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a bug, provided you properly cite the help.
- Submitting the same or similar work to this course that you have submitted previously to this course, unless you committed some act while doing that work that is not reasonable, in which case you should re-do the work without viewing the old.
- Turning to the course’s heads for help or receiving help from the course’s heads during the quizzes or test.
- Turning to the web or elsewhere for instruction beyond the course’s own, for references, and for solutions to technical difficulties, but not for outright solutions to problem set’s problems or your own final project.
- Whiteboarding solutions to problem sets with others using diagrams or pseudocode but not actual code.
- Working with (and even paying) a tutor to help you with the course, provided the tutor does not do your work for you.
Not Reasonable
- Accessing a solution to some problem prior to its deadline.
- Accessing or attempting to access, without permission, an account not your own.
- Asking a classmate to see their solution to a problem set’s problem before its deadline.
- Discovering but failing to disclose to the course’s heads bugs in the course’s software that affect scores.
- Decompiling, deobfuscating, or disassembling the staff’s solutions to problem sets.
- Failing to cite (as with comments) the origins of code or techniques that you discover outside of the course’s own lessons and integrate into your own work, even while respecting this policy’s other constraints.
- Giving or showing to a classmate a solution to a problem set’s problem when it is he or she, and not you, who is struggling to solve it.
- Looking at another individual’s work during the quizzes or test.
- Manipulating or attempting to manipulate scores artificially, as by exploiting bugs or formulas in the course’s software.
- Paying or offering to pay an individual for work that you may submit as (part of) your own.
- Searching for or soliciting outright solutions to problem sets online or elsewhere.
- Splitting a problem set’s workload with another individual and combining your work.
- Submitting (after possibly modifying) the work of another individual beyond the few lines allowed herein.
- Submitting work to this course that you intend to use outside of the course (e.g., for a job) without prior approval from the course’s heads.
- Turning to humans (besides the course’s heads) for help or receiving help from humans (besides the course’s heads) during the quizzes or test.
- Viewing another’s solution to a problem set’s problem and basing your own solution on it.
- Viewing the solution to a lab before trying to solve it yourself.
Acknowledgement and Authorization
ITHUB plans to record audio, photos, and video of Information Technology lectures, sections, office hours, seminars, and other events and activities related to IT (the “Recordings”), with the aims of making the content of the course more widely available and contributing to public understanding of innovative learning (the “Projects”). As part of the Projects, the Recordings, or edited versions of them, may be made available to other students, to students at other educational institutions, and to the broader public in the Internet, television, theatrical distribution, digital media, or other means. One of the ways it is expected that the Recordings, or edited versions of them, will be made publicly available is under a Creative Commons Attribution-NonCommercial-ShareAlike (ITHUB) license. Another example is that ITHUB may make and disseminate montages of “memories” from the class with images from the Recordings. The Recordings also may be used to make other derivative works in the future. Students may elect not to appear in photos and video used in the Projects and may still participate fully in IT class.
If you have any questions about the above, contact us RMT