![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jfariasfThis would be my last post about the internship.
I enjoyed everything I'm learning from this internship, and I believe the skills I learned would help me greatly in my career as a software engineer. I wish the internship was longer and covered more topics, as sometimes it felt very challenging, like going from 0 to 100, as it would be better to have more prerequisites before getting into it, but I tried to manage it the best I could.
I think I had to read and study the documentation more than once to understand it in the context of the project properly. It wasn't easy; it wasn't simple. I'm able to create litmus tests and to understand the usage of synchronization primitives in the code. I worked with spinlocks and memory barriers. However, I believe 3 months aren't enough for the whole ride of learning about the complexity of the LKMM, the CAT language, synchronization primitives, and memory barriers.
If you are interested in a project related to litmus tests, I absolutely recommend you that before you apply, try to get familiarized with Kernel development (reading and writing code), about setting up virtual machines and running custom kernels in them (i.e., QEMU), and most importantly, about the Linux Kernel Memory Model. I believe this would help you get around the hurdles of initial obstacles and technical issues when running code that is prone to fail, so you'll get more time to dedicate to the things you are interested in.
Today, I feel I learned A LOT from everything I read and did and still need to learn more. There's no way I would've done any of this by myself, so I much appreciated every bit of information I got.
I think an organization like Outreachy is one of the most amazing ideas I've seen. I wish it gets bigger, more accessible, and even more diverse.
I enjoyed everything I'm learning from this internship, and I believe the skills I learned would help me greatly in my career as a software engineer. I wish the internship was longer and covered more topics, as sometimes it felt very challenging, like going from 0 to 100, as it would be better to have more prerequisites before getting into it, but I tried to manage it the best I could.
I think I had to read and study the documentation more than once to understand it in the context of the project properly. It wasn't easy; it wasn't simple. I'm able to create litmus tests and to understand the usage of synchronization primitives in the code. I worked with spinlocks and memory barriers. However, I believe 3 months aren't enough for the whole ride of learning about the complexity of the LKMM, the CAT language, synchronization primitives, and memory barriers.
If you are interested in a project related to litmus tests, I absolutely recommend you that before you apply, try to get familiarized with Kernel development (reading and writing code), about setting up virtual machines and running custom kernels in them (i.e., QEMU), and most importantly, about the Linux Kernel Memory Model. I believe this would help you get around the hurdles of initial obstacles and technical issues when running code that is prone to fail, so you'll get more time to dedicate to the things you are interested in.
Today, I feel I learned A LOT from everything I read and did and still need to learn more. There's no way I would've done any of this by myself, so I much appreciated every bit of information I got.
I think an organization like Outreachy is one of the most amazing ideas I've seen. I wish it gets bigger, more accessible, and even more diverse.
