I think it's a waste of time unless you're doing it out of curiosity or if it's directly related to your job.
I say this because I was once a new developer who felt inadequate not being able to understand the "lower level" details of our field (from my relative perspective of a web developer or product developer). Especially posts about compilers, OS or cryptography.
I spent the hours and I read the books and I built the toys. I found some joy in it at the time but otherwise I don't remember or use most of what I learned. Its lasting effects on my value as a developer or individual has been minimal.
This is not to say you shouldn't spend time learning things like this. I'm just saying I don't think you should make a programming language because posts on HN say so.
I agree. I think programmers who want to build stuff but lack creativity and entrepreneurship can end up chasing rabbit holes while telling themselves their being productive.
I think it's a waste of time unless you're doing it out of curiosity or if it's directly related to your job.
I say this because I was once a new developer who felt inadequate not being able to understand the "lower level" details of our field (from my relative perspective of a web developer or product developer). Especially posts about compilers, OS or cryptography.
I spent the hours and I read the books and I built the toys. I found some joy in it at the time but otherwise I don't remember or use most of what I learned. Its lasting effects on my value as a developer or individual has been minimal.
This is not to say you shouldn't spend time learning things like this. I'm just saying I don't think you should make a programming language because posts on HN say so.