# Packages for "my own" code
**URL:** https://discourse.julialang.org/t/packages-for-my-own-code/27129
**Category:** New to Julia
**Created:** [August 3, 2019, 2:56pm UTC](https://discourse.julialang.org/t/packages-for-my-own-code/27129 "2019-08-03T14:56:04Z")
**Posts on this page:** 2
**Page:** 2
### Author:  [@lewis](https://discourse.julialang.org/u/lewis)
#### Post date: [April 10, 2020, 8:36pm UTC](https://discourse.julialang.org/t/packages-for-my-own-code/27129/21 "2020-04-10T20:36:05Z")
It seems like “project” has some Julia specific meaning.
I am getting very lost among modules, packages, and projects. Well, modules are pretty simple really.
So, going from a module to a package is mystifying in the extreme. And every IDE and build system seems to have its own notion of project.
---
### Author:  [@hendri54](https://discourse.julialang.org/u/hendri54)
#### Post date: [April 10, 2020, 9:18pm UTC](https://discourse.julialang.org/t/packages-for-my-own-code/27129/22 "2020-04-10T21:18:23Z")
Here is my understanding:
1. module = namespace
2. package = one way of defining an environment
3. project = another way of defining an environment (could be a package)
where
environment = a collection of directories where Julia looks for Project.toml files to resolve dependencies.
Then
package = a directory with a Project.toml and a bunch of other standardized things that make the code contained inside it self-contained and reusable. See [Code Loading · The Julia Language](https://docs.julialang.org/en/v1/manual/code-loading/#)
project = also a directory with a Project.toml, but not necessarily all the other stuff that defines a package.
This would be a good opportunity for those who really understand the details to correct what I just wrote.
[Previous page](https://discourse.julialang.org/t/packages-for-my-own-code/27129.md?page=1)