# Has anyone made a Julia code organization cheat sheet?

**URL:** <https://discourse.julialang.org/t/has-anyone-made-a-julia-code-organization-cheat-sheet/142996>\
**Category:** Teaching & Outreach\
**Tags:** code-organization, cheatsheets\
**Created:** [November 17, 2026, 10:35pm UTC](https://discourse.julialang.org/t/has-anyone-made-a-julia-code-organization-cheat-sheet/142996 "2026-11-17T22:35:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rafael.guerra](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rafael.guerra/32/216610_2.png) [@rafael.guerra](https://discourse.julialang.org/u/rafael.guerra)\
**Post date:** [November 17, 2026, 10:35pm UTC](https://discourse.julialang.org/t/has-anyone-made-a-julia-code-organization-cheat-sheet/142996/1 "2026-11-17T22:35:03Z")

</div>

Hi all,

I’m a hobby Julia user and I keep getting confused about code organization: how projects, environments, packages, modules and registries fit together.

I tested several AI systems to help draft a one-page cheat sheet, but it took a fair amount of iteration and checking before I was reasonably happy with it. It’s attached as an SVG.

It covers:

- How Julia finds code: `--project` → environment stack → `Project.toml`/`Manifest.toml` → depot → registry
- Project vs package (the difference I most often got wrong)
- What modules are (namespaces), and `using` vs `import`
- Public vs private registries, basic package layout, and common Pkg commands

**Two questions:**

1. Does something like this already exist? I’d rather use/link a maintained one.
2. If not, could more experienced folks take a quick look and correct anything wrong or misleading? _Since I’m not an expert, some of it may be off._

Happy to update the sheet with any corrections and repost, but it’s probably more efficient to hear it straight from knowledgeable Julia programmers.  
Thanks!

 ![julia-code-organization-Mistral-AI_v4](https://global.discourse-cdn.com/julialang/original/3X/0/b/0bc357443b9917b1bf822fbf6bd4580095a04947.svg)

---

<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:** [November 18, 2026, 5:21am UTC](https://discourse.julialang.org/t/has-anyone-made-a-julia-code-organization-cheat-sheet/142996/2 "2026-11-18T05:21:36Z")

</div>

Very nice!

Some remarks:

- using of LOAD\_PATH is discouraged
- do you have an editable version? I would like to replace LanguageServer with JETLS
- Revise.jl is not mentioned
- startup.jl is not mentioned

---

<div class="post-metadata">

**Author:** ![rafael.guerra](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rafael.guerra/32/216610_2.png) [@rafael.guerra](https://discourse.julialang.org/u/rafael.guerra)\
**Post date:** [November 18, 2026, 7:49am UTC](https://discourse.julialang.org/t/has-anyone-made-a-julia-code-organization-cheat-sheet/142996/3 "2026-11-18T07:49:15Z")

</div>

Thanks, Uwe!  
Is SVG editable? Absolutely, and I recommend using the awesome free and open-source vector graphics editor Inkscape.
