User:MichaeLeroy: Difference between revisions
(Added information on my Scratch efforts.) |
m (Updated my Julia statistics) |
||
| Line 9: | Line 9: | ||
{{mylangend}} |
{{mylangend}} |
||
Currently, I'm concentrating on providing Julia solutions to tasks. There are still many unsolved tasks for this language, and I find that this work is an excellent stimulus to learning this language. As of |
Currently, I'm concentrating on providing Julia solutions to tasks. There are still many unsolved tasks for this language, and I find that this work is an excellent stimulus to learning this language. As of 8 August 2015, Julia has solutions for 400 tasks, which is more than half of the currently released tasks. I've provided just over 150 Julia solutions, accounting for about 38% of this language's solutions. |
||
I maintain a [https://github.com/MichaeLeroy/rosetta-code github] repository of many of my Rosetta Code solutions. |
I maintain a [https://github.com/MichaeLeroy/rosetta-code github] repository of many of my Rosetta Code solutions. |
||
Latest revision as of 21:38, 8 August 2015
| My Favorite Languages | |
| Language | Proficiency |
| Julia | Scholar |
| R | Journeyman |
| Perl | Tinkerer |
| SQL | Journeyman |
| Python | Apprentice |
| Scratch | Novice |
| c | Aspirant |
Currently, I'm concentrating on providing Julia solutions to tasks. There are still many unsolved tasks for this language, and I find that this work is an excellent stimulus to learning this language. As of 8 August 2015, Julia has solutions for 400 tasks, which is more than half of the currently released tasks. I've provided just over 150 Julia solutions, accounting for about 38% of this language's solutions.
I maintain a github repository of many of my Rosetta Code solutions.
I've recently begun to look at Scratch as a means to introduce the young (and young at heart) to writing code. Because Scratch is a visual programming language, posting full solutions at Rosetta Code is problematic. I hope to share my Scratch solutions here by relying upon references to a Rosetta Code Task Solutions studio that I've established at the Scratch website. If I do a decent job of summarizing these solutions at Rosetta Code proper, perhaps I'll manage to avoid getting too many "this example needs attention" citations as I do so.