So is Photoshop and Google Maps - the point of the article isn't bashing on Excel, it's about choosing the wrong tool for a job.
This is constantly repeated truisms, and yet I don't use it and have no plans using it. I'm certain I'm not alone. Excel is counterintuitive and not 'consumable' as the opposite to SQLite. Surely I understand it not the same. Also I suspect most of the Excel users use it like CVS editor.
The immediate feedback and visual layout make it the definition of "killer app." Jupiter notebooks has been trying to replicate the magic for years. Entire businesses and industries are built around selling products to successfully replicate what was originally living in a spreadsheet somewhere.
Too easy to refute. Treating "Excel" as actually "spreadsheet processing," the software has been so consistently and hugely popular that everything from early PDAs [0] to Google Sheets / iCloud Numbers has supported it. Every type of personal computing device has it, from graphic calculators [1] to laptops to tablets to PDAs to many cell phones.
> I suspect most of the Excel users use it like CVS editor.
Like some classes of addictive chemical compounds, you may start with this but quickly find it is the gateway to other habits.
[0] https://en.wikipedia.org/wiki/HP_95LX
[1] https://education.ti.com/en/software/details/en/139B977E62CB...
I feel like I'm hearing "Hundreds of people who don't like Elvis can't be wrong". And I don't even like Elvis!
"Karen" can literally write programs with little training, there's memory, there's functions, there's references, excel is the best.
I do not particularly like excel, I find it interesting but often obtuse and limited in annoying ways and I agree that for an established workflow using "proper" code is generally better. But imho where Excel excels is in dynamic exploration and supporting decision making, where the type of analysis and visualisations you might want to do can change radically and quickly
And, what's git? A spreadsheet can be committed to git.
Version control for spreadsheets? It'd be awesome to have on its own, but it's also not hard to add it on top of spreadsheets' existing features.
That's exactly my point.
It's always interesting to see where developers don't build obvious solutions into existing tool.
You're very right that it's not hard, but to me, the fact it hasn't been done, is interesting thing from a sociological perspective.
I've seen many code editors with amazing git ergonomics built in, never for spreadsheets.
I'm actually working on text only spreadsheet markup that is human intuitive and building interfaces to go with it.
>I'm not sure, honestly. It depends on whether you want the fix being done by a resource you consider to be a cost center or a value center. The former will do the cleanup job for bottom dollar. The latter would team up with Karen to amplify the project's impact while cleaning it up.
You're right that the answer is "it depends." In the world of risk management and audit, what Karen has created is called a "user-developed application." Her employer should give her a big pat on the back, and then take a step back to decide 1) if this Excel spreadsheet is mission critical, 2) if it is, who will maintain it, and 3) whether its importance justifies building a formal IT solution to support the business function (either in-house or using COTS software).
I agree that Karen did nothing wrong! She found a process that could be improved or automated, and was able to use technology to do it. If someone is caught off guard when the Excel file goes kaput, then that's not Karen's problem nor is it her fault; it's her employer's responsibility to pay attention to their own business requirements.
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.
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.
This is not the first time I see developers berating non-technical users, and I like the thesis that they will function as cost-centers that will do a cleanup job instead of teaming up with the user. It's like they will attempt to "do the work" in a binary fashion, making the "correct" choices, often focused on technical factors, like which library to use or what algorithm, instead of focusing on the business domain.
I also see this attitude when facing technical issues or bad code as if it wasn't our job to deal with bad code (and as if non-bad code existed)
And that avocado slicer vs. kitchen knife analogy is perfect, it captures the nuance so well. Some tools are brilliantly specialized, while others thrive on flexibility. Maybe the real takeaway is that knowing when to reach for each is the mark of a savvy developer.
Thanks again for the great discussion, this is why I love sharing on Hackernews, nowhere else has such a density of curious, sharp-minded people who push ideas further.
I was a bit confused by the post because it seems to be written about a persona that I haven't personally come across: professional developers who choose visual workflow tools as a primary solution over building with code the "right way".
I'm still a bit confused because you make broad statements about these tools and their users while actually you seem to be focused on this specific subset of users. e.g. when you talk about why these tools are successful, was your intent to limit the scope of your comments about the success of this category to just professional developers?
In a separate comment, I criticized the post before I fully realized you're specifically talking about developers, and not the typical audience for these products. I'm trying to understand if that's the lens through which the entire post should be interpreted. If so, making that more clear would strengthen the post I think.
I'm still a bit skeptical about the existence of said persona, but happy to be shown I'm wrong.
> You know what happens with Excel. Karen from accounting builds a “simple” spreadsheet to track expenses. Six months later, it’s a 47-sheet monster with circular references and VLOOKUP formulas that would make a mathematician weep. The company depends on it, nobody understands it...
It sounds like Karen did a valuable service to the company. She combined a technical skill set with her domain knowledge to create a system that was so successful that the company now depends on it. Cleaning up the technical debt seems like a task that's well worth the cost.
> ...And when it breaks (not if, when), guess who gets called to fix it?
I'm not sure, honestly. It depends on whether you want the fix being done by a resource you consider to be a cost center or a value center. The former will do the cleanup job for bottom dollar. The latter would team up with Karen to amplify the project's impact while cleaning it up.
For these reasons I think your analogy is not effective. I don't disagree with your thesis, though; I prefer code in almost all cases. But that's just me. I know for certain, though, that if I had stock options in that company in this hypothetical scenario I'd rather keep Karen around than whoever fixes the VLOOKUP syntax. And if visual tools are what empowers Karen... well, there you go.