Inception: virtualization, containerization, etcetera
I've always found the names of subjects of the 42 School quite on point. Sometimes funny or witty, but at least they always made sense. That's honestly not the case for 'Inception'. I've never understood the logic behind the choosing of this name. Maybe it has something to do with the fact that this project about virtualization needs to be evaluated entirely in a virtual machine? I think the more likely explanation is that while writing the curriculum the people who were doing it were suffering some sort of writer's fatigue. Just like I am right now, because after describing so many projects, it is hard to stay original I feel like. But I made this obligation to myself and therefore only I am to blame...
What I learned
Anyway, I learned a lot while doing this project, but what I learned most I think is that DevOps isn't really something for me. 😅 I think it goes for most programmers, but the infrastructure, dependency management, configuration and all that just seem so super boring and unnecessary. I talked to one other student in my school who was very passionate about this project and about DevOps, which made me believe that I maybe should give it another chance and try harder to understand its purpose and to like it, but not anytime soon, I am afraid...
