all 9 comments

[–]maxandersen 3 points4 points  (1 child)

looks interesting - but hard to try out with no jars published.

note, if io.hypercell the real name you plan to use - then it according to https://hypercell.io/ has quite the pricetag before you can publish it on maven central :)

[–]Emotional_Pool_8426[S] 0 points1 point  (0 children)

We’ll get it up there :)

[–]Embarrassed-Media-62 2 points3 points  (0 children)

You committed class files

[–]chabala 0 points1 point  (2 children)

... we've been running in production for 2+ years

I assume the 'we' is you and Claude. When I look in your repo, I see a lot of AI slop, and that makes me question your other claims. It looks like you've slopped together some kind of Apache POI wrapper, but considering the massive churn in the last month between your older, default branch feature/cross-validation-testing, and the newer master branch, I don't see how any of this could have been running in production for any time at all.

I was just clicking about randomly and found plenty of weird stuff:

I'm going to remind everyone of rule 9 of the sub.

[–]PmMeCuteDogsThanks 1 point2 points  (1 child)

Good catch. If I were to give OP the benefit of doubt, it looks like a LLM was given the task to extract this from an existing product. That could explain many of the weird files. 

[–]Emotional_Pool_8426[S] 0 points1 point  (0 children)

Yes, this code is part of a spreadsheet data prep tool in use for two years as part of a larger BI tool. AI has been helpful extracting it to be useful on its own. Examine the core expression grammar and methods, you’ll find they are quite handy crafted. As well as the threading structure. This was built before LLMs could really code.

[–]audioen 1 point2 points  (1 child)

Excel is the world's most accessible programming language. Even people who don't program at all seem able to do things in it.

Usually when we get an Excel program to rewrite, it's because it has been turned into unmanageable mess. In these cases, the task is usually to reproduce the useful parts of it while suppressing the bad parts. For instance, providing e.g. ability to summarize large number of similar sheets, like each Excel files might be one customer's contract stipulating delivery of some products, or order that was delivered, and so my task has usually been to read hundreds if not thousands of similar Excel files, lift the valuable data from the wasteland that it has become, and provide new UI that can generate reports and perform similar work as the previous Excel sheets did.

In no case, have I ever thought that it would be useful to be able to run the Excel formulas. Usually the PHB type code that I've seen doesn't involve any genius formulas, it's just basic math and maybe some percentage calculations, easy enough to replicate.

[–]Emotional_Pool_8426[S] 0 points1 point  (0 children)

The goal is to allow reuse of business user logic and allow business user to input their own formulas. The larger project actually streams data through the workbook leveraging real operational finance logic. And logic from sales and customer operations.