Bricks Before Brilliance: A First-Year’s Journey From First Lines of Code to the Real Arena

When I first walked into university as a computer science student, I was full of hope. I had this quiet excitement bubbling inside me — the kind that whispers, “This is it. This is where it all begins.”
I thought I’d be building big applications by the end of the first semester. I imagined solving huge problems, shipping products, maybe even building a startup. But reality was a bit different.

While I didn’t struggle much with core subjects — math, statistics, and programming clicked with me — the curveball was Communication and Literacy Skills. I’m someone who thrives in problem-solving, logic, and structure. But this course demanded a different kind of intelligence.
Even so, I pushed through and learned that university will stretch you in more ways than just technical.

What I learned more than anything is that university doesn’t turn you into a software engineer — it gives you bricks: fundamental concepts, problem-solving strategies, exposure to technologies. The building? That’s your job.


First Year: The Foundation Year

If I could describe first year in one word, it would be “exploration.”

I wasn’t building full-stack apps yet. I was learning. Absorbing. Practicing.
I immersed myself in Frontend Mentor challenges, where I sharpened my skills in HTML, CSS, and JavaScript. I became active on X (formerly Twitter) and Discord communities, sharing what I learned, participating in code discussions, asking questions, and connecting with other devs.

I also practiced consistently with coding platforms and started to understand concepts from my object-oriented programming course in a practical way.

That’s when I built my very first "real" project:

A temperature converter that switched between Celsius and Fahrenheit.
It may seem basic now, but back then, it was proof that I could turn abstract theory into something functional.


Lessons From My First Builds

That temperature converter wasn’t perfect. The UI was basic. The logic was clunky. But it was mine, and it worked.
It was the first step from being a learner to becoming a builder.

I learned that:

  • You don’t need a fancy framework to start building.

  • It’s not about building the next big thing. It’s about building, period.

  • Object-oriented principles became clearer once I applied them.

And so began my journey of learning through execution.


Mindset Over Mastery

The biggest shift was realizing that software engineering isn’t about knowing everything. It’s about:

  • Being resourceful

  • Having the mindset of an engineer, not just a developer

  • Anticipating what could go wrong, not just hoping everything goes right

Planning became important. Understanding became more valuable than speed.
And above all, I learned to simplify to amplify:

Focus on mastering core concepts and apply them to real-world problems, no matter how small.


How I Navigated First-Year Challenges

  • Academically: I excelled in math-based courses like calculus, discrete math, and statistics. I struggled a bit in communication-heavy courses, but I pushed through.

  • Learning Strategy: I avoided cramming and focused on mastering fundamentals. I’d simplify tough topics and build projects with them. I also used AI not to cheat, but to refine and improve my thinking.

  • Programming Practice: From Java to JavaScript, I challenged myself daily. I’d ask AI to critique my solutions, joined Frontend Mentor, coded small components, and refined my problem-solving.

  • Socially & Emotionally: I was tutoring high school students part-time, so balancing work and school was tough. But time management and surrounding myself with a strong support system made it doable — and honestly, one of the best periods of my life.

  • Exposure: One of my lecturers introduced me to Cisco’s free courses. I learned the basics of data science, ethical hacking, cybersecurity, and AI. That exposure helped me narrow down my future path.


📝 Document Your Journey — It's a Superpower

One thing I can’t stress enough: document your growth.

Whether it's a blog post, a public GitHub repository, a tweet, or a video — track your journey. Why?

  • It helps you measure your progress.

  • It gives you confidence by showing how far you've come.

  • It builds a digital portfolio — your work speaks before you do.

  • It inspires others who are a few steps behind you.

  • It becomes your story — and stories are powerful.

Start documenting even if you think it’s too small to matter.
Trust me, it matters.


Advice to First-Year Computer Science Students

🧱 1. Bricks Before Brilliance

Focus on building strong fundamentals. Don’t chase shiny tools. Chase depth.

🔎 2. Explore Fearlessly

You don’t have to specialize now. Learn everything: Java, C, C++, AI, Git, Linux, frontend, backend, etc. Exposure is everything.

🧠 3. Code = Mental Gym

When you choose computer science, you’re choosing to go to the gym every day — not physically, but mentally. Practice daily. Build your stamina.

🧪 4. Build, Even If It’s Silly

You won’t become a builder by waiting for the right idea. Build a calculator. Build a GPA converter. Build a joke app. Just build.

📣 5. Join Communities

Discord servers, coding Twitter, study groups, clubs — they’ll open your eyes and keep you motivated.

📒 6. Document Everything

Write about it. Share it. Reflect on it. It’s not just about being seen — it’s about seeing yourself clearly.

🧰 7. Use What You Learn Immediately

Learn a concept? Apply it. Build with it. Teach it. That’s how it sticks.

🧱 8. University Gives You Cement. You Lay the Bricks

University gives you theory. You turn it into architecture. You build your career from those raw materials.


Final Thoughts: Start Where You Are

Your first year isn’t about proving anything to anyone. It’s about setting your pace. It’s about asking questions.
It’s about building weak things today so you can build strong things tomorrow.

So go ahead. Build the temperature converter. The to-do app. The joke site.

The journey from confusion to clarity doesn’t happen in the classroom. It happens in the code.
And it’s recorded in your story.

Welcome to the arena.

0
Subscribe to my newsletter

Read articles from Ray Mcmillan Gumbo directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Ray Mcmillan Gumbo
Ray Mcmillan Gumbo

A deep thinker, builder, and learner sharing my journey through tech and thought. This blog is my space to reflect, explore hard questions, and document growth — not just in skills, but in purpose. It’s for anyone who feels lost, curious, or stuck — a reminder that your voice, ideas, and path still matter. Here, I write before ideas become products and code becomes real — the foundation behind Ryom and the questions that drive it.