TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Use Spreadsheets Everywhere

169 pointsby jetheredgealmost 4 years ago

38 comments

laGrenouillealmost 4 years ago
I agree with a lot of the points raised here. I think many of the problems with spreadsheets are due to the software rather than the users. As mentioned in the article, its hard to slowly iterate from a small manageable spreadsheet to an larger software solution.<p>For example, Excel would be a lot more usable and maintainable for me if there was a way to make a special &quot;data sheet&quot; in which data types are forced to be consistent within columns and there was a concept of column names. Still GUI-based and user-friendly. That would encourage a logical seperation between data entry, data output, and computations. In my experience, the main challenge of helping users with spreadsheets is when they create spaghetti code that mixes data and computation together.
评论 #28050392 未加载
评论 #28050724 未加载
评论 #28050177 未加载
评论 #28050366 未加载
评论 #28051602 未加载
评论 #28050404 未加载
评论 #28050403 未加载
评论 #28051629 未加载
评论 #28050086 未加载
d--balmost 4 years ago
One aspect that is rarely talked about is that Excel is really good for developers who know about data&#x2F;stats&#x2F;business&#x2F;databases but don&#x27;t know about frontend app development.<p>Excel thrived in banks, not because traders used it, but because IT&#x2F;Quant people used it. It&#x27;s so much more straightforward to build a UI in Excel than with React. Just type things in cells, then wire them with simple VBA buttons. Of course there are things you can&#x27;t do, but for the purposes of a bank, it&#x27;s very rare that you find one.<p>So if I am a quant, I don&#x27;t need to go to the frontend guy, trying to explain to him what a &quot;vega&quot; is and why I would want to multiply by notional&#x2F;vol to change the units. This is a huuuuge time saver. And you can change your UI anytime. Just open the file, add a column, click save and it&#x27;s done.<p>At some point, banks knew that fat-finger-mistakes could cost them fortunes, and the lack of auditing was terrible. But they had to force traders to switch off their sheets by threatening them with internal fines (we&#x27;ll charge you $2m for running things with Excel). So traders complied, but then they got into years-long projects, to create shitty shitty web apps, that couldn&#x27;t do half of what Excel had built-in. Every change would need to go through an approval process, and it&#x27;s unclear whether these systems had less bugs than spreadsheet did.<p>The first thing they wanted when the project was done? &quot;Give me a button to export to Excel&quot;.<p>For the shameless plug part, I am building a tool to try and bridge code and spreadsheet (<a href="https:&#x2F;&#x2F;www.jigdev.com" rel="nofollow">https:&#x2F;&#x2F;www.jigdev.com</a>). Lmk if you have comments&#x2F;suggestions.
评论 #28051029 未加载
France_is_baconalmost 4 years ago
This article is BS. As others have noted, it is a straw man argument.<p>Everyone uses spreadsheets, including developers. I use them. I&#x27;m not going to spend 50 hours coding when I can create a spreadsheet in 5 minutes.<p>Of course, the issue is when things get complicated, as the author and others here have noted.<p>Creating a CRM from spreadsheets is pure madness, for example, when there are so many other options that exist, without having to custom program.<p>For me, whenever you have a one-to-many or many-to-many situation, that&#x27;s where spreadsheets, to me, fall apart.<p>I personally have used spreadsheets to do my finances, but only because I was too lazy to scope out different bookkeeping systems. I&#x27;m fairly expert in accounting, too. I&#x27;ve used a LOT of different accounting systems, and installed and trained people on them. But there&#x27;s no way that one can get up and running as fast as one can by using Quickbooks or other accounting systems, in terms of all the report features, etc.<p>Pre-defined apps are fairly unchangeable, but unless one has critical information that depends on a custom solution, it&#x27;s better to shoehorn your business into a pre-existing app. I do admit that. Very few small and medium sized businesses require that, though, I&#x27;ve never seen one yet that can&#x27;t use a prior existing solution. Though there might be, but only very, very small percentage, like, less than 1%. However, a large Fortune 1000 enterprise could have stuff they need custom programming, because of the scale. But I don&#x27;t have any experience with enterprise organizations so I can&#x27;t comment on that. Maybe SAP or whatever is good for them, I don&#x27;t know.
WJWalmost 4 years ago
Can&#x27;t disagree. Spreadsheets are incredibly powerful tools and the barrier to entry is very low.<p>The only situation I can think of where you should discourage their use is in those situations where you know <i>for sure</i> in advance that the application is going to outgrow the spreadsheet very soon and&#x2F;or immediately. If you are building a new microservice that will serve a million customers per day, don&#x27;t make the mockup in a spreadsheet.
评论 #28050548 未加载
linker3000almost 4 years ago
If you have had to fill multiple, spreadsheet-based, customers&#x27; InfoSec questionnaire about your SaaS product, including the need for tailored, multi-paragraph answers (ie: you can&#x27;t copy&#x2F;paste from stock responses), you might disagree with the raw headline.
评论 #28050139 未加载
评论 #28052974 未加载
评论 #28050531 未加载
castillar76almost 4 years ago
There&#x27;s a real back-and-forth struggle for me with spreadsheets. I find people very frequently reach for them for things that they do really well: data slicing and dicing, ordering and sorting, formulae that cross-reference cells, and so forth. However, the <i>contents</i> of those spreadsheets are often (for me) not numeric, but text, and working with text that&#x27;s longer than a few words in Excel is <i>still</i> a huge PITA, even after all these years, because Excel still thinks of the contents of cells as numbers first.<p>Consider the output of your average audit. You&#x27;ll have tables of findings, each of which needs a due date, a risk rating, a description of the problem, a description of the solution, auditor notes, customer comments, responsible party assignments, and so forth. (Yes, those would eventually go well in a tool like Jira, but that&#x27;s for later--this is coming out of an audit visit.)<p>From a <i>data</i> standpoint, putting those in a spreadsheet makes sense: you can now order the findings by date or risk rating, hide ones that don&#x27;t apply, cross-reference findings between visits, and so forth. However, from a <i>text</i> perspective, it&#x27;s awful: the descriptions might run to multiple paragraphs, comments and instructions need more complicated formatting than just &quot;bold or italic&quot;, some fields should be constrained on content while others need to be free-form, and so forth. All of those things work much better in a Word table than in Excel cells, but putting the content in Word utterly removes the ability to data-manipulate. So you wind up either creating some Frankenstein hybrid solution or with crushing one perspective to satisfy the other.<p>If Microsoft wants a win for Excel, making it an order of magnitude easier to deal with free-form text in cells would be an enormous step forward.
评论 #28053435 未加载
jayd16almost 4 years ago
We need a spreadsheet format that&#x27;s more conducive to the professional programmer workflow.<p>Parsing them is actually very complex. You just have to hope your library can handle everything in excel. If you&#x27;re a cli native I&#x27;m not really sure what you do.<p>Spreadsheets don&#x27;t play very will with source control. If the underlying format was text and every cell and formula was on a new line it would work out ok. As it is now, merging them is very cumbersome....impossible for the laymen that might be the main user of the sheet.<p>By going with a speadsheet and not something like SQL, you lose a lot of rigor.<p>There&#x27;s probably a few more needs but these are top of mind for me.
评论 #28050480 未加载
评论 #28051642 未加载
Vasloalmost 4 years ago
People understate the power of spreadsheets. You are literally using a visible programming language. When I have to write a algorithm to read from a file or a spreadsheet, I can model it very easily on the spreadsheet to get all my i&#x27;s, j&#x27;s, and k&#x27;s right, and I can watch it occur incrementally line by line in a spreadsheet. When I was buying my house, I was able to easily line by line show my wife where all the cash was going. No print statement, variables, or anything I&#x27;d need in Python or C++. I could do it in 5 mins and it was as good as anything those languages could have done.<p>All that said, I can see issues with errors that are hidden by spreadsheets but those can be handled with good spreadsheet design (i.e. NEVER EVER hard code anything into a cell) and they simply just need a way to do GIT type version control natively. We recently got the ability to have multiple people work in the same spreadsheet at a time if on MS Teams, but there&#x27;s more work to do there.
评论 #28052066 未加载
评论 #28052006 未加载
zwiebackalmost 4 years ago
Article raises some valid points but how do you catch the point where the spreadsheet gets out of control? Maybe MS could build in a warning system and then suggest some potential solutions.<p>Minor quibble: it&#x27;s an Apple III in the ad, not an Apple ][ as the post says. I remember running Visicalc on my Apple ][ but it wasn&#x27;t until Excel appeared that I realized how seductive spreadsheets can be.
评论 #28050178 未加载
usehackernewsalmost 4 years ago
As a product manager, spreadsheets have been an incredible asset to build products when I had limited resources and to iterate quickly.<p>When we had no front-end devs available - we used Googles sheets API, connected our spreadsheets to our production DB, and did all the input of raw data, and ingestion of outputs automatically. User interaction happened within the spreadsheets.<p>When FE devs opened up, we eventually built the UI to replace the spreadsheet (Which is a very hard task, spreadsheets are good at what they do). But by this point, we knew exactly what we needed in the ux and had iterated on the ux multiple times.
jhbadgeralmost 4 years ago
My issue with spreadsheets is that they don&#x27;t encourage reproducible science. For example, if you write code in R or python to log transform your data, you can look at the code and see that it has been done. If you have a spreadsheet that you (or worse, someone else) has created, you can maybe look at the values and guess it has been log transformed, but you can&#x27;t know for certain that was the case and no other transformations were applied.
bitwizealmost 4 years ago
One thing I&#x27;m surprised hasn&#x27;t taken off is something like Framework. Framework was a hybrid word processor&#x2F;spreadsheet&#x2F;database&#x2F;graphics&#x2F;communications program based around the unifying concept of a frame, all scriptable in a Lisp-like programming language from which every frame -- down to individual spreadsheet cells which counted as frames -- was directly addressable. Frames could even serve as sources of input or sinks for output to&#x2F;from external programs or remote machines.<p>Framework was pretty much Emacs for the office, and such was its power that unlike contemporary spreadsheets and word processors, which were usually positioned as productivity tools for generating business documents and reports, Framework was explicitly marketed as a decision making tool for executives. It did well in markets such as Europe where Lotus hadn&#x27;t taken over, but it just about died when the Windows era started.
jacobdialmost 4 years ago
Spreadsheets versus programmers is a war that can be much more peaceful. In my work, I have found that, especially in data science, the spreadsheet user and the programmers are often trying to accomplish similar tasks, but the “language barrier” between them leads to much more fragmented workflows. I also think this article does a good job of identifying spreadsheets as a low-code programming language — spreadsheets are immensely powerful pieces of software. Along these lines — I’ve been building Mito (<a href="https:&#x2F;&#x2F;trymito.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;trymito.io&#x2F;</a>), a spreadsheet GUI for Python. Every edit you make in the spreadsheet generates the equivalent Python code.
评论 #28049883 未加载
评论 #28051709 未加载
评论 #28050222 未加载
mmckelvyalmost 4 years ago
I think a lot of the &quot;problems&quot; with using large scale spreadsheets can be somewhat ameliorated by moving the underlying data to a proper database and then using the spreadsheet as a GUI &#x2F; interactive analytical tool. Now that you can make external API calls in Excel[1], this actually seems doable.<p>[1] <a href="https:&#x2F;&#x2F;docs.microsoft.com&#x2F;en-us&#x2F;office&#x2F;dev&#x2F;scripts&#x2F;develop&#x2F;external-calls" rel="nofollow">https:&#x2F;&#x2F;docs.microsoft.com&#x2F;en-us&#x2F;office&#x2F;dev&#x2F;scripts&#x2F;develop&#x2F;...</a>
bob1029almost 4 years ago
We are getting pretty crazy with our use of Excel documents these days. With a little bit of OpenXML magic, you can read&#x2F;write these things from code. I&#x27;m not talking about CSV either. I am talking about full-blown XLSX files, where you can control font&#x2F;color&#x2F;size&#x2F;worksheets&#x2F;et.al. with a few lines of logic.<p>Once you are able to read &amp; write excel documents with a piece of software, you can do some pretty fucking incredible things.<p>Imagine being able to click a single button and download a total configuration output for a customer&#x27;s environment (maybe 20-30 worksheets auto-generated in seconds). You can then email this human readable document to the customer for modifications. You then feed this back into the system to load their adjusted values (there is a diff&#x2F;check-in report to confirm first).<p>The reason we and our customers like this approach is because there is a lot of configuration where we need to compare lists of things and slice parts of one thing into another. It makes replicating success absolutely trivial. Being able to style the document is a much bigger benefit than you would probably think at first. CSV is trivial to employ, but it is very constrained on this front. For a developer who is familiar, color &amp; layout doesn&#x27;t move the needle much. For a customer who has no clue how the back-end works, these things make all the difference in the universe. Things you can&#x27;t edit are grey background, things you can are green, etc.
foxbeealmost 4 years ago
Some apps should be spreadsheets. Some spreadsheets should be apps.<p>It&#x27;s the user&#x27;s decision that&#x27;s usually wrong. Not the framework in which the solution is built.<p>For example, at Budibase [1], we&#x27;ve found a high percentage of our use cases are companies upgrading their in-house spreadsheets to applications due to several reasons: Volume of data Lack of auditing Lack of control Accessibility<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;Budibase&#x2F;budibase" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Budibase&#x2F;budibase</a>
3majalmost 4 years ago
I have a love hate relationship with spreadsheets. While in University I was a bit of an Excel Monkey, I knew everything there was to know and I prided myself in not having to use my mouse to make complex models... Now that I worked at a major bank, learned to code and moved to the data science side I despise spreadsheets. Most people don&#x27;t realize this but out entire banking system is built on a couple excel models that all the banks use - when something goes wrong its a nightmare to fix.<p>Recently, we&#x27;ve started to see a major shift away from spreadsheet models to spreadsheets being used as data dumps and then being uploaded into third party software. Usually this &quot;software&quot; tends to be nothing more than some SQL and python scripts behind a fancy UI. I would personally prefer the banks to continue using Excel sheets and then pay for their employees to learn basic python and SQL but that&#x27;s too simple and the SaaS sales guys have their claws firmly embedded in the upper levels of most orgs.
评论 #28050295 未加载
neovivealmost 4 years ago
Spreadsheets are the original low-code&#x2F;no-code platforms! There&#x27;s something magical about showing a non-coding subject matter expert a few Excel tips and watching them subsequently visualize and automate a process on a spreadsheet. Also, looking at spreadsheets built by non-coders is a great way to spur software&#x2F;start-up ideas.
kinj28almost 4 years ago
Every CRM starts with a spreadsheet or every applicant tracking system starts with spreadsheet. Many organizations love to start with spreadsheet and then evolve to application (Ready or custom).<p>At <a href="https:&#x2F;&#x2F;www.dronahq.com" rel="nofollow">https:&#x2F;&#x2F;www.dronahq.com</a> we support 1. users to connect to their spreadsheets and build applications on top. or pull data from multiple datasources e.g. spreadsheets and support ticket system and build custom tool.<p>2. We understand people love columnar database like spreadsheet or airtable.com, hence we offer an built-in database called &#x27;sheets&#x27;<p>3. We support most excel formula and functions for binding data or writing complex business logic i.e Logical Functions, Date and Time Functions, Text Functions, Math Functions, custom functions
jccalhounalmost 4 years ago
Spreadsheet programs are incredibly powerful. I was a math education minor and one of the classes I remember most was using computers in the classroom and using spreadsheets to do things that aren&#x27;t obvious like estimate square roots. (well at least not obvious to me)<p>However, I think spreadsheet programs are still way to complex for the vast majority of people. So many people are so math phobic that they won&#x27;t even think of opening a spreadsheet.<p>One thing I&#x27;ve done with a spreadsheet a few dozen times is take the outputted CVS file my learning management system gives me in the form of last name, first name and convert it to first last in one cell. I still have to find the bookmarked answer I found years ago and cut and paste it in and I don&#x27;t really understand how it works.
timviseealmost 4 years ago
Please no!<p>Spreadsheets are broken. It&#x27;s easy to be at error due to calculation issues, which you&#x27;ll only find out when manually going over it. It&#x27;s a calculator that can&#x27;t properly calculate. Many business have made huge mistakes due to it.<p>Never ever use it for financial calculations.
davnicwilalmost 4 years ago
At Stacker (YC S20) we do something kind of in between, hoping to catch usecases where people need an actual app just as they are outgrowing the spreadsheet, by allowing you to build an app... from your spreadsheet!<p>It should be interesting for anyone who&#x27;s done a lot of thinking* about the relationship between spreadsheets, no code, and custom software. Check us out: <a href="https:&#x2F;&#x2F;stackerhq.com" rel="nofollow">https:&#x2F;&#x2F;stackerhq.com</a><p>* if this is you, and you&#x27;re <i>really</i> interested, we&#x27;re hiring. Email in my profile :-)
评论 #28054992 未加载
taninalmost 4 years ago
Spreadsheet is incredibly powerful<p>However, if your use case is narrower (e.g. only use CSVs), there are more suitable tools.<p>As a person who knows how to code, using a real programming language or SQL is way way better.<p>To that end, I&#x27;ve built a Desktop app that enables you to work with CSV using SQL here: <a href="https:&#x2F;&#x2F;superintendent.app" rel="nofollow">https:&#x2F;&#x2F;superintendent.app</a>
turboconalmost 4 years ago
For what it&#x27;s worth, I&#x27;ve now seen a couple times where the spreadsheet becomes too large and somebody hooks the spreadsheet up to a database so it does queries. That seems to work well for the users willing and able to learn some SQL, and it confuses most others which results in some really strange spreadsheets...
goatloveralmost 4 years ago
So Alan Kay was right about live coding, at least for the average person, but he was wrong about what kind of software. That or SmallTalk with spreadsheets would be the killer low-code app. Lotus Notes also made use of @ formulas for it&#x27;s forms, and then there was Hyper Card for easily building GUIs.
mikewarotalmost 4 years ago
Spreadsheets are incredibly powerful tools, as they support reactive programming natively.<p>The main problem is when you embed a table in a sheet and use it as you would in a database. It is far too easy to overflow the maximum spreadsheet size, or overwrite data... or worst of all sort some <i>but not all</i> of the columns.
nix0nalmost 4 years ago
Do any of the spreadsheet lovers here use anything other than Excel?<p>I want to like LibreOffice Calc but it&#x27;s just too slow.
评论 #28050828 未加载
fleroviumalmost 4 years ago
It&#x27;s the interface: a grid of editable cells is incredibly easy to use and as almost as information-dense as possible.<p>It&#x27;s interesting to see non-excel&#x2F;google sheets products use the same interface to good effect. Examples don&#x27;t come to mind but I&#x27;m sure there are some.
评论 #28050117 未加载
评论 #28050659 未加载
PretzelFischalmost 4 years ago
Spreadsheets are good for one thing but they are the handy hammer that seems to work for many other things. I would love to see an open and extensable table&#x2F;matrix program that would surplant the spreadsheet applications.
beefmanalmost 4 years ago
Plain sortable tables are underused. Markdown tables are horrendous for example (CSV blocks would be better). Having formulas as well would be amazing, but let&#x27;s not ask for the world.
andrewlgoodalmost 4 years ago
When contemplating shifting end users to something other than spreadsheets, one needs to keep in mind how many spreadsheet users there are and what there motivations to change.
spicybrightalmost 4 years ago
Dang, what software engineers hate spreadsheets? I&#x27;ve never worked anywhere that didn&#x27;t use them for project planning and other such stuff.
评论 #28050067 未加载
评论 #28050251 未加载
评论 #28049849 未加载
评论 #28050605 未加载
评论 #28049828 未加载
peter303almost 4 years ago
Most of my hundreds of spreadsheets are simple: rarely larger than screen with about 20 columns and 50 rows. Error creeps in with size.
jonfromsfalmost 4 years ago
Githubs new project management tool is essentially a github-aware spreadsheet. It&#x27;s surprisingly awesome.
Kinranyalmost 4 years ago
We need software that works both as a spreadsheet and as a database.
评论 #28050445 未加载
评论 #28050183 未加载
GaryTangalmost 4 years ago
Excel is unusable on ios. For that reason, I’m out.
andrewlgoodalmost 4 years ago
Article covers a great point, just does not provide a framework to make decisions regarding when to use spreadsheets.<p>I am a CFO that has used spreadsheets my entire career (30+years). They can definitely have a vital role in any company and can also cause incredible problems.<p>A few thoughts that were not mentioned in the article:<p><pre><code> 1) in many companies the users of spreadsheets are not allowed to use anything more powerful than spreadsheets (or maybe MS Access which causes more problems). To get a SQL&#x2F;Python (or other programming language) solution requires submitting a request to IT and then waiting two years to work up the priority queue. This is not a complaint against IT and the priority process. The reality is most spreadsheets do not start out as important enough to warrant high priority. 2) Spreadsheets are great containers. Not only can they hold a model, but also the raw data, and even emails regarding the model&#x2F;inputs&#x2F;etc. This makes them very handy for keeping everything in one file regarding an analysis. 3) IME, most significant spreadsheets get rewritten as they evolve, especially when they change hands. This is both good and bad. While the rewrite allows correction of built up badness, it is rarely done with the discipline one sees with refactoring in more traditional code. Moreover, when a hand off happens, the rewrite is generally done because the recipient does not fully understand how the existing model works. 4) Large spreadsheets cannot be effectively audited outside of locking&#x2F;password protecting non-input cells. Very rarely is this actually done. As a result, you get the scenario the author describes of hard-coded values in cells that once contained formulas. These are almost impossible to find in worksheets with large numbers of tabs and thousands of formulas. 5) Spreadsheets generally do not use true version control. For most of my career, one simply used &quot;File Save As&quot; to create a new version. In the early days it was due to a fear Windows would crash and you would lose your work. Later, it became a way to step through changes and determine the impact of the change. While this method provides some ability to go back to a prior state, people really do not track properly what each version contains and what are the true differences (would love to find a way to use Git effectively on spreadsheets). 6) Most spreadsheets do not have test cases. They certainly do not increase the test case universe as modifications are made. As a result, cannot tell if things break when changes are made. </code></pre> Given all of these things, I recommend using spreadsheets for ad hoc analyses and to pilot analytics that will become part of a routine process. The latter point is the point the author is making (and the point of his title). I would add that the analysts need a plan and methodology to determine when they need to convert from the anything-goes freedom of spreadsheets to a more disciplined, maintainable, controlled program.
brimoorealmost 4 years ago
I agree with this one. People who don&#x27;t know how to code can easily use spreadsheets in your everyday life. For example, to calculate your income and expenses. To track and monitor your finances.
评论 #28049800 未加载
评论 #28051775 未加载
评论 #28049711 未加载