I don't have much to add to what others have said about workflow. Lots of good advice so far, especially about putting things into modules early on and putting effort into getting short, tightly-focused functions.
Here's the one piece of advice I wish I had been given early on: Multiple dispatch is the heart and soul of Julia. The language has lots of other neat features, but multiple dispatch --and the associated type system-- is the key to effectively modeling problems in Julia. It's the one thing you should concentrate on really understanding, and the one thing you should really pay attention to when looking at well-designed code others have written. If you're coming from an OOP background, it may take some time to come to terms with how multiple dispatch allows, encourages, and sometimes demands that you structure your model. On Thursday, May 12, 2016 at 12:01:04 PM UTC-5, David Parks wrote: > > I'm a few weeks into Julia and excited and motivated to learn and be as > efficient as possible. I'm sure I'm not alone. I know my way around now, > but am I as efficient as I can be? > > What haven't I tried? What haven't I seen? What haven't I asked? > > For those of you who have been around longer, could you share your advice > on efficient day-to-day development style? > > For example: > > - What IDE do you use? Are you using Atom? A combination of Atom and > the REPL? Something else? > - How do you debug complex code efficiently? How do you debug other > peoples code efficiently? > - Do you have a favorite way of visualizing your work? > - Are there must have tools? packages? utilities? > - Any simple day-to-day efficiency/advice you could share with others > who didn't yet know to ask. > > >
