# Blog post about my experiences with Julia

**URL:** <https://discourse.julialang.org/t/blog-post-about-my-experiences-with-julia/79976>\
**Category:** Community\
**Created:** [April 25, 2022, 8:19am UTC](https://discourse.julialang.org/t/blog-post-about-my-experiences-with-julia/79976 "2022-04-25T08:19:00Z")\
**Posts on this page:** 1\
**Showing post:** 140

<div class="post-metadata">

**Author:** ![jbu](https://avatars.discourse-cdn.com/v4/letter/j/a8b319/32.png) [@jbu](https://discourse.julialang.org/u/jbu)\
**Post date:** [April 29, 2022, 7:49pm UTC](https://discourse.julialang.org/t/blog-post-about-my-experiences-with-julia/79976/140 "2022-04-29T19:49:02Z")

</div>

I agree error stack traces can be pretty intimidating. I’ve seen error messages while using Zygote + DiffEqFlux where the name of a single type in the error was over 2000 lines long 😅

As discussed in [another post](https://discourse.julialang.org/t/why-does-scientific-notation-break-the-range-function/80014/93) though, it sounds like there are tools in the works to make errors more interpretable. And as mentioned [here](https://discourse.julialang.org/t/why-does-scientific-notation-break-the-range-function/80014/81) it sounds like pull requests are welcome for simplifying error messages.

---

_[View the full topic](https://discourse.julialang.org/t/blog-post-about-my-experiences-with-julia/79976)._