# REPL development vs script file paths

**URL:** <https://discourse.julialang.org/t/repl-development-vs-script-file-paths/112435>\
**Category:** New to Julia\
**Created:** [April 2, 2024, 6:01pm UTC](https://discourse.julialang.org/t/repl-development-vs-script-file-paths/112435 "2024-04-02T18:01:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [April 2, 2024, 6:19pm UTC](https://discourse.julialang.org/t/repl-development-vs-script-file-paths/112435/2 "2024-04-02T18:19:29Z")

</div>

> [@ruairidh](#):
>
> Turn `src/utils.jl` into a package and `add` or `dev` it into the project environment. This seems overkill if the utilities are specific to this project and has the disadvantage of requiring a separate Git repo (I think?).

It doesn’t require a separate git repo. e.g. you can have one git repo & package `MyStuff` for the project, with `MyStuff/src/MyStuff.jl` for the re-usable parts of the project and `MyStuff/scripts/` for scripts. Then your scripts can all just do `using MyProject` for the re-usable utilities.

(Later on you can always refactor into multiple packages/repos as things develop.)

In general, as soon as you start asking “how should I organize this code” you should be creating one or more packages. Packages are lightweight (need not be registered publicly), and benefit from a lot of tooling (e.g. Revise.jl). See also [Best practise: organising code in Julia - #2 by stevengj](https://discourse.julialang.org/t/best-practise-organising-code-in-julia/74362/2)

---

_[View the full topic](https://discourse.julialang.org/t/repl-development-vs-script-file-paths/112435)._