3 ms·

I hate it when people generate these contrived examples where they intentionally stack the scenario to favour whichever way proves their point the most. Which

I hate it when people generate these contrived examples where they intentionally stack the scenario to favour whichever way proves their point the most. Which is easier to understand: =SUM(profits01_2012:profits12_2012) Or: SELECT * FROM dassaddasads WHERE date > 1325394000 AND date < 1356930000 Which is easier to understand?!

deleted 14y ago
[deleted]
InclinedPlane 14y ago
This ignores the common use case. yummyfajitas' examples were exceedingly stereotypical of both excel and mysql usage.
- UnoriginalGuy 14y ago
  They aren't stereotypical of the kind of Excel that gets written by people who use it as a major part of their job. They're stereotypical of people writing poor Excel queries against unnamed cells via location reference.
dspeyer 14y ago
Is that first one valid Excel? I've never seen it before.
- UnoriginalGuy 14y ago
  Yes, it is valid Excel. Naming cells is something they teach in beginners courses. http://www.computerhope.com/issues/ch000704.htm http://www.computerhope.com/issues/ch000704.htm http://support.microsoft.com/kb/274504 http://support.microsoft.com/kb/274504
omni 14y ago
I have seen literally hundreds of Excel spreadsheets from banks, consultancies, and VC firms and I have never, ever seen anyone name individual cells the way you are proposing here. If I had to name individual cells in a monthly model spanning the next 10 years over 250 line items, I'd quit that job. I'm not saying that Excel can't do it, but a) it sounds like it would take a huge amount of time, so b) it is not practically done in "the real world."
- jodrellblank 14y ago
  If I had to name individual cells in a monthly model spanning the next 10 years over 250 line items, I'd quit that job. Why would you quit the job over a few minutes of scripting with "WorkSheet.Names.Add"? http://msdn.microsoft.com/en-us/library/office/ff835300.aspx http://msdn.microsoft.com/en-us/library/office/ff835300.aspx

deleted 14y ago

[deleted]

InclinedPlane 14y ago

This ignores the common use case. yummyfajitas' examples were exceedingly stereotypical of both excel and mysql usage.

UnoriginalGuy 14y ago
They aren't stereotypical of the kind of Excel that gets written by people who use it as a major part of their job. They're stereotypical of people writing poor Excel queries against unnamed cells via location reference.

dspeyer 14y ago

Is that first one valid Excel? I've never seen it before.

UnoriginalGuy 14y ago
Yes, it is valid Excel. Naming cells is something they teach in beginners courses. http://www.computerhope.com/issues/ch000704.htm http://www.computerhope.com/issues/ch000704.htm http://support.microsoft.com/kb/274504 http://support.microsoft.com/kb/274504

omni 14y ago

I have seen literally hundreds of Excel spreadsheets from banks, consultancies, and VC firms and I have never, ever seen anyone name individual cells the way you are proposing here. If I had to name individual cells in a monthly model spanning the next 10 years over 250 line items, I'd quit that job. I'm not saying that Excel can't do it, but a) it sounds like it would take a huge amount of time, so b) it is not practically done in "the real world."

jodrellblank 14y ago
If I had to name individual cells in a monthly model spanning the next 10 years over 250 line items, I'd quit that job. Why would you quit the job over a few minutes of scripting with "WorkSheet.Names.Add"? http://msdn.microsoft.com/en-us/library/office/ff835300.aspx http://msdn.microsoft.com/en-us/library/office/ff835300.aspx