5 ms·
A lot of people who have access to Excel also have access to Access - and a lot of what they do would be better served in database than a spreadsheet. Yet they
by untog 12y ago
A lot of people who have access to Excel also have access to Access - and a lot of what they do would be better served in database than a spreadsheet. Yet they don't use one - there must be a reason for that, and I don't think it's IT restrictions.
- andrewfong 12y agoThis little tidbit from Chris Granger seems relevant: "Excel is inherently observable since it doesn't have any hidden state and all values are there for you to see and manipulate. It's also direct. You change values in the grid, drag drop things, do calculations on selections, and so on. And it manages to sidestep a lot of incidental complexity; spreadsheets are timeless, without setup, and don't even have a notion of being run." http://www.chris-granger.com/2014/03/27/toward-a-better-programming http://www.chris-granger.com/2014/03/27/toward-a-better-prog...
- miahi 12y ago> don't even have a notion of being run They actually do have such a notion - in Excel you can set the calculations to Manual and then you hit F5 to refresh everything in one go. Useful when you deal with current date and time.
- Renaud 12y agoIt's actually F9. F5 opens the Go To dialog box.
- deleted 12y ago[deleted]
- frandroid 12y agoSaying Excel doesn't have any hidden state is stretching things a bit--your formulas don't show up until you are directly on them, so mistakes (formula results that got turned into static data, for example) are hidden until you put your cursor directly onto them.
- Someone 12y agoI never use it, but you can toggle between showing formulas and showing values with CTRL + ` (grave accent) (http://office.microsoft.com/en-001/excel-help/display-or-hide-formulas-HP005199811.aspx http://office.microsoft.com/en-001/excel-help/display-or-hid...)
- rahimnathwani 12y ago"formula results that got turned into static data" This hints at one of the sources of problems with Excel. One good approach to using Excel is to always be in one of two modes: changing the structure (equivalent to coding) and entering values (equivalent to using software). Of course, at the early stages of designing something you will be entering lots of dummy values (e.g. ARPU) to check that your formulae work. However, many people don't distinguish between collections (rows, columns or other contiguous areas) of cells which _should_ contain values, and those which should contain formulae. I, like many, prefer to indicate input cells with a yellow or orange background, so that I know everything else is a formula. You can do even better: - If you're done designing a spreadsheet, and expect to use it for a production process, then mark the input cells as unlocked, and protect all the sheets. Then the end user won't be able to mess up the formulae. - Always write formulae in a way that they can be copied across or down whilst pointing to the right places. This can be achieved through use of one or more $ signs to fix a reference. I've seen a fair number of spreadsheets where there are a large number of similar formulae, but they have been entered/adjusted manually. This is fine only if you never make mistakes, and if no one else needs to change the formulae later or verify they are correct. My point is that "formula results that got turned into static data" can be avoided with just a few easy rules. However, most people aren't taught these rules :(
- dragonwriter 12y ago> Always write formulae in a way that they can be copied across or down whilst pointing to the right places. This can be achieved through use of one or more $ signs to fix a reference. Except if you are using modern version of Excel, don't general use $ references for this, go one step further and use names (for fixed individual datapoints where you would use two $s) or named tables with named columns (for the most common use of single $ references.) This is more self-explanatory and less error-prone.
- dragonwriter 12y ago> Excel is inherently observable since it doesn't have any hidden state Except that it does -- even in terms of simple numerical values what you see is not necessarily the actual value, but instead the result of passing the value through a format string that can vary by cell.
- rahimnathwani 12y agoSadly, most people don't use this feature, and are content to show values using the default format, even if it results in values displayed as 12904819.23 (which might be better displayed as 12.9m or 12.90m).
- gavinpc 12y agoThis Rory Blyth cartoon has been ungoogleable for at least ten years now, but I still check every so often. Now here it is! http://wyorock.com/excelasadatabase.htm http://wyorock.com/excelasadatabase.htm What I was going to say before unexpectedly finding that, is that the gap between Excel and Access is huge. I've made a living off of that gap at various points, and at some point I stopped thinking they were "doing it wrong" and started thinking, "whatever makes you happy."
- aaronem 12y ago> ...at some point I stopped thinking they were "doing it wrong" and started thinking, "whatever makes you happy." The secret to success in contract software development.
- kiyoto 12y agoSQL is scary. I've talked to hundreds of customer prospects for Treasure Data, and by far the biggest surprise I encountered is how few people know their way around SQL. I am not talking about just "business" people but also programmers. Contrast this dearth of SQL-proficient population with the massive, massive Excel user base: I jokingly tell my friends that Excel is by far the most popular programming language =p
- sitkack 12y agoMuch of the ORM market and NoSQL were precisely because programmers don't understand SQL.
- manicdee 12y agoThat, and typing "select x from table A, table B where tableA.foreign_key = tableB.index and tableA.index=5" is a little long-winded and more prone to error, when you can just do x = ModelA.objects.get(pk=5).ModelB
- chris_mahan 12y agoSELECT B.x FROM tableA A JOIN tableB B on A.foreign_key = B.index WHERE A.index = 5 That's very simple, if you know SQL. I think
- chris_mahan 12y agoTrue that. I use SQL extensively, and never run into all these problems other people run into. I also don't use ORM. there's so much you can do well and fast with SQL. (I've also seen dreadful abominations in sql, like stored procedures that dynamically generate code for pivot tables... wait, that was me who did that)
- untog 12y agoAccess actually has (or had, it's been a long time) a very well put together visual query designer. As long as you weren't doing anything crazy you'd never need to touch SQL.
- collyw 12y agoSomeone has to explain how a database works before you can use Access properly. Explain the relational model. Otherwise it just offers tables to the user that look a bit like an excel sheet but with less functionality. In Excel they can form some sort of data model a lot more easily.