# Best way to structure Julia code

**URL:** <https://discourse.julialang.org/t/best-way-to-structure-julia-code/26591>\
**Category:** General Usage\
**Tags:** question\
**Created:** [July 20, 2019, 4:59pm UTC](https://discourse.julialang.org/t/best-way-to-structure-julia-code/26591 "2019-07-20T16:59:13Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [July 20, 2019, 5:31pm UTC](https://discourse.julialang.org/t/best-way-to-structure-julia-code/26591/3 "2019-07-20T17:31:21Z")

</div>

This is what I would also like to continue to do, but it is not (yet) supported by the linter of vs-code, and Kristoffer Carlsson says:

> [@How to use local module within a Project directory?](https://discourse.julialang.org/t/how-to-use-local-module-within-a-project-directory/26358/4):
>
> I think there are some things in the loading of code that were put there to make the transition between the old package manager without Project files (0.6) to the new package manager (0.7) easier.
> 
> I would advise against touching `LOAD_PATH` and just use packages and `dev` for local code you want to reuse.

---

_[View the full topic](https://discourse.julialang.org/t/best-way-to-structure-julia-code/26591)._