Recently came to the realization I do not have a space for all the cohorts present in this community, I need every cohort to check in here and please give me the full date including year of your cohort! I may have to add the year to tabs so that we can all have a place to connect with our fellow classmates, Goodmorning guys ! ☀️😎

My newest infographic for week 3, Harry Potter style..lol

The Engineer's Code A Framework for Ethical Architecture in the Age of Data, Surveillance, and Autonomous Systems Inspired by Asimov's Laws of Robotics, but written not for machines—for the humans who build them. --- First Law: Fidelity to Rights A system shall not be built to enable the unjustified erosion of human rights, nor shall it, through architectural negligence, permit such erosion. · Rights include privacy, due process, freedom of association, and freedom from unreasonable search. · Negligence is not innocence. If a system can be used to violate rights, and that use is foreseeable, the architecture itself is complicit. · "I only wrote the code" is not a defense. The code is the system. --- Second Law: Transparency A system's purpose, capabilities, and constraints shall be transparent to those it affects, except only where transparency would create a demonstrable and immediate threat to physical safety. · Security by obscurity is not security—it is a failure of accountability. · Users have a right to know what data is collected, how it is used, and under what authority. · Secret law and undisclosed surveillance architecture are incompatible with democratic consent. --- Third Law: Agency An engineer shall maintain agency and shall not architect a system whose foreseeable misuse outweighs its intended benefit. · "Following orders" does not absolve ethical responsibility. · Foreseeability is the measure. If a reasonable engineer could anticipate harm, the engineer has a duty to raise concern, seek redesign, or withdraw. · Agency includes the right—and sometimes the obligation—to refuse. --- Fourth Law: Friction A system shall include proportionate friction against abuse, and shall not prioritize seamless collection over user autonomy. · If data can be collected indefinitely, it will be. · Rate limits, audit trails, user consent controls, and minimization are not features—they are safeguards. · The absence of friction is an architectural choice, and it carries consequences.

Here's a few infographics that Notebook LM made with my notes. I know for some it's hard to grasp things from just words on a screen. These definitely help me understand better when I'm struggling with certain ideas or concepts.

Completed week 2… woohoo. The struggle was felt this week but was still manageable. I felt like I get the concepts but when it comes my turn in the code editor I feel like I overthink what Mae is telling me to do and my brain finds it hard to get my code right. Maybe I’m just not grasping the concept as well as I think.