One close to my heart use case is to enable older people use phones easily.
Most of the app UIs built today is so difficult to use, people unfamiliar with technology find it even more challenging.
This tool if enabled with voice and freed from adb shackles can make it so convenient for the older folks or even the blind folks.
Part of my tool(finder) can even be used to create a walkthrough overlay on the screens.
Getting local models to eventually drive all this is the goal. Cost reduction due to that is a nice by-product.
More use cases I can think of will be in the security space, automating logins to test apps, for example. Using app+mitmproxy+llm to do some automations around security.
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 :)
Thank you for visiting our website and providing positive feedback! It's important to note that our competitors are not Google's free offerings. The product we are currently promoting is tailored to the enterprise audience, particularly those who require office suite applications and online collaboration, but also have stringent data security requirements. Our product is well-suited for these needs, as our on-premise deployment method can perfectly accommodate such demands.
Regarding the https issue you raised, I will discuss it with our team. In fact, the trial interface you logged in is that we deployed an on-premise product in a server environment. This is not a conventional trial system but rather a specialized presentation. Rest assured, the web page is secure, and we appreciate your understanding.
If you have a heightened interest in our product, please feel free to leave your email on our contact page. Our team is eager to engage in further communication with you.
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 :)
I wouldn't be so sure. LLMs have hit a wall, anthropic and openai can't seem to make anything that performs better than their current offerings.
Developers are going to be in threat short term because the market is very competitive right now, but unless there's some brand new kind of AI that isn't an LLM, I think we've probably seen all they can do
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
I am curious to know your motivation behind making this?
You wanna integrate this into a product? or was it a try to optimize on Claude's cost?