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.

There's something I want to make clear to every single person in this community. This space will never be about charging you to belong. I didn't build this for profit — I built it because I know what it feels like to need guidance, support, and real people around you who are trying to grow. This is a place where we learn, push forward, and hold each other accountable… together. And with anything real, anything that actually matters, there will always be people who question it, doubt it, or try to tear it down. That's normal. Every strong movement, every meaningful community, and every person doing something different faces resistance. Not because it's failing — but because it's doing something right. So if you ever see negativity around what we're building here, understand this: we stay focused, we stay grounded, and we keep moving forward. This community is built on value, not transactions. On growth, not shortcuts. On people, not profit. I've invested my own time, energy, and money to keep this space alive — because I believe in what it can become for all of us. And as long as I'm leading this, you will always have a place here. No fees. No catch. Just growth. Let's keep building. This is my promise to keep this free and accessible to any Maestros willing to join and add to it.