# Julia Script-Based Development Workflow

**URL:** <https://discourse.julialang.org/t/julia-script-based-development-workflow/129639>\
**Category:** General Usage\
**Tags:** question\
**Created:** [June 4, 2025, 12:21pm UTC](https://discourse.julialang.org/t/julia-script-based-development-workflow/129639 "2025-06-04T12:21:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Nathan\_Boyer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nathan_boyer/32/14825_2.png) [@Nathan\_Boyer](https://discourse.julialang.org/u/Nathan_Boyer)\
**Post date:** [June 4, 2025, 3:20pm UTC](https://discourse.julialang.org/t/julia-script-based-development-workflow/129639/4 "2025-06-04T15:20:19Z")

</div>

I know this struggle well and have made several posts on this forum about it. Here are a few tips:

1. Make your functions smaller. A full script should probably not be converted into a single function but rather a series of smaller function calls. It is easier to check and write tests for smaller functions and smaller subsets of inputs and outputs.

2. The fastest method to get what you want is to temporarily write the `global` keyword in front of intermediate variables you want to check after the function finishes executing.

3. Infiltrator.jl can drop you into a REPL in the context of a local function. Then you are free to explore and manipulate variables from there.

---

_[View the full topic](https://discourse.julialang.org/t/julia-script-based-development-workflow/129639)._