Notes from the moments between clicks.

While sketching a small browser-based prototype, I caught myself treating privacy as a settings screen I could add near the end. I restarted the plan by listing what data the idea truly needed, what could stay on the device, and what should never be collected.

The change made the project simpler. Privacy by design is not only about preventing harm; it can also force clearer decisions about what a product is actually for.

Related engineering work

• CAN Bus Anomaly Lab

My first threat-modeling exercise felt like a list of things that could go wrong. It became more useful when I stopped thinking only about attackers and started asking who could be confused, excluded, pressured, or exposed by an ordinary design decision.

Security thinking gets stronger when it includes the experience of the person using the system. Anticipating misuse and anticipating friction are both ways of taking people seriously.

Related engineering work

• Microgrid Controller Simulation
• CAN Bus Anomaly Lab

A repository can technically work while still making the next person search through unclear names, generated files, and missing context. I treated a cleanup session as communication work: organize the structure, explain the purpose, and make the useful path obvious.

Good documentation respects other people's time. A clear project also makes it easier for me to notice what I actually understand and what I have only been carrying forward.

Related engineering work

• Power Quality Lab
• Microgrid Controller Simulation

I reviewed a form using only a keyboard and quickly found places where the visual design looked finished but the interaction did not. Labels, focus order, contrast, and motion preferences determine who can actually participate.

Accessibility is not an optional polish layer. If digital citizenship is about contributing to spaces responsibly, access has to be part of the definition from the beginning.

A polished video used charts and confident narration to make its conclusion feel settled. I followed the sources in the description and found that one link did not support the number shown, while another was several years older than the narration implied.

Production quality can make a claim feel verified before any verification happens. I now treat confidence, editing, and visual polish as presentation signals—not evidence signals.

As I look ahead to starting electrical engineering in Canada, I wanted to review what I am publicly attaching to my name online. That meant checking bios, old posts, shared profiles, and the tone of the spaces where I participate most.

The goal was not to erase personality, but to make sure my digital footprint reflects the kind of learner and community member I want to be: curious, responsible, and increasingly aware of cybersecurity and digital citizenship.

AI summaries are useful for orientation, but they often compress uncertainty out of a topic. This week I started checking every summary against at least one primary source before I reuse any claim.

That extra step slowed me down slightly, but it improved my confidence and made my notes more accurate. Convenience is only ethical when it still leaves room for responsibility.

Related engineering work

• Trailhead Customer Support API
• Power Quality Lab

I noticed that tired scrolling made me less thoughtful about what I liked, shared, and clicked. I replaced late-night scrolling with a short shutdown checklist and one intentional article or video.

The change helped me separate rest from distraction and made my online time feel more chosen than automatic.

I used to treat privacy setup as a one-time task, but every new app quietly adds fresh decisions. I now check visibility, permissions, contact sync, and notification settings before I start using a service regularly.

That routine turns privacy from a vague value into a repeatable behavior.

Short messages travel fast, and tone gets flattened easily. I started pausing before sending corrections or reminders, especially in group chats where public friction can grow quickly.

Being concise does not require being sharp. Clear and respectful replies reduce noise and help people stay engaged.

I spent too much time tuning tools that were supposed to save time. The problem was not the apps themselves, but the way I kept optimizing instead of doing the work.

I now ask whether a tool improves clarity, safety, or output quality. If it mainly adds novelty, I treat it as optional.

A shared study document was growing quickly, but sources were inconsistent. I added a simple citation pattern and a note explaining why link quality matters when notes get reused.

The fix was small, but it made the document more trustworthy and easier for everyone to build on.

A story moved quickly through class chats this week, and my first instinct was to repeat it before I had checked the source. I stopped, looked for the original report, and realized the summary being shared had left out important context.

That moment reminded me that media literacy is often about slowing down when everyone else is speeding up. Accuracy is part of respect.

I used to think about passwords mostly when a site forced me to update one. This month I started treating password checks as maintenance: review reused passwords, confirm multi-factor authentication, and update recovery methods.

Cybersecurity feels more manageable when I break it into repeated habits instead of waiting for a problem to force a reaction.

After winter break I noticed I was reaching for my phone more often than I wanted, mostly because notifications kept interrupting study time. I reviewed which apps actually deserve immediate attention and turned most of the rest into scheduled check-ins.

The change felt small, but it gave me more control over attention and made my online time feel intentional again.

A few of us kept running into the same digital tool issues, and I realized I was typing the same answers over and over. I turned those answers into a short shared guide with steps, screenshots, and a note on safe account setup.

Helping once is useful, but documenting a solution can help more people with less friction.

I experimented with using AI to organize study questions and explain unfamiliar terms, but I kept noticing how easy it was to let the tool become the voice of the work. That is useful for speed, but risky for learning.

I set a simple rule for myself: AI can help me start, compare, or check, but it should not replace the part where I explain the idea in my own words.

Related engineering work

• Trailhead Customer Support API

I realized several apps had access to my location even though they did not need it all the time. It happened gradually because tapping allow was easier than thinking through the tradeoff in the moment.

This reflection pushed me to switch more apps to while-using or never. Privacy is often decided in the tiny moments when convenience asks for less thought.

I noticed how easy it is to repost something because it sounds right or matches the mood of the moment. This week I made myself read beyond the caption before sharing anything that sounded factual or urgent.

That small pause changed how I think about participation online. Sharing is not neutral when other people may trust the signal I send.

I wanted a way to think more seriously about the kind of person I am online, not just the things I post. Digital citizenship felt like the right starting point because it connects behavior, safety, community, and reflection.

Beginning this log made the topic feel practical. Instead of treating good online behavior as a vague ideal, I could start recording choices, patterns, and improvements over time.