TL;DR

For software tester, every day is a learning opportunity. We are in the business of making software, an illusional thing that needs the computer to manifest itself. And making software is a complicated process. This post gives you a hint on how to learn something when you do not understand it. This post is based on a remarkable book written by Chad Fowler, The Passionate Programmer.

Here is one set of possible questions:

Continuous integration is always a hot topic, but do you really know how does it internally work on your project?

How that bug fix finishes on production or integration server? Why do you use two programming languages in your project, e.g., Javascript and Ruby?

I would like to know the difference between Javascript and Ruby languages. What is Angular? What is Ruby on Rails?

Do you know in which programming language is build script written?

Why we use Heroku instead of Amazon Web Services?

Where do we store confidential customer documents?

What is S3?

How do we do some tasks triggered by timer?

What is a cron job?

What is the batch?

Why our server needs 100 Gb of RAM?

How can I see how much memory is currently used by the server? What is a memory leak?

What is garbage collection (hm, is this internal DEVOPS joke or real problem)?

Conclusion

You probably have your own set of questions. Note them down, make a task with a deadline, and start learning on your path to the passionate tester.