Why I Built Stuff: What My First Python Project Taught Me

December 3, 20245 min read

print("Hello World")

My first "project" was a get-rich-quick scheme. It was the golden age of YouTube Shorts, brainrot (how fitting that it's Oxford Word of the Year for 2024!) content with weird Reddit posts narrated by AI voices. I knew a little bit of Python, I set out to scrape the most upvoted posts in select subreddits, grab a few comments, and merge them with soap-cutting, Minecraft-jumping, and patio-cleaning-with-a-power-washer videos. The goal? Build a faceless YouTube channel, swim in views, and strike it big.

Spoiler alert: I didn’t get rich. But I learned a lot. And for now, that’s enough. Riches can wait. I’ve got more to build, and much more to learn. I can keep telling that to myself...

And so, here we are! Welcome to the first post on berkem.xyz, my little corner of the internet. 🎉

I’ve always believed there’s magic in building things — whether it’s crafting a well-written piece, figuring out a creative solution, or even making resin dice (my latest hobby 🧙‍♂️🎲). The process is messy, thrilling, and, above all, rewarding.

For instance, I often find myself spending hours automating tasks that could be done in minutes. Why? Because building something is more fulfilling than ticking off another task from an endless to-do list. Sure, I could just check my competitors' websites manually, but where’s the fun in that? Instead, I built a mini tool to handle it for me.

This led me down a path where I:

  • Discovered I needed to learn web scraping
  • Started learning BeautifulSoup
  • Ran into anti-scraping measures
  • Found out about Selenium
  • Failed multiple times with Selenium
  • Finally succeeded in collecting HTML files

That was just the beginning. After exploring various NLP packages on GitHub and getting assistance from AI, I spent another 4 hours building a tool that now scrapes competitor websites, analyzes their content, and alerts me to relevant updates about their activities.

Phew.

I'll probably use this tool once every 6 months. What a time "saved"!

You can tell, I’m not an expert.

  1. I don’t write code like a seasoned developer.
  2. I’m not planning to build the next ChatGPT.
  3. And I definitely can’t create a GPU from scratch (if I could, I would try).

What I can do is explore. Try things. Solve small, everyday challenges that make life easier or just a little more fun. And that’s what this blog is all about.

berkem.xyz isn’t just a blog — it’s an experiment.

  • Can I really learn to automate boring stuff? (great book btw)
  • Can I make simple tools that actually help people?
  • Can I push my limits while still having fun?

I think the answer is yes.

Don't Overestimate That Guy 🌟

I remember someone I deeply respect once said, 'Developers often think everyone wants to learn programming, and that they, as a selective few, have managed to succeed. You can start coding in two weeks and if you get exposed to it for at least 4 years, you become a programmer. Try not to overestimate developers.'

I think about this a lot. There has always been a certain information asymmetry between me and those making their living through software development. I've always been a tech-savvy person, comfortable navigating computers and technology. But I had never translated my ideas into code or brought something from my mind to life on the screen.

That stuck with me. There’s always been a gap between me and software developers. I believe I always sensed their feeling of superiority, even if unintentional. This vibe once deterred me from pursuing software engineering, but now I see it differently.

  • Programmers write the code like the hands of a project.
  • Developers build and design experiences. They are the creative builders.
  • Engineers are the architects, solving complex problems and ensuring stability.

Once I started learning to code, I realized I thrive on creating something tangible. It’s become a hobby of mine, not something I’m doing just for the sake of it. My journey began there, driven purely by curiosity and the joy of building.

I’m here to build, not prove anything.

The Journey So Far 🛤️

So, here’s what you can expect to see here:

  • Mini Projects: Tiny tools and plugins designed to solve everyday problems.
  • Learning Logs: My progress in Python, iOS development, and maybe a random hobby or two.
  • Honest Stories: The wins, the facepalms, and everything in between.
  • My Journey as a Wannabe Founder: I failed as a founder when I was just 20, and since that day, I've been working hard to ensure it doesn't happen again.

I’ve been inspired by how much can be achieved when you build in public, so this blog will share both my process and my results. I want to show that you don’t need to be an expert to create something meaningful. I'm showing that since 1995 😶‍🌫️

print("Cheers")

berkem from, you guessed it, berkem.xyz

deneme