Being my team's local Excel guru (every team has one)... I was (un)lucky enough to work on a project in my previous job that involved documenting someone's badly written Excel/VBA code after he suddenly left the company.... the guy had clearly just recorded a whole bunch of macros then copied and pasted stuff around, with minor editing... no comments, no naming conventions... ech... painful 4 months of my career...
But seriously, this book is mainly useful to beat people around with, because people like him definitely aren't gonna read it.... they see "Professional" and "development" in the title and they ain't gonna open it.... More so, ub3r-l33-g33k-developer types aren't gonna read it either.... they're all too high'n'mighty'n'l33t to develop in Excel.....
None the less, I'm ordering my copy, so I can slap people around with it whenever they ask me to develop something huge for them.... I'm not even a developer by trade!!!
Slashdot Mirror
.... to beat a few people around the head with...
Being my team's local Excel guru (every team has one)... I was (un)lucky enough to work on a project in my previous job that involved documenting someone's badly written Excel/VBA code after he suddenly left the company.... the guy had clearly just recorded a whole bunch of macros then copied and pasted stuff around, with minor editing... no comments, no naming conventions... ech... painful 4 months of my career...
But seriously, this book is mainly useful to beat people around with, because people like him definitely aren't gonna read it.... they see "Professional" and "development" in the title and they ain't gonna open it.... More so, ub3r-l33-g33k-developer types aren't gonna read it either.... they're all too high'n'mighty'n'l33t to develop in Excel.....
None the less, I'm ordering my copy, so I can slap people around with it whenever they ask me to develop something huge for them.... I'm not even a developer by trade!!!