Sense & Scale

A site to explore cultures, cities, and computing at varying senses and scales. Updated by Ar Ducao, with content from classes at NYU, MIT, CUNY and more.

Contact: see syllabi

  • Agenda

    Assignment

    1. Read/listen, take notes, and be ready for in-class timed exercises & discussions on: 
      • The epigraph and Introduction of Medical Apartheid by Harriet A. Washington, available in ePub and audio. Note that this book was written in 2006; much of its information is (sadly) still correct; but some of its terminology is no longer in keeping with the MLA and APA guidelines on inclusive language.
      • “Sonny’s Blues” by James Baldwin, available in epub and audiobook (NYU login required).
        • With the audio: start in Part 3 at 35:38 and end at Part 4 at 55:37.
    2. What current technology issues come to mind from your reading? Please find a news item about a relevant technology issue, and add its URL to the 9/25 tab in D&T News Items 2024.
    +
  • Announcements Agenda Assignment

    Announcements

    • Please log into Brighspace now and note the availability of all Timed Exercise extensions. All students must be caught up by this Sunday. No more extensions without an accommodation via Student Advocacy, the Moses Center, or the office of Spiritual Life.
      • I’m grading exercises as they come in, but will refrain from publishing grades until everyone is caught up.

    Agenda

    Assignment

    1. Read/listen, take notes, and be ready for in-class timed exercises & discussions on: 
      • The epigraph and Introduction of Medical Apartheid by Harriet A. Washington, available in ePub and audio. Note that this book was written in 2006; much of its information is (sadly) still correct; but some of its terminology is no longer in keeping with the MLA and APA guidelines on inclusive language.
      • “Sonny’s Blues” by James Baldwin, available in epub and audiobook (NYU login required).
        • With the audio: start in Part 3 at 35:38 and end at Part 4 at 55:37.
    2. What current technology issues come to mind from your reading? Please find a news item about a relevant technology issue, and add its URL to the 9/23 tab in D&T News Items 2024.
    +
  • There is no excerpt because this is a protected post.

    This content is password protected. To view it please enter your password below:

    + ,
  • Summer 2024Prof. Ar Ducao, arlduc [at] nyu.eduTuesdays, 12:15-3:15 PMWallkill State Correctional Facility  Overview ?️ ? This course will prepare students to write basic software and web pages, and it will introduce a full foundation of computer science and design coding concepts that can be applied to many kinds of technical…

    Summer 2024
    Prof. Ar Ducao, arlduc [at] nyu.edu
    Tuesdays, 12:15-3:15 PM
    Wallkill State Correctional Facility 

    Overview ?️ ?

    This course will prepare students to write basic software and web pages, and it will introduce a full foundation of computer science and design coding concepts that can be applied to many kinds of technical projects. Students will be exposed to Python, HTML, CSS, and the Unix operating system. This course will take place in the computer lab, so concepts will be demonstrated and discussed through hands-on computer exercises and assignments. Concepts include data types, data structures, syntax, tags, elements, attributes, functions, variables, expressions, inheritance, statements, and version control. 

    Learning Goals ? ⏏️

    1. Learn basic computer science concepts, including data types, non-decimal numeric systems, data structures, input and output, conditions, and iteration.
    2. Work with an IDE (integrated development environment).
    3. Write basic back-end functionality with Python.
    4. Write basic front-end styles with HTML and CSS.
    5. Learn best practices for writing code that other people can read. 

    Schedule ? ?️

    This is an approximate schedule. It is subject to change based on the general work pace of the computers and the students.
    ?️

    For each week, the assignment will be the exercises at the end of the chapters we studied. For example: Week 1’s assignment will be the exercises at the end of Chapter 1 in both the Python book and the HTML/CSS book.

    Starting around Week 5, I’ll reserve the last 20-ish minutes of class for 1-on-1 meetings to check in with each of you!

    1. Introduction and Best Practices (Chapter 1)
      • Python: The Way of the Program
      • HTML/CSS: Structure
      • Other: Python IDLE, Notepad, Explorer. Non-decimal numerical systems (binary and hex), Boolean logic, data types. 
      • Additional assignment: Please write me a letter introducing your past experience with any computer or digital technologies, as well as what you’d like to learn in this class. Thanks!
    2. Introduction Continued (Chapter 2)
      • Python: Variables, Expressions, Statements
      • HTML/CSS: Text
    3. Writing Programs and Building Structure (Chapter 3)
      • Python: Functions
      • HTML/CSS: Lists
    4. Case Studies: Designs (Chapter 4)
      • Python: Case Study: Interface Design
      • HTML/CSS: Links
    5. More Structure (Chapter 5)
      • Python: Conditionals and Recursion
      • HTML/CSS: Images
    6. Input and Output (Chapter 6)
      • Python: Fruitful Functions
      • HTML/CSS: Tables
    7. Looping Forward (Chapter 7)
      • Python: Iteration
      • HTML/CSS: Forms
    8. Strings and Styles (Chapter 8)
      • Python: Strings
      • HTML/CSS: Extra Markup
    9. Case Study and Cascading Styles (Chapter 9)
      • Python: Case Study: Word Play
      • HTML/CSS: Introducing CSS
    10. More Structure and Style (Chapter 10)
      • Python: Lists
      • HTML/CSS: Color
    11. Data Relationships (Chapter 11)
      • Python: Dictionaries
      • HTML/CSS: Text
    12. Wrap Up (Chapter 12)
      • Python: Tuples and Beyond
      • HTML/CSS: Boxes and Beyond

    Course Books ?️ ⌨️

    Grading ?️ ?

    Grades will be based on weekly programming assignments in the course textbooks, which can be started in class. Grades are calculated as follows:

    • 30% Structure: Are all the parts of the program set up?
    • 30% Implementation:  Are all the parts of the program completed?
    • 20% Style: Have you thoughtfully used comments, variable naming, and function naming so as to help make the code understandable? Is your code organized and well indented? Is your code authored by you?
    • 20% Function: Does the program run on the computer properly? NOTE: This part can take the longest, so for the short assignments in this class, I recommend that you draft out the structure, basic implementation, and style first.

    Extra credit can be earned in a few different ways:

    1. Participate extensively in class discussions by sharing an answer or informed, respectful opinion. 
    2. Help another student with their assignments. If you write (in your assignment) you helped them that week and they verify it in writing, you’ll receive a few extra credit points for that week.
      • If someone helps you, please give them credit by writing an acknowledgment in your assignment submission!
    3. Work ahead in the Python text book. If all goes smoothly with the computer lab, we will probably reach Chapter 12 in class, so completing Chapters 13 and beyond will count as extra credit.
    4. Creative modifications to the Free Python Games modules installed on some computers. If you’re interested in this, please discuss with me in advance!

    Helpful Notes As You Begin: How to Make Your Code Readable, Not Just Functional!

    BASED ON GOOGLE STYLE GUIDES

    ?️

    Optimize for the reader, not the writer
    Codebases often have extended lifetimes and more time is spent reading the code than writing it. Choose to optimize for the experience of the average software engineer reading, maintaining, and debugging code rather than the ease of writing said code. For example, when something surprising or unusual is happening in a snippet of code, leaving textual hints for the reader is valuable.

    • PROGRAM STYLE
      • Import all external packages at the beginning of your program, just after any module comments and docstrings and before module globals and constants. 
      • Indentations: Be consistent in your indentations. Python IDLE should auto-format your code, but I recommend indenting your code blocks with 4 spaces or 1 tab. Never use tabs or mix tabs and spaces, because this will cause an error when you run your code.
      • Maximum line length should generally be 80 characters. Exceptions:
        • Long import statements.
        • URLs, pathnames, or long flags in comments.
      • Generally place only one statement (conditionals and iterations) per line. However, you may put the result of a test on the same line as the test only if the entire statement fits on one line. 
      • Functions: Try to keep them short. Long functions are sometimes appropriate, so no hard limit is placed on function length. If a function exceeds about 40 lines, think about whether it can be broken up without harming the structure of the program.
    • NAMING STYLE
      • Function names, variable names, and file names should be descriptive; avoid abbreviation. In particular, do not use abbreviations that are ambiguous or unfamiliar to readers outside your project, and do not abbreviate by deleting letters within a word.
      • Always use a .py filename extension. Never use dashes or hyphens.
      • Do not use single character names except for counters or iterators.
      • Guidelines derived from Google’s Python Recommendations:
    TypeStyle
    Functionslower_with_under()
    Global ConstantsCAPS_WITH_UNDER
    Global Variableslower_with_under
    Local Variableslower_with_under
    • COMMENTING STYLE
      • Add an explanatory comment above every conditional and iterative statement. Example:
        # Iterate through each person in class
        for y in our_cs_class
      • Add short inline comments to help explain potential surprises. Example:
        print(eggs + chocolate + plantain_chips) #not printing cheese yet

    Thanks for taking this class!
    ?️ ? ? ⏏️ ? ?️ ?️ ⌨️


    + ,
  • Ideal Scenario We’re able to install new software in the lab during the spring, then we’ll be ready for CS in the summer. New software: New Books: Bonus: Blender “Donut” Tutorial Videos Less Ideal Scenario We’re not able to install new software. In this case, we would go with the…

    Ideal Scenario

    We’re able to install new software in the lab during the spring, then we’ll be ready for CS in the summer.

    New software:

    New Books:

    Bonus: Blender “Donut” Tutorial Videos

    • A series of thirteen short tutorials for complete Blender beginners, culminating in an animated pile of donuts. Learning animation is oriented towards video tutorials these days, so if the students could access this donut tutorial (which apparently is the #1 beginning Blender tutorial), it could help their learning!

    Less Ideal Scenario

    We’re not able to install new software. In this case, we would go with the previous books:

    If we can’t install new software but we ARE able to copy software between computers at PEP, this would help. The worst case scenario is that some of the computers have Python and Python games, while some don’t. In this case, students would have to work in groups and share computers all semester.

    +
  • Computer Science Students worked with the following in previous semesters of PEP Comp Sci: 3D Animation Recommended free software: Blender, which does not require web connectivity to use. Blender is very popular with young animators today. Some (all?) PEP lab computers already have Microsoft 3D Viewer, but this software can…

    Computer Science

    Students worked with the following in previous semesters of PEP Comp Sci:

    • Python + IDLE
      • IDLE is Python’s Integrated Development and Learning Environment.
      • IMPORTANT: Python 2 and Python 3 are VERY different. The same version of Python should be installed in the entire lab. (We installed Python 2 in the PEP lab back in 2019, but Python 2 is increasingly deprecated.)
    • Free Textbook: Think Python
    • Free Python Games (download Zip file here)
      • Students can learn Python by modifying the code for these free, simple games.

    3D Animation

    Recommended free software: Blender, which does not require web connectivity to use. Blender is very popular with young animators today.

    Some (all?) PEP lab computers already have Microsoft 3D Viewer, but this software can only be used to view 3D models. It can’t be used to make models or animation.

    + ,
  • There is no excerpt because this is a protected post.

    This content is password protected. To view it please enter your password below:

    + ,
  • Announcements More extra credit opportunities around NYU Agenda Research Paper Notes Intersectionality Assignment Due December 5: Writing Center summary due at the bottom of your Google Doc. In two or three paragraphs, please include Due December 7: Peer Review 2

    Announcements

    • Now in D&T menu: schedule for rest of semester
    • Reminder: Peer Review 1 is due today. Four people still need to send their reviewed document.
    • On Shooting at Club Q in Colorado Springs and Processing Space
      • Wed. Nov 23 at 12:00 p.m. ET
      • For the NYU community—OGI is hosting a processing space with the Center for Global Spiritual Life and Division of Student Affairs to be in community with one another and share reflections on how this attack is impacting us. (Virtual) Read Full Statement

    More extra credit opportunities around NYU

    • Book talk: Disabilities of the Color Line
      • Thurs. Dec 1 at 4:00 p.m. ET
      • The Center for Disability Studies is hosting a reading of the book Disabilities of the Color Line: Redressing Antiblackness from Slavery to the Present (NYU Press, 2022)(Virtual) More Info & RSVP
    • NYU Stolen and Found Poetry Contest
      • Deadline: Sat. Dec 10 at 11:59 p.m. ET
      • All undergrad students are invited to vocalize and reflect on the contemporary effects of colonialism today. Up to $600 in awards. More Info & Apply

    Agenda

    Research Paper Notes

    • Discussion section: unless you have a clear reason to do so, don’t introduce any new sources in this section or subsequent sections.
    • Peer Review 1 Confirmations
    • Peer Review 2 Partners
    • Reminder: The class book list has resources you can use. See the syllabus.

    Intersectionality

    Assignment

    Due December 5: Writing Center summary due at the bottom of your Google Doc. In two or three paragraphs, please include

    • The name of the WC staff you met, and the date of your meeting.
    • The main suggestions from the WC staff.
    • Any additional notes or thoughts that you took away from your session.

    Due December 7: Peer Review 2

    • At least 20 written comments are required.
      • When you’re reviewing your peer’s paper, please edit in or leave comments.
      • After you write the 20 comments, you can earn extra credit by making bold/italic/underline edits (in SUGGESTION MODE) using the code I used (cultural/hyperbole/research issues). 
      • Please focus on Research Competencies in your review, using
      • However, if any cultural competency issues stand out to you, please do highlight these in your comments.
      • When you download and send your Peer Review 2, please add your name to the end of the document name. For example: “D&T Doc – Parker,Peter – reviewed by Miles Morales”
    +
  • Announcements FINAL IN-PERSON SESSIONS: Nov 30 and Dec 14 Agenda Assignment Reminder to use your Zoom profile pic on Monday (we have another guest speaker). Thanks! Due next Monday, November 21: Peer Review 1. 

    Announcements

    FINAL IN-PERSON SESSIONS: Nov 30 and Dec 14

    Agenda

    Assignment

    Reminder to use your Zoom profile pic on Monday (we have another guest speaker). Thanks!

    Due next Monday, November 21: Peer Review 1. 

    • At least 20 written comments are required.
      • When you’re reviewing your peer’s paper, please edit in or leave comments.
      • After you write the 20 comments, you can earn extra credit by making bold/italic/underline edits (in SUGGESTION MODE) using the code I used (cultural/hyperbole/research issues). 
    • Please focus on Cultural Competencies in your review. Use the Cultural Competency Guide section of the Project Resources post to guide your review. Specifically, use:
    • IMPORTANT: When you’ve finished your review, download your partner’s Google Doc as a Word file, then send me the Word file. You must do this to earn credit for Peer Review 1.
    • PLEASE don’t resolve any of your peer reviewer’s comments, or accept/reject any of their suggestions, until they’ve sent me the Word file of their comments.
    +
  • There is no excerpt because this is a protected post.

    This content is password protected. To view it please enter your password below:

    + ,