![]() |
|
|
FlashChat | Actuarial Discussion | Preliminary Exams | CAS/SOA Exams | Cyberchat | Around the World | Suggestions |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#31
|
|||
|
|||
![]() One way is not to follow the oversight in the demo here. at 3:30 he inserts a column, but doesn't fix the grand total or average columns.
http://office.microsoft.com/home/vid...HA102376171033
__________________
John 3:16 |
#32
|
||||
|
||||
![]() PDF: Goal-directed debugging of spreadsheets
http://web.engr.oregonstate.edu/~erw...ug_VLHCC05.pdf Quote:
Alas, I see no links on how to get a hold of the software itself. May be they're developing it for commercial use, and don't have a full release yet. Or perhaps they see it just as an academic project. Last edited by campbell; 02-25-2008 at 12:02 PM.. |
#33
|
||||
|
||||
![]() So, after I've written a few articles on general principles of preventing/detecting spreadsheet error, I'm looking to see what direction I should go in.
I've got an idea for a technical article, talking about loss of precision in using floating-point arithmetic, and some tricks to consider to reduce that sort of thing (numerical analysis sorts of ideas.... I know quite a few actuaries have been exposed to this, but many more have not.) Another idea was dealing with end-user risks, considerations, resources, etc. Any ideas from people? What kinds of computing/programming/spreadsheet errors/issues would you like to read about? |
#34
|
||||
|
||||
![]() Quote:
Poor documentation results in the following problems/risks: 1) Significant lost productivity for future users (technical or not) as they have to spend hours to days to months trying to understand the spreadsheet. 2) Misuse due to lack of understanding of the spreadsheet. 3) Lack of use of the spreadsheet or using spreadsheet to only part of its potential. 4) Having to rebuild the spreadsheet by a future user (call it "re-invent the wheel risk"). I think this risk is particularly high in environments with high turnover. I think advanced spreadsheet users tend to design spreadsheets in a "for my eyes only" way. I'm guilty of this myself. The key is realizing that your product is near useless in the future if you don't document it or don't take the time to "teach" it to someone else. |
#35
|
||||
|
||||
![]() Quote:
![]()
__________________
Some people are like slinkies. Mostly useless, but provide amusement when pushed down the stairs. |
#36
|
||||
|
||||
![]() Quote:
__________________
Carol Marler, "Just My Opinion" Pluto is no longer a planet and I am no longer an actuary. Please take my opinions as non-actuarial. My latest favorite quotes, updated Nov. 20, 2018. Spoiler: |
#37
|
||||
|
||||
![]() I'm on the EUSPRIG mailing list (it's in Yahoo groups I think.... here it is - obviously, it's not just Europeans on the group), and end user concerns was something that came up recently, in response to this article: http://www.cfo.com/article.cfm/11525407?f=insidecfo
Sloppy Spreadsheets: Readers Speak Out Readers make some pointed additions to CFO.com's "worst practices" list. Quick summary: - formatting sucks, not set up for printing - missing info: no context/title on each individual sheet, no numbering of sheets for printout (important if you'll be distributing hard copies around -- you can't refer to tab "Sheet1") - things that look bad when reformatted because of text bleeding over into adjoining cells - no summary of all tabs for a large file - I have this problem with some of the work I've come across.... a bunch of tabs with similar names, and no index/table of contents - hard-coded numbers (I've mentioned this in a couple of articles) - hiding columns/rows with sensitive information in it... and leaving that in when file is distributed to external people. The worst I've seen here is someone changed the format to white on white.... easy enough to change it to be readable. They recommend "protecting" a cell, but that just protects against people inadvertently coming across sensitive info. It is relatively easy to "break" Excel passwords, and I've done it in the past with legacy spreadsheets where the originator was no longer around. - using a spreadsheet where a calculator will do (I use Excel as an informal calculator all the time. I don't see the problem here, unless you suck at Excel. But then if you suck at Excel with calculation, you'd probably suck with a calculator.) |
#38
|
||||
|
||||
![]() Using the Excel row numbers as the primary key for a table (one of my department's main spreadsheets has this quality) - the table doesn't even have column headings, so I pity the fool (i.e. me) who decided to insert a row at the top to type in a description for each column, and inadvertently destroyed the spreadsheet.
Is it so difficult to put in a hard-coded column of numbers that go 1, 2, 3, 4, ... so you're independent of the position on the page? ![]() |
#39
|
||||
|
||||
![]() Quote:
|
#40
|
||||
|
||||
![]() Quote:
__________________
When I meet you in person, shots on me! Do you bite? We are a bunch of high roller players who like to play high roller games - Hardinda |
![]() |
Tags |
machine learning, predictive analytics, speadsheet error, spreadsheets |
Thread Tools | Search this Thread |
Display Modes | |
|
|