# JuliaCon 2025 Hackathon Ideas!

**URL:** <https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956>\
**Category:** 2025\
**Tags:** juliacon, hackathon\
**Created:** [July 22, 2025, 6:55pm UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956 "2025-07-22T18:55:57Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [July 26, 2025, 2:33am UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956/13 "2025-07-26T02:33:56Z")

</div>

I’ll be trying to chip away at more of the [pairwise reduction refactor (#58418)](https://github.com/JuliaLang/julia/pull/58418). Some concrete things to work on here include:

- Doing a coordinated merge with sparse arrays for some pre-cursors that were split out (julia#55628 + JuliaSparse/SparseArrays.jl#615).
- Brainstorming on the arrangement of the internals (and perhaps a real interface?) to help packages that were overloading internals before
- Improvements to the benchmarking and analysis/plotting
- Hunting for more optimizations and better rearrangements (that is, [Performance challenge: can you write a faster sum?](https://discourse.julialang.org/t/performance-challenge-can-you-write-a-faster-sum/130456))

---

_[View the full topic](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956)._