For older people, they should find more use with Google assistant / siri doing simple tasks for them like calling, playing music, playing videos and so on.
That curriculum never went live on the freeCodeCamp platform. So I recently built a free, open-source course on cryptography designed completely for developers: https://cryptography-for-devs.github.io
The course builds up intuition step by step.
First we cover the fundamentals. Going from symmetric encryption -> password hashing -> rainbow tables, salt -> PBKDF2.
Then the second module, the more exciting one, we go from: Diffie Hellman key exchange -> RSA -> TLS.
The material is filled with stuff I always wanted to know about like Chain of Trust, how SSH authentication with GitHub works, TLS handshake.
I am curious to know how you decided to built this...? It must have been HUGE amount of work to built it. Why you want to compete with the free offering of Google?
Also when I login there's no https in that page. Enable that please.
All the best and all the powers to you for competing with Google :)
I've tried covering only those concepts that a developer must know to understand what's going behind the scenes of framework function calls.
For example in case of Django, when a user is created, it uses PBKDF-2 for storing user password. A developer should not know at all how the pseudo-random function inside the KDF works. But they must know that PBKDF-2 is used because modern GPUs, custom circuits are damn powerful at parallel password cracking. This will make the developer realize why we use PBKDF-2 in the first place.
The course builds up intuition step by step. It starts from simple symmetric key encryption then we go to cryptographic hash functions then to password hashing then to rainbow tables & salt and then finally to PBKDF-2.
I'm releasing the first part of the course. The second part is planned to be around public-key cryptography. The tentative concepts that I think I will cover are (lessons in order of teaching): Diffie Hellman key exchange, RSA, E2E encryption, TLS / HTTPS, certificate authorities.
Most of the HN crowd might know about these concepts so I believe we all will step up to discuss how we can make the course's content a timeless resource for developers all around. I am not going to leave it as is, I will keep on iterating based on our discussions. Your inputs / time won't go waste.
Imagine yourself back to be as a beginner programmer... - could this course have helped you back then? - what changes I should make to the course that would have helped the younger you back then?
I've tried covering only those concepts that a developer *must know* to understand what's going behind the scenes of framework function calls.
For example in case of Django, when a user is created, it uses PBKDF-2 for storing user password. A developer *should not* know at all how the pseudo-random function inside the KDF works. But they must know that PBKDF-2 is used because modern GPUs, custom circuits are damn powerful at parallel password cracking. This will make the developer realize why we use PBKDF-2 in the first place.
The course builds up intuition step by step. It starts from simple symmetric key encryption then we go to cryptographic hash functions then to password hashing then to rainbow tables & salt and then finally to PBKDF-2.
I'm releasing the first part of the course. The second part is planned to be around public-key cryptography. The tentative concepts that I think I will cover are (lessons in order of teaching): Diffie Hellman key exchange, RSA, E2E encryption, TLS / HTTPS, certificate authorities.
Most of the HN crowd might know about these concepts so I believe we all will step up to discuss how we can make the course's content a timeless resource for developers all around. I am not going to leave it as is, I will keep on iterating based on our discussions. Your inputs / time won't go waste.
Imagine yourself back to be as a beginner programmer...
- could this course have helped you back then?
- what changes I should make to the course that would have helped the younger you back then?
I kind of feel you. I also feel that AI is going to be so powerful that most of the developers read it as "all average developers" are going to be in threat.
I am trying to build my own products, trying to build a business around so that money gets taken care of. Then I will code for fun, not for paying bills :)
An article I wrote on how subtraction (or basic arithmetic) works inside the processor. I wondered it one day and went deep into up till registers. This resulted in me learning about how exactly CPU executes code.
Its from a few years back but never posted on HN. The content is timeless because basics stay more or less the same.
Let me know your honest thoughts. I love going deep into questions my mind gets stuck on. Let me know if you want me to continue this deep dive:D
Are you still into E2E testing these days? I am currently of the thought process that using AI to create e2e tests is not the right strategy but letting AI maintain it is the right one.
Any thoughts you would like to share since you are have had more experience using AI for e2e testing than anybody I know.
Man, Sikuli. My mind just blasted to see that people did similar stuff in 2009!
When I saw a few months ago, Open Interpreter used OpenCV to interpret GUI. Don't you think Sikuli was way way ahead of its time?
Please tell me more about the success part, if you could tell me more about what steps did Sikuli performed? how fast was it? Because when I last tried Open Interpreter that used OpenCV, it felt way too slow for UI e2e testing.
For older people, they should find more use with Google assistant / siri doing simple tasks for them like calling, playing music, playing videos and so on.