Re:Every Visual Workflow Tool Is Just Excel for Developers W...
by jdauriemma on Monday August 04, 2025 @02:02PM
(#44789376)
Good point, though not all spreadsheets are created equal. Some get quite unmanageable, and that can be a productivity bottleneck over time (unless you're not really adding new use cases)
Re:Every Visual Workflow Tool Is Just Excel for Developers W...
by Ezhik on Monday August 04, 2025 @02:11PM
(#44789502)
Maybe the real problem to solve is not killing Excel but providing a pathway for load-bearing Excel sheets to grow into full applications, development practices and all.
Re:Every Visual Workflow Tool Is Just Excel for Developers W...
by jdauriemma on Monday August 04, 2025 @02:16PM
(#44789550)
I feel like this is doable with a good LLM-assisted coding tool, but it's just a hunch.
Re:Every Visual Workflow Tool Is Just Excel for Developers W...
by antisthenes on Tuesday August 05, 2025 @09:35AM
(#44797782)
I think the hardest part here is UI.
With Excel you get no-code immediate UI feedback in the cells.
Most people will use an Excel sheet as an array or a dataframe.
Re:Every Visual Workflow Tool Is Just Excel for Developers W...
by dalibenothmen on Monday August 04, 2025 @06:57PM
(#44792273)
Thank you for your comment.Totally get what you’re saying and yeah, that’s a solid take. My main point was more about what happens next when those "Excel-as-solution" systems grow beyond their original scope and start needing maintenance, collaboration, or scale. That’s where things can get tricky. But I completely agree Excel often is the hero in the early stages.
The technical debt here was solved by creating a complex Excel worksheet. The sheet is the solution.
For small companies where these Excel monsters get created, it is the #1 best way (read - cheapest) to solve technical debt, which, before Excel, was probably a bunch of arcane manual processes that took 5x as long with worse accuracy.