# Naming conventions for property/method/variable overlaps

**URL:** <https://discourse.julialang.org/t/naming-conventions-for-property-method-variable-overlaps/127474>\
**Category:** General Usage\
**Created:** [March 28, 2025, 6:16pm UTC](https://discourse.julialang.org/t/naming-conventions-for-property-method-variable-overlaps/127474 "2025-03-28T18:16:03Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![co1emi11er](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/co1emi11er/32/206849_2.png) [@co1emi11er](https://discourse.julialang.org/u/co1emi11er)\
**Post date:** [March 29, 2025, 12:00pm UTC](https://discourse.julialang.org/t/naming-conventions-for-property-method-variable-overlaps/127474/5 "2025-03-29T12:00:42Z")

</div>

I have found that using modules and submodules provides the best user experience. It also helps a lot with method discovery. Here is a [thread](https://discourse.julialang.org/t/modules-and-submodules-for-a-better-user-experience/123600) I posted about it.

I plan to write my packages this way moving forward. Here is my latest package using this approach for inspiration: AISCSteel.jl

And with your `RationalFunctionApproximation` being too long, you can always do:

```julia
import RationalFunctionApproximation as RFA

```

In fact I do that with my package:

```julia
import AISCSteel
import AISCSteel.Shapes.IShapes.RolledIShapes as RIS

```

---

_[View the full topic](https://discourse.julialang.org/t/naming-conventions-for-property-method-variable-overlaps/127474)._