# Choosing a numerical programming language for economic research: Julia,

**URL:** <https://discourse.julialang.org/t/choosing-a-numerical-programming-language-for-economic-research-julia/85697>\
**Category:** Community\
**Tags:** blog, blog-post\
**Created:** [August 13, 2022, 7:37am UTC](https://discourse.julialang.org/t/choosing-a-numerical-programming-language-for-economic-research-julia/85697 "2022-08-13T07:37:53Z")\
**Posts on this page:** 1\
**Showing post:** 79

<div class="post-metadata">

**Author:** ![JackStrauss](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@JackStrauss](https://discourse.julialang.org/u/JackStrauss)\
**Post date:** [August 15, 2022, 5:52pm UTC](https://discourse.julialang.org/t/choosing-a-numerical-programming-language-for-economic-research-julia/85697/79 "2022-08-15T17:52:35Z")

</div>

> [@TheCedarPrince](#):
>
> Inspired by @Sukera 's comment a bit up the chain about `test` documentation and @johnmyleswhite 's comments on identifying and trying to tackle issues, I opened a PR to the Julia docs that gives an example workflow on how to use `pkg> test` within one’s own package going through how to create tests, run the tests, and add the test suite to one’s own package.

A fantastic idea.

some time my misunderstanding of Pkg let me to initiate a discussion of here, where I showed myself to be rather ignorant of Julia, alas, I have no shame and here it is, if of use. [Best practice for packages on shared drives](https://discourse.julialang.org/t/best-practice-for-packages-on-shared-drives/83374)

---

_[View the full topic](https://discourse.julialang.org/t/choosing-a-numerical-programming-language-for-economic-research-julia/85697)._
