The Journey to Data Science from Scratch
Introduction
It’s a rare opportunity to be part of a well-rounded machine learning and data analysis team at the company, complete with sufficient resources and a solid pipeline. I’m taking this chance to learn about data science, and if there’s anything I don’t understand, I can directly ask my colleagues. The scope of data science is vast, and there isn’t a clear direction at the moment, so I’m just going to learn and see what sparks come from this journey—let the side hustle begin!
Plan
-
Revisit the pieces I missed from my university statistics course (2 weeks)
- Distributions and various testing methods
- R: Learning while reviewing
-
Review linear algebra (3 weeks)
- I’ve completely forgotten everything
-
Review Andrew Ng’s machine learning course (1 week)
- When I took this course, it was using Octaves, but the concepts should be applicable
-
Complete the Deep Learning Specialization on Coursera (6 weeks)
-
Finish reading the data science books I purchased earlier (3 weeks)
-
Follow the curriculum at fast.ai while diving into research papers
- I previously completed courses 1 to 4 but forgot everything.
-
Data engineering
- Airflow
- Kafka
- I particularly want to learn these two
This plan should fill about 100 days, and I might look for some additional data analysis-related courses since it seems like there’s a heavy focus on machine learning and deep learning. In any case, I’m documenting everything I think of here to avoid forgetting.
Goals
I primarily want to explore the fun aspects of integrating front-end development with data science, such as working with ml.js or tensorflow.js, which sounds really exciting.
Additionally, I have certain ideas that require the support of data science, so I want to take advantage of this time to bolster my knowledge in that area. Previously, my notes were scattered everywhere, and now I can hardly find them, plus I’ve forgotten a lot. This time, I’ll make sure to document everything thoroughly on my blog.
Related Posts
- When Measurement Becomes the Goal: From Window Tax to PR Counts I once wrote a small tool to count how many PRs I had contributed in a quarter, how many reviews I had left, and how many tickets I had closed, hoping to use the numbers to prove my output to my manager. My manager simply said performance is not judged by output alone. Only years later did I understand—when measurement becomes the goal, it is no longer a good measure. From Britain’s window tax and the Hanoi rat bounty to evaluating developers by PR count today, the mechanism is exactly the same.
- Using Cloudflare Images for Image Storage and Transformation Putting an image on a web page is the easiest thing in frontend. But doing it properly — resizing, generating every format, holding up under traffic — turns into a whole solution of its own. I ended up handing all of it to Cloudflare Images and keeping just one original.
- Stop Using Access Keys Already Access Keys are an easily overlooked security risk on AWS. Use OIDC with IAM Roles so GitHub Actions can securely access AWS resources without any secrets.
- Database Primary Keys: AUTO_INCREMENT, UUID, and UUIDv7 Backend developers often have to decide on a primary key: auto increment or UUID? What about collisions? How much faster is UUIDv7 compared with created_at + index? After benchmarking 20 million rows and looking at the design trade-offs, this post gives you the answer.