Docker in TOP

[mccooking]

In the 2025 Stack Overflow Survey, 71% of developers used Docker, which was a 17% increase since the 2024 survey, and this number would likely be higher now.

It is a skill that should be in every web developer's repertoire, and I would be happy to contribute, as someone who has fully completed TOP's Foundations and JavaScript curriculum that would like to give back.

[ZackHoang]

I'll be honest and say that I don't think this is necessary. While SOF's data is provided and perhaps valid, my biggest question would be: Why?

For context, I have never worked professionally as a developer and I'm at the Messaging App right now and most of my experience in programming has just been within the scope of TOP.

I don't see Docker being helpful for folks around here and it does not align with the goal of teaching programming fundamentals within the context of the web.

The curriculum right now is fine as it is without Docker, I think. The kind of application that learners are building here are not sufficiently complex enough that Docker would be useful and I think it would be quite a rabbit hole that is best avoided.

[JoshDevHub]

I don't necessarily find the usage number to be all that compelling for our usecase. For developers looking to land their first role, the only thing adding a Docker course would do is maybe help people pass certain ATS checks. I just don't think either of these things are remotely true:

1. Juniors getting asked about Docker during interviews.
2. Juniors being expected to directly work on the company's container setup after getting hired (in fact, I would say if this does happen to you, you should be extremely concerned lol)

The most I think a junior is getting asked to do is to install it, pull an image, and run compose up. No one needs a course for that.

I think a more compelling argument for our situation would be opening up deployment possibilities in full stack apps. Right now, we can't really tell learners to deploy on DigitalOcean or Linode or other lightweight/cheap options because the ops would get too complicated. Docker would help a lot with that. That's something I could maybe get on board with, although I also think it's a pretty low priority.

Also, I realize I'm a maintainer, but this doesn't mean I'm shutting this down or anything. Definitely interested to hear other perspectives on it.

[ZackHoang]

I personally have found the deployment options presented in TOP have been sufficient. I have deployed File Uploader app I made with TOP using Render to host my server and Neon for my db and the process have been seamless. On Render, you just have to sign in with GitHub and just direct to your repo and it's up. Neon is also just creating a new db and just grabbing its URL to use on your Render server.

I have never used any other deployment options like DigitalOceans or Linode before so I have no idea. If it is true that these deployment options are cheaper compare to what the current recommended PaaS can offer and Docker and help ease the deployment process, that might be a good idea. Though, honestly, I have not had any trouble deploying stuff I made through TOP.

I'm not on board with having a full blown new Docker course because that's just a little too far off and places additional maintaining effort on your maintainers like yourself. There is quite enough things to keep up with on the current Node and Rails path already.