Zinia-Store

Day 30 of 30: 🎊🎊👏👏😃💐
What Changed? The Finish Line is Just the Start. 🏁

About thirty something days ago, I began this challenge with a background in fashion design, a curiosity about tech, and a healthy dose of imposter syndrome. I saw the world of clothes and the world of code as two very separate continents.
Today, as I cross the finish line, those continents have collided.

Looking back, the technical growth is undeniable. Concepts that felt alien four weeks ago, like wrangling messy CSVs in Pandas, debugging complex SQL joins, or wrapping my head around the linear algebra of PCA, are now familiar territory. I’ve moved from memorizing syntax to actually thinking in data structures.

But the most profound shift wasn't in my Python skills, but in my mindset.

I’ve stopped viewing data as abstract numbers on a screen. I now see data physically. I see it like a physicist sees forces, a way to model reality, test hypotheses, and predict outcomes. When I look at a fashion collection now, I don't just see aesthetics, but SKU velocities, supply chain bottlenecks, and optimization opportunities.

My capstone project, using real-world e-commerce data to forecast demand in the Nigerian market, solidified this. Seeing the data proved that 80% of revenue often comes from just 20% of products was a revelation. It proved that the sustainability crisis in African fashion isn't just an environmental problem; it's a data problem waiting to be solved.

So, what’s next?
This 30-day mark isn't the end, it’s the launchpad for a full career pivot. I am aggressively pursuing roles that sit at the intersection of fashion, technology, and sustainability. I am ready to move beyond intuition and use rigorous data analysis to build smarter, less wasteful systems for our local industries.

A massive thank you to everyone who followed along, offered encouragement, and kept me accountable. Sharing this journey publicly was scary, but it was also the best motivator I could have asked for.

Here’s to the next chapter. The data journey continues. 🚀🌍💙

WomenInTech python SQL GrowthMindset DataAnalysis NewBeginnings

Day 28 of 30: We are in the home stretch of the 30-day data challenge! 🏁

Everything I’ve wrestled with this month, from leaning messy CSVs to finally understanding SQL joins, is culminating right here. For my final capstone project, I’m bringing together my passion for sustainability and my new data skills to tackle a critical real-world issue.

Here is a sneak peek at what I’m building:

Overproduction in the fashion industry is a major environmental crisis, especially here in Nigeria, where textile waste is rampant. Local brands often rely on intuition rather than evidence when planning inventory.

My goal is to build a demand forecasting model that predicts sales volume for specific clothing categories based on historical data and seasonality, helping brands produce only what they can sell.

I’m diving deep into a robust, real-world E-commerce Fashion Transactional Dataset. It may contain over one or two years of sales records, including timestamps, SKU details (colour, size, category), pricing changes, and customer location data.

It’s messy, it’s complex, and it’s exactly the kind of challenge I’m ready for. It is time to prove that data can drive sustainability.

Stay tuned for the results! 🚀

Day 26 of 30: Reflections 😔

I know you're probably wondering where today's series is, wellllll, I'm blank.

Today, I do not have anything to say aside from the fact that I'm exhausted and burnt-out. Today is to pause and reflect. Most times I've been tired, but I still show up by posting. I recollect a few nights dozing off more than 10 times while typing but I still kept on.

People say putting things out will make one gain visibility.

The question I ask myself daily is
1. Who sent me? (read in pidgin)
2. Is it really worth all the stress coupled with my other engagements?
3. What next after Day 30?

Because if I'm to be sincere with myself, I still don't know anything.
Meanwhile, here's a little summary of my year review.💐

Day 25 of 30: Approaching data like a physicist.

Many analysts dive straight into a dataset, fishing for correlations and retroactively creating a story around whatever they find. I take the opposite approach. I treat data analysis exactly like a physics experiment.

In a lab, you don't randomly smash particles together just to "see what happens". You start with a theory and design an experiment specifically to test it. I apply this same scientific method to business data.

Before writing a single line of code, I define the problem and formulate a clear, falsifiable hypothesis. For example: "I hypothesize that the Q3 drop in conversion rate was driven specifically by mobile users encountering the new checkout UI."

Only then do I touch the data. The dataset becomes my experimental apparatus. I extract precisely the metrics needed to support or refute that specific statement, at my level, nothing more, nothing less.

I believe this rigorous, hypothesis-first methodology prevents "data dredging" finding statistically significant but meaningless patterns in the noise. It ensures that the final analysis isn't just a collection of interesting charts, but a definitive answer to a critical business question, grounded in evidence.

Day 23 of 30: The importance of "Clean Inputs". The Universal Truth of GIGO 🗑️➡️📉

Coming from an electronics background, the concept of "Garbage In, Garbage Out" (GIGO) made instant sense to me. It’s just a new name for an old lab nightmare.😅

Remember setting up a complex circuit experiment? You have your theories and your formulas ready. But if your voltmeter is uncalibrated, your oscilloscope probe is damaged, or your temperature sensor is just noisy, it doesn't matter how elegant your physics equations are.😥

If the input measurements are flawed, your final calculation of resistance, capacitance, or energy will be wrong. You cannot "math" your way out of bad sensor data.

Data science is exactly the same. Your machine learning model is the formula. The dataset is the sensor reading. If you feed a sophisticated algorithm data that is full of duplicates, missing values, or biased information (garbage in), the model will confidently spit out nonsense (garbage out).

Just as a physicist spends time calibrating their instruments before an experiment, a data scientist must spend time cleaning and validating their data before modeling. No amount of algorithmic horsepower can fix broken inputs.

Day 22 of 30:

At first glance, physics vectors and data science vectors seem unrelated. In physics, a vector is a tangible arrow defining magnitude and direction, like wind blowing 20mph East. In data science, it’s an abstract list of numbers representing features like a product defined by [price, weight, rating].

The bridge connecting them is coordinate geometry.

A physics vector representing movement in 2D space can be written as coordinates (x,y). This pair of numbers is literally a data vector of length two.

The fundamental similarity is that both represent a position in space relative to an origin. Physics usually limits this to tangible 2D or 3D space. Data science simply expands this concept into high-dimensional "feature space."

A product vector of [10, 2kg, 4.5 stars] is a single point plotted in a 3D abstract space where the axes are price, weight, and rating. Whether it's physical movement or abstract attributes, a vector is ultimately just an ordered list of coordinates defining a specific location in a defined space.

Day 20 of 30: 💐

The fashion industry's waste crisis is devastating, and Africa is tragically becoming the world's landfill for fast fashion leftovers. Here in Nigeria, we see the reality of overproduction every day, mountains of unsold clothing that benefit no one. This isn't just an environmental disaster; it's economic foolishness. Too many brands are guessing instead of knowing.

We must stop producing blindly! Data analysis is the urgent revolution we need. It is the key to unlocking precise inventory needs and stopping waste before it starts. By leveraging predictive analytics, African brands can move beyond outdated intuition and accurately forecast demand based on our unique, rapidly shifting local market nuances.

Imagine the power of producing exactly what the market in Lagos, Accra, or Nairobi wants right now! No more, no less. This isn't just about sustainability, it’s about survival and profitability for local businesses. Data-driven inventory means less waste choking our environment and more capital for our designers to innovate. Let's use the power of numbers to clean up this mess and build a smarter, resilient African fashion future.

Day 19 of 30:

For most fashion analysts, this is believed to be one of their favorite applications of data science in fashion because it turns raw visual chaos into actionable design assets. 🎨➡️📊

Imagine a folder full of hundreds of runway images from Paris Fashion Week. Trying to manually extract a cohesive color palette from that is slow and subjective.

From Pixels to Palettes, to a computer, an image isn't a picture of a dress. It's just a massive grid of numbers representing RGB (Red, Green, Blue) values.
First, we use a library like OpenCV to load the image. It reads the file and converts it into a massive multidimensional array (think of a giant 3D spreadsheet) of pixel data.

We can't just average all the pixels, or we'd end up with a muddy gray. We need to find groups of similar colors.

We throw all those millions of pixel values into a machine learning algorithm called K-Means Clustering (part of the 'scikit-learn' library). You tell K-Means, "Find me the 5 most distinct color groupings in this mess." It expertly sorts pixels into clusters and calculates the very center RGB value of each cluster.
These center values are your dominant colors.

Now we have the exact numerical RGB values for our palette, but numbers aren't inspiring to look at. This is where Matplotlib shines.

We don't just use Matplotlib for line graphs. We can use it to visualize colors.
We take those 5 RGB values identified by K-Means, we feed them into Matplotlib to create a simple bar chart or pie chart. Instead of plotting data points, we tell Matplotlib to color each section of the chart using those specific RGB values.

The Result is an instant, mathematically accurate color palette derived directly from the runway images. You can process entire seasons in minutes, identifying shifts from "Millennial Pink" to "Gen Z Green" with hard data.

It’s the perfect blend of machine learning muscle and creative visualization. 🤖✨