Retler
commented
2 months ago In general, I see myself contributing to all of the stated assignments. There is not one that I think I cannot participate in. What I want instead, is to highlight the parts where I think I will excel and thereby contribute most (enumeration is based on numbers from briefs.md):
1. Since Python is my strongest programming language (at the moment), I imagine that in the beginning I would be contributing a lot to building MVP's and those quick-and-dirty solutions where speed is valued above robustness.
3. Security in software is something that is dear to me. I imagine participating in some projects where I get to apply some of the security scanning tools. But I also hope to go beyond that and get the change to extend, modify or even develop additional security scanning tools which may be applied on future projects. Finally, I think that tuning and configuring these tools is crucial, in order to minimize the number of false-positives.
5. I can clearly see myself contributing to making tools, scripts and cool plugins for other developers. Things can get really nerdy here, and I am going to love it.
6. I like containerization and container hardening. It's a great way of streamlining the deployment process and adding security early in the process, which I think is both fun and also important.
7. Having done a fair bit of reverse-engineering (i.e. reading others peoples obfuscated or even compiled code), code reviews is something I can see myself participating in. If I get to do security-audits or threat modelling as part of this process, then its a great bonus.
We have added a list of brief descriptions of things that are representative of what we're involved in as a team.
briefs.md
👉 Read through the briefs and then add one or more comments to this issue where you reflect on how you could see yourself contribute to the different assignments.👈
Feel free to make assumptions if you find the briefs too sparse.