My company failed. Worked on it 6 years and ended in a burnout. Thing is I can say I tried. And now I have another few years (like atleast 40 I hope^^) to do something else. Failing early isn’t the Ende. You did atleast try if you fail.
If you've any questions, please do ask, I'd love to make myself useful.
This one will interoperate with Bouncy Castle (both Java and C#) as we both use FIPS 203 draft, but it won't interoperate with OQS simultaneously (three-way interop) as that is still on the Round 3 submission.
See also: https://github.com/bcgit/bc-java/issues/1578
(Disclosure: BC is my employer)
For general here is a list: https://pq-crystals.org/kyber/software.shtml
One thing Im personally missed out (now 27; started at 12 with web stuff) is writing. Not only writing blog articles or documentation, but writing for the sake of documenting small hacks or bigger concepts. So that would be one tip I personally would loved to get.
About projects: - either do things like features for small projects (e.g. dark mode for something like altcha.org) - try to fix some bugs - or try to recreate small projects based on a framework or vanilla for the sake of learning stuff.
As a tip for learning more things etc. in the web dev space -> Look into accessibility. Its a huge and interesting topic.
Also "that is hard and might be too hard for my skill level." -> Do it. Get started with something "easy", read papers, do tutorials, write stuff about what you learned. You wont learn if you wont try :D
In general -> Keep on learning. Don´t waste time on chasing the next framework and ask. Asking questions can be interpreted as being annoying. But if you try to understand different view points, different tech etc. you will end up talking with people that will bring you forward.
It´s nothing against docker, but keeping a bare web server secure and then introducing databases etc. with self build images is nice.
One thing Im personally missed out (now 27; started at 12 with web stuff) is writing. Not only writing blog articles or documentation, but writing for the sake of documenting small hacks or bigger concepts. So that would be one tip I personally would loved to get.
About projects: - either do things like features for small projects (e.g. dark mode for something like altcha.org) - try to fix some bugs - or try to recreate small projects based on a framework or vanilla for the sake of learning stuff.
As a tip for learning more things etc. in the web dev space -> Look into accessibility. Its a huge and interesting topic.
Also "that is hard and might be too hard for my skill level." -> Do it. Get started with something "easy", read papers, do tutorials, write stuff about what you learned. You wont learn if you wont try :D
In general -> Keep on learning. Don´t waste time on chasing the next framework and ask. Asking questions can be interpreted as being annoying. But if you try to understand different view points, different tech etc. you will end up talking with people that will bring you forward.