Archive Note

My First Steps into Data Science

This is one of the earliest notes in the writing archive. It captures how the learning journey started before later project work became more outcome-focused.

A short reflection on curiosity, inconsistency, and the habits that made technical learning sustainable.

Data science started as simple curiosity for me. I wanted to understand how numbers could explain behavior, support decisions, and reveal patterns that are hard to notice in raw tables.

The first weeks were not smooth. I had to learn programming basics, statistical thinking, and dataset handling at the same time. Every new topic introduced unfamiliar terms, and it was easy to feel overloaded.

What helped most at the beginning

  • I focused on one small concept each day instead of trying to cover everything in one session.
  • I practiced with tiny datasets so debugging stayed manageable.
  • I wrote simple notes after each session to preserve what worked and what failed.

First practical mindset shift

I stopped asking, "Which tool is best?" and started asking, "What decision should this analysis support?" That one question made projects clearer and reduced wasted effort.

Progress became faster once learning moved from topic collection to problem solving.

Where this note sits today

This post remains in archive mode because newer case studies show stronger execution depth. Still, it records the foundation: consistency beats intensity, and practical questions beat abstract goals.

Understanding Python Loops

Beginner-friendly loop patterns with practical examples.

Read post

The Importance of Data Visualization

Why visuals help explain decisions and model outcomes.

Read post

One Link to Rule Them All

Automation case study using Google Sheets and Apps Script.

Read post