Yeah, it's easy: once you know a dozen languages or so the quick reference like this one is all you really need to learn most languages, ...
Yeah, it's easy: once you know a dozen languages or so the quick reference like this one is all you really need to learn most languages, at least to the point of comfortably writing everyday code. I say "most" languages, because this kind of reference doesn't work for languages based on completely different semantics than the languages you know: APL and J are the primary examples for me (EDIT: also, Forth. But not Factor or Cat or Joy... dunno why exactly). Anyway, this is great for polyglot programmers, who would be bored to tears by "beginners guide" to just about any language and who know enough about how programming languages work. It's probably of very little help to programmers who know only a very few languages and/or for those who didn't study programming language design, though. In my case I successfully used this site (and some other resources, as well) to get up to speed with Haxe, Nim, LiveScript and Lua, but then again, learning new languages is something I do all the time ( https://klibert.pl/articles/programming_langs.html ) for years now, so I may not be the best example :)
Posted by klibertp on Apr 26, 2015, 1:53 PM
Tags
Related issues
- I mean that's the problem though.
- I've always believed the opposite: get conditionals deep in your code so that the higher level control flow is regular.
- The biggest problem with AI isn't being able to do things.
- I am a 3D printing maker type nerd (I make my own tools for other creative tasks, rather than as their own outcomes) and I saw an incredi...
- Of course not, those are clearly scams.
- Claude makes more detailed plans that seem better if you just skim them, but when analyzed, has a lot of errors, usually.
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
hackernews (EdTech)
I mean that's the problem though.
I've always believed the opposite: get conditionals deep in your code so that the higher level control flow is regular.
The biggest problem with AI isn't being able to do things.
I am a 3D printing maker type nerd (I make my own tools for other creative tasks, rather than as their own outcomes) and I saw an incredi...
Of course not, those are clearly scams.
Claude makes more detailed plans that seem better if you just skim them, but when analyzed, has a lot of errors, usually.
Effectively everyone is building the same tools with zero quantitative benchmarks or evidence behind the why / ideas … this entire s...
> creating and operating a small company in Germany is a nightmare To be fair, I think the problem operating in Germany is its federated...
Yeah, it's easy: once you know a dozen languages or so the quick reference like this one is all you really need to learn most languages, ...
Yeah, it's easy: once you know a dozen languages or so the quick reference like this one is all you really need to learn most languages, at least to the point of comfortably writing everyday code. I say "most" languages, because this kind of reference doesn't work for languages based on completely different semantics than the languages you know: APL and J are the primary examples for me (EDIT: also, Forth. But not Factor or Cat or Joy... dunno why exactly). Anyway, this is great for polyglot programmers, who would be bored to tears by "beginners guide" to just about any language and who know enough about how programming languages work. It's probably of very little help to programmers who know only a very few languages and/or for those who didn't study programming language design, though. In my case I successfully used this site (and some other resources, as well) to get up to speed with Haxe, Nim, LiveScript and Lua, but then again, learning new languages is something I do all the time ( https://klibert.pl/articles/programming_langs.html ) for years now, so I may not be the best example :)
Comments (0)
No comments yet. Start the discussion.