Comment by jackalope | Hacker News Reader

Comment by jackalope | Hacker News Reader

Parent Full thread

This is why I'm continually amazed that Excel is used in business at all. I use a command line program to record my hours and can report the time I've worked on a project to the second. Unfortunately, my Excel-based timesheet sucks at math, and shaves off time when it converts my HH:MM:SS totals to the decimal figures (HH.x) required by payroll. It's so bad, sometimes the values displayed in the columns don't add up to the displayed total if you enter them in a calculator. No sweat, I only get paid for the displayed total, and at the end of the year I compute the difference and add it to my last timesheet.

I can't imagine trusting my business finances to a program that can't deliver a reasonable amount of precision. I wonder how many fortunes are made by people well-placed enough to exploit Excel's weaknesses ("Hmmm, Excel shows that we made only $10,000,000 at our bake sale. What should I do with this leftover $700,000?" or "I can use Excel to show you that I owe you less money than I actually do.").

Let's be clear, this is a type conversion issue for seconds, Excel's not going to start adding up normal numbers strangely.

And the point of this article and the point he's trying to drive home is that it lets non-programmers actually use their computers for computing.

For most businesses a home-brewed excel spreadsheet vs a $50,000 custom program that any of us here wrote?

The harsh reality is that the Excel version written by Jane from accounting who's the Excel whizz or even the smart college temp will probably be better and cheaper than anything we could ever give them.

Until Jane leaves for greener pastures.

I do understand what you're saying though, there is a time, place, and trade offs for everything related to computing.

(imho) Most 'businessy' systems can and should start out as spreadsheets, it lets the business people solve the problems with process design, and prove its real-world value without bringing a costly developer in. The developers (like myself) should be there to take the codified mess that results, clean it up, improve usability, bring in more stability, and accountability. - Sadly, that is rarely how things go.

The problem is that by the time they've modified the spreadsheet app to solve issues with process design, workflow, edge cases, it's an unholy mess that nobody wants to touch.

excel as a functional prototyping tool.

I have no problems with this. The internal logistics of a business are better a codified mess then legend and arcanum amongst the locals.

"The harsh reality is that the Excel version written by Jane from accounting who's the Excel whizz or even the smart college temp will probably be better and cheaper than anything we could ever give them."

Too true, but I've always wondered if this is true because visual programming languages have never really been accepted as part of development or because visual programming languages were touted as a replacement for "normal" programming? Maybe it is the bad taste CASE tools left.

No, its not that.

For one Excel can be learned just after looking at it, and most people have someone who can teach them the basics.

Plus you just click one button and turn it on and then its a matter of making sure your logic pans out and the numbers get calculated correctly.

Let me restate my thesis because I sense I wasn't clear given your response.

I believe that programmers rejection of visual programming tools has lead to a situation where programmers haven't been able to easily integrate Excel into programmer's workflow in a meaningful way or evolve tools as easy to use as Excel that translate directly to code.

Actually, Excel does add up normal numbers strangely, in that like (that many computer programs) it takes user input in decimal format but stores and operates on it in binary floating point.

Its hardly as if systems that do arithmetic on exact arbitrary-precision decimal (or rational) values and only resort to approximating with binary floating point when an operation requires it haven't been around for decades.

If you pre-format the cell as text, any value input will be stored in its entirety. For one offs, prepending any string with ' will force Excel to store as text.

For date, it typically does not truncate seconds, so not sure what's happening there.

My first move in a fresh Excel workbook is Select All, Format Cells as Text.

If I were to pick one thing I wish Excel handled better out of the box, it was it's annoying habit of reformatting numbers pasted in.

Reply on news.ycombinator.com