# Julia protips

**URL:** <https://discourse.julialang.org/t/julia-protips/16749>\
**Category:** General Usage\
**Created:** [October 24, 2018, 5:04pm UTC](https://discourse.julialang.org/t/julia-protips/16749 "2018-10-24T17:04:43Z")\
**Posts on this page:** 1\
**Showing post:** 54

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [November 1, 2018, 12:01pm UTC](https://discourse.julialang.org/t/julia-protips/16749/54 "2018-11-01T12:01:43Z")

</div>

> [@airpmb](#):
>
> (at least those that concern the core language/standard library and any packages that are \>= 1.0) should not be at as much risk of becoming outdated?

There is certainly a trade-off here between ease of contributing and having outdated examples. 1.0 may be around for at least a few years, but [standard libraries can potentially change](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623/16) even during that timeframe, and 3rd party libraries are moving at a very quick pace, with some releasing multiple new major versions in a year.

At the same time, the presence of outdated code snippets on the net is already a concern for some (but of course we cannot do anything about that and all languages which are developed actively have this problem).

I think the ideal to strive for is having an API and documentation (with examples etc) that makes things so intuitive and well-explained that “pro tips” are not needed at all.

---

_[View the full topic](https://discourse.julialang.org/t/julia-protips/16749)._