I highly recommend simply getting involved with an existing package that you use. Start small, and slowly learn the codebase. Look through the issues to get a sense of what bugs and enhancements they're already considering, and maybe start an issue or two to ask about missing functionality that you might want. Then start posting PRs for missing functionality you need. Be sure to add unit tests. Don't get discouraged if they're not approved right away — it takes a lot of time to read and understand code you didn't write. But the review process is great for learning the best-practises for library code (which, you're right, is a very different beast than one-off scripts and pseudocode. It's gotta be fast and work for everyone!).
It's always amazing to me how, every time I post a new PR, I learn something new or have missed an obvious bug that is quickly caught. The folks involved here are wonderful. Matt On Thursday, July 10, 2014 6:55:20 PM UTC-4, Ted Fujimoto wrote: > > Hi all, > > Can anyone recommend any references on how to create a Julia package like > a seasoned Julia developer? Based on my conversations with some of the > Julia experts, the process seems a bit more involved than just writing out > Julia-style pseudocode. Are there general rules of thumb on how to optimize > Julia code? > > Thanks, > Ted >
