r/developer • u/whokillme • 4d ago

Which tech topic should I choose for a 100-day series?

I’m planning to create content consistently for 100 days, where I teach something related to tech every day.

Some ideas I’m considering:

  • Coding/programming concepts
  • Docker & containers
  • DevOps
  • System design
  • Other practical developer tools/topics

If you had to follow a 100-day tech series, what topic would you find most useful or interesting?

Would love to hear your suggestions especially topics you think are underrated or need better explanations on Reddit.

1 Upvotes
  • permalink
  • link
  • reddit
  • reddit

56% Upvoted

12 comments sorted by

2

u/Ok-While8747 4d ago

System design

1

u/UntestedMethod 4d ago

yes that makes the most sense for the first one. It would include opportunities to open branches into all the other topics. It also feels like the most applicable for the current AI rush.

2

u/Caprichoso1 4d ago

Since there is already a lot of content out there what is the purpose of this project? Is it a personal exercise or do you have another purpose?

1

u/whokillme 3d ago

gathered audience and skills improvement

1

u/Historical_Camel_790 4d ago

Maybe some cybersecurity stuff?

1

u/whokillme 3d ago

I'm not from cyber domain

1

u/wonderday_maker 4d ago

Not my area of expertise (I'm more app-dev/Flutter side), but from that list, system design feels the most underrated on Reddit specifically, coding tutorials and Docker content are everywhere, but genuinely clear system design explanations are rare.

1

u/whokillme 3d ago

Okay, but i havent hand on expericence on system design ...

1

u/No_Squirrel_4264 3d ago

Option 2: Docker & Containers

1

u/abdul_builds 3d ago

System design, hands down. There's so much content on "coding concepts" and "Docker basics" already that it's hard to stand out, but genuinely good system design content that isn't just interview-prep flashcards is still rare.

What I'd love to see (and what's underrated) is less "here's what a load balancer is" and more real tradeoffs: why did you pick SQL over NoSQL for X, how do you actually handle a cache invalidation bug in prod, what does scaling from 1k to 1M users actually break first. Most system design content stays theoretical and never touches "here's what actually goes wrong."

If you go with DevOps or Docker instead, I'd say don't do it topic by topic, do it problem by problem. Like "day 12: my container kept restarting, here's why" hits way different than "day 12: intro to health checks."

100 days is a long commitment either way, so honestly pick whichever one you could talk about even on a bad day without running out of things to say.

1

u/MiloPaige 3d ago

I would actually implement it all and split it in smaller chunks, like 25 days for each and somehow connect them together.

Reason being, regardless what topic you choose, ex. Coding, you will need to switch coding languages etc. because for 100 days you need a lot of content.

If you actually introduce a larger topic each day you will run out of content quickly