marissa codes marissa codes marissa codes marissa codes marissa codes marissa codes

πŸ“ My Blog πŸ“

Welcome to my blog! Here I share my thoughts on coding, technology, and life. ✨

πŸŽ‰ Welcome to 2026

πŸ“… January 2026

2025 was terrible. I got sick, spent time in the ICU, passed out during daily standup, went to countless doctor appointments, had delayed disability appointments, got scammed by a psychic for $1,285 (cultural relevance to Saneria here), and generally failed backwards not forward. And all of this could have been avoidedβ€”even the health struggles IF I had done quarterly goals.

I stumbled through 2025 with modest achievements: acceptance and a scholarship to Berkeley, started a company with my friend Design for Users due to necessity of crippling medical bills, but still I believe a lot of my issues could have been avoided had I PLANNED MY YEAR and my goals.

It was easy to set goals in college: summer internship, fulltime job, graduate. These goals were often immediate, actionable, and cyclical. However postgradβ€”yes I did get post grad depressionβ€”but my northern star / purpose felt murky and unknown. However, 2026 I am taking control.

What I Did to Prepare for 2026:

I did a 2025 review: What went well, what failed, what brought joy. I did the printout from the video linked below: Spotify Episode

I cleaned: Cleanliness is next to Godliness and I needed my space to be clean for maximum productivity.

Started a notetaking system: My brain thrives on patterns so I chose Obsidian to take notes on everything I am learning and doing to accelerate in 2026.

Set my reading goals: In 2025 I read 5 books. I want to double it to 10 in 2026.

Deleted all social media except X: (self explanatory)

Set work goals: For engineering as well as math to review for my masters program.

Welcome to 2026 ✨

πŸš€ "We had to Google it to make sure it actually existed" - How I Turned Doubt into Success

πŸ“… August 21, 2025

"We have never heard of your school, we had to google it to make sure it actually existed." Those words are what have sent most people running to the hills or wanting to astral project out of their chair during an interview, but for me, it was a challenge.

During recruitment season many bright students are often faced with their own inadequacies, however, these faults can be rebranded as strengths, not weaknesses. So how did I get the job? As Nico Avocado says I was two steps ahead.

1. I was scrappy

Before applying to the internship, I had extensive internship experience going back to high school. The first tech startup I worked at was in 2017, a 3-D printing company known as Xometry, where I was a digital marketerβ€”a gig I got from cold-calling startups in my area.

2. My experiences were unique

In addition to typical software engineering internships, I had been a teacher with the well-respected AmeriCorps program. This aligned with one of the core values of the firm, as they were involved with local educational volunteer programs in the area.

3. I did not come to the interview empty-handed

To demonstrate my initiative and genuine interest in the firm, I created an investment thesis based on my personal interests and tailored it to align with the scope of the firm's focus areas. This comprehensive and well-researched thesis not only highlighted my analytical skills and understanding of the industry but also provided a tangible example of how I could contribute to the firm. I presented this thesis during my final interview, which allowed me to showcase my knowledge, creativity, and dedication to making a meaningful impact within the organization.

4. I practiced

Before my interview, I utilized online resources containing both behavioral and technical interview questions and did mock interviews with friends.

So, don't doubt yourself your weakness just might be your greatest strength ✨

πŸš€ Four Things I Have Learned from Working at a Startup

πŸ“… August 18, 2025 | Previously published on my Medium in 2022

I am a rising junior in college and a computer science major with a passion for science β€” especially computer science. So when I was able to apply what I had been learning at school as an engineer for a startup (not just any startup, but one that rebuilds the internet for you), I said YES. Throughout my time working as a software engineer at Sonr, I have learned things I would not have in the traditional college setting. Here are the four main lessons I have learned:

1. School is a starting point β€” it is up to you to finish the rest

My computer science coursework mainly focused on object-oriented programming, and the fact that I have taken applicable math and science courses has aided in the comprehension of my work tasks. However, working in the field has gifted me with irreplaceable knowledge. For example, in the classroom, we are not working in teams, so using Git Flow did not apply to the scope of our coursework. While working at Sonr, I have been able to learn and apply Git Flow. Git Flow is one of the most common tools used by engineering companies; it describes the project's release cycle and adds specific roles to different branches.

2. You don't learn to swim by reading a book on how to swim

During the school year, one of my greatest resources was my textbook; it was essential to read before lectures. However, to be a good programmer, you don't just read or solve school problems; you build. I had two goals this year: get a certification and add more to my GitHub because my GitHub was actually barren. I can proudly say I have achieved both goals. I received my Chainalysis Cryptocurrency certification, and my GitHub has new additions from work and personal projects. I used to fear personal projects, but with the coaching of my coworkers, I have begun to make them. Currently, I am working on personal projects that intertwine my love of art and science, such as a Y2K-inspired GitHub-hosted website and a pink tic-tac-toe game.

3. Feel stupid every day

Before my job, I had reached a plateau. I was doing well in school, but I knew there were things I needed to learn because "the wise man knows what he does not know." Working at a startup gave me the ability to learn what I didn't know and learn things ahead of when I would be in school. Therefore, I am confident this upcoming fall semester will be less taxing than previous semesters.

4. Read about everything

In our office, there are a lot of books. Books about math, science, philosophy, and more β€” you name it. One thing I've noticed from reading and absorbing a multitude of literature is that it makes you a better thinker and person. By exposing yourself to a variety of literature, you open your mind to diverse thoughts and perspectives and start to see the world differently.

Working at Sonr has made me a better learner, thinker, developer, and person. It has shown me how to be resilient, work harder, and adapt to change. This is your sign to go work at a startup. ✨

πŸ‘” The Manager: Meeting Your Workplace Fate (and How to Prepare)

πŸ“… August 15, 2025

The manager, also known as the person who decides your workplace fate (just kidding, but only a little). Good managers are critical in one's first job out of undergrad. They play a pivotal role in the trajectory of one's career growth and professional development.

I met my manager on Superday when he interviewed me. Ultimately, my Superday was successful, and I got hired for the jobβ€”yay! However, being hired is one thing; doing well on the job is another. I believe in the power of preparation because, as Benjamin Franklin said, "By failing to prepare, you are preparing to fail."

Therefore, I decided to meet with my manager months before my start date to ensure I had knowledge of the tech stack and more insight into the company culture. I prepared for the meeting by making a list of questions reviewed by my career coach. Each question was divided into three categories: tech stack, company culture, and engineering team culture.

πŸ“‹ My Question List:

  1. What are the expectations within the first 30 days of the job?
  2. What is your culture around problem-solving?
  3. When will I have a chance to meet the team?
  4. What project will I be joining what are the expectations - goals -and outcomes?
  5. What do you like about the culture, what would you change?
  6. How can I be an asset to the culture?
  7. Will we be meeting regular basis?
  8. Who will I be asking questions in the beginning?
  9. What does Day 1 look like/ what are the logistics?
  10. What technical things I can learn now to prepare?

I highly encourage every new SWE to set up a meeting with their manager early to begin building a strong relationship. ✨

πŸ€– AI Ethics in Software Development

πŸ“… August 12, 2025

As AI becomes more integrated into our daily lives, it's crucial to consider the ethical implications of the software we build. Here are my thoughts on responsible AI development...

Read more β†’

πŸ“š My Reading Challenge: 50 Books This Year

πŸ“… August 15, 2025

I've set a goal to read 50 books this year! Here's my current progress and some of my favorite reads so far. Reading has been such a great way to learn and grow...

Read more β†’

🏠 Miniature House Design: A Creative Outlet

πŸ“… August 12, 2025

When I'm not coding, I love working on miniature house designs. It's a perfect creative outlet that helps me relax and think differently about design and space...

Read more β†’

More blog posts coming soon! 🌸✨