# Replacing MATLAB/Octave with Julia

**URL:** <https://discourse.julialang.org/t/replacing-matlab-octave-with-julia/136558>\
**Category:** General Usage\
**Created:** [April 4, 2026, 4:04pm UTC](https://discourse.julialang.org/t/replacing-matlab-octave-with-julia/136558 "2026-04-04T16:04:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [April 4, 2026, 4:16pm UTC](https://discourse.julialang.org/t/replacing-matlab-octave-with-julia/136558/4 "2026-04-04T16:16:15Z")

</div>

That being said, most people in Julia use other workflow styles. See also the thread: [Best practise: organising code in Julia - #2 by stevengj](https://discourse.julialang.org/t/best-practise-organising-code-in-julia/74362/2)

If you want to work quasi-interactively and see lots of intermediate outputs, one alternative is to use a Jupyter notebook (IJulia.jl) or Pluto notebook (Pluto.jl) — every code block in its own cell gets a displayed output saved in the notebook, and you can easily go back and edit and view intermediate steps without necessarily re-running the whole thing (though Pluto automatically re-runs all downstream calculations).

---

_[View the full topic](https://discourse.julialang.org/t/replacing-matlab-octave-with-julia/136558)._