Klee, Kandinsky, Escher, Kahlo, Riviera, Ethan Heidelbaugh, Steve Hemingway, Marcel Duchamp, Georgia O'Keefe, and whatshisname that I'm totally spacing out on right now but I'll remember later probably.
I did a little more research and there were indeed quite a few resources to be found that I had initially overlooked when I last pursued it. And, coincidentally, before I posted this I spent a long while working with a Google Docs spreadsheet to see whether or not I might be able to hack together some sort of rough guesstimation tool or primitive convolutedValuationCalculator or something, which turned out to be a little overly optimistic in my case due to my somewhat limited spreadsheet chops.
(Which is not to say that I didn't learn a lot from playing with the data. Also, it is impressive to me that Google Docs has a spreadsheet application that is actually pretty usable and responsive, I was kind of expecting the worst case scenario but ended up making 3-4 additional spreadsheets for a couple other projects.)
However, while fun, my efforts still didn't feel like they were yielding results that could be held up to even minor scrutiny by one of the alternate solutions hawked by most of the top Google results. You know how there are some areas of software where Open Source has for all intents and purposes been able to provide options that mirror the feature sets and overall functionality of their proprietary analogs? Well, unfortunately, to me it seems that Business Analytics is still something of an Open Source ghetto, with few viable options to be found, and those scarce resources and projects that do exist don't seem to have the features I'd most benefit from.
Wrapping up, though, I was able to come up with a few very primitive views and models for this project that were slightly helpful; however, as I mentioned before, I am no spreadsheet shaman by any stretch of the imagination, and although I'd love to take the time to practice those skills, it is honestly not a viable option this month and we need software with this functionality quickly.
My feeble efforts did "work", (well, sort of), which was interesting, but I lack confidence in the way I approached the problem and overall my efforts still felt like I was doing a lot of voodoo-powered guesswork, which is probably accurate, and I think that even if I practiced for a few days, I'd probably not be able to handle incorporating the hardcore number crunching and quantitative analysis features necessary to make a project successful.
I know in the banking industry there are some standard valuation methods for this sort of thing, although I don't remember much from my Principles of Banking classes now that it's twelve years later. It would be really nice, however, to be able to build something with a strong core foundation, and I suppose the only way to succeed with an approach like that is to work with industry-accepted formulas & methodologies.
I forgot to specify another particularly important point, as well: specifically, my main concern (and an area that was conspicuously unrewarding in terms of search results) as I mentioned before, my ideal "goal" would be to find an algorithm or set of algorithms that are (if not universally) accepted by the banking industry, the business valuation industry, intellectual property appraisal services, trademark appraisers, etc. It is important to me that these valuation methods are transparent, as I'd like to develop some Open Source software that utilized them, and I'd like to be confident in the methodologies and formulas before wasting any time writing the software rulesets.
But I'm not even sure that such metrics exist. Is the valuation software market as fragmented and wildly variable as it appears? I will probably never know. :-)
I did find a few books on Amazon that seemed to contain this type of information, but holy mackerel, I cannot currently justify shelling out $250.00 for a single title! I had no idea that this type of information was still entrenched in proprietary solutions, or even if the theoretical texts are available, they are still prohibitively expenses for my particular situation.
Long-term, I think I'm going to attempt to collect a decent sampling of the formulas and algorithms involved, because I think Open Source projects could eventually be made to rival the best of the proprietary options. But short-term, I do have an immediate need for something that can provide decent valuations without being too laborious or convoluted.
You're not aware of any Open Source projects that handle this type of thing, by any chance? I did spend a little time Googling for such a project, but it didn't result in anything worth pursuing, unless my search queries were not using the correct verbiage, which is possible.
I understand that business analytics in general is one area where the Open Source software equivalents are still not compelling alternatives to the proprietary offerings, and I am trying to explore the reasons why this is so. I understand that the legal expertise is an expensive problem domain, and probably represents a large barrier to entry, which is also probably true of the MBA & higher-level education involved in enhancing the rulesets and programmatic routines, and also that analytics projects may not be appealing to Open Source programmers necessarily due to the fact that they are not very glamorous compared to certain other projects.
And quantitative analysis of the data sets is also quite clearly a highly specialized and difficult realm, I'm sure, which is to say nothing about the subjective stuff that might be involved - I'm thinking stuff like "user group studies" to measure brand impact and loyalty trend information, which is probably overthinking it of course, but any additional thoughts into what might would yield insights and statistically solid data points might be useful.
However, maybe that's overthinking the problem, which I tend to do sometimes. I guess I'd be happy with a super simple scoring method that provided a little feedback about "consumer's overall brand satisfaction score", or something.
Back to the old drawing board for now - thanks for the response and information, brk.
If a small demo, as you put it, is important enough that you need to show it for your career, it's important enough to either spend the time learning web design basics to make a decent looking demo, or else to enlist outside help.
(This doesn't necessarily mean hiring an expensive web designer or design firm; I regularly consult on projects for cheap or free in order to help clients, business contacts, and friends, and have found that it almost always pays off in terms of establishing better relationships with people, who in turn refer projects back to me, etc.)
So, I guess what I'm saying is, if you're not the greatest at design but need design services, then, uh, try to make friends with a good web developer with altruistic tendencies.
I really liked The Pragmatic Programmer, although some might think it's not a very technically challenging work.
I also like most of O'Reilly's Perl books.
Also, Jonathan Rockway's book on Catalyst was very helpful for me, although there were some issues with typos in the first edition (which is to be expected.)
Also, Philip Greenspun has published a good free collection of computer-science and web-development related texts on his website.
(Sure, he's a little arrogant and some people find his writing style to be somewhat abrasive or even borderline nonsensical, but I certainly liked most of his work. And I believe I learned quite a bit from it, as well, though I'm sure that is debatable.)
I use Flash, and I'm also aware of Perl's "Catalyst Framework", which I also, uh, use all the time. I mean, um, they are both, uh, software projects aimed at uh, what's the phrase I'm looking for here, oh yeah.
They are both software projects designed to leverage object-oriented best practices and innovative programming concepts in order to facilitate rapid applications development on the web.
So, er, no confusion at all, uh, right?
(I like how you claim ignorance on behalf of an entire "community", as if that's some kind of excuse.)
I couldn't agree more. It seems like terribly bad form.
(That being said, well, I'm a very biased Perl/Catalyst developer.)
But I'm not surprised by this, much. I am forever resigned to the fact that open source projects in general (and in particular, the more "polite" open source projects such as Perl culture overall) generally do a haphazard job when it comes to branding their projects, and obviously fall flat on their faces most of the time when it comes to policing a trademark, or what-have-you.
It's not that the Perl/Catalyst people aren't <strong>smart</strong> enough to register Catalyst as a trademark; it's simply that doing so would be antithetical to the entire Perl culture. Plus, it costs, like, $400 or something to register a trademark, and what kind of open-source hippies have that kind of money just lying around anyway.
So, we're probably going to have to get used to the fact that Adobe is going to run rampant over the Catalyst Framework, as they are of course the 800-pound gorilla of design software. Not that I don't like Adobe, of course, some of their software is pretty nice to use. (Especially if you are provided the software through your job, and you don't have to think about the price tag.) (And before you bark at me, uh, yes, I do in fact use both the GIMP and InkScape on my "real" computer. I just think some Adobe products are nice an polished and useful and optimized.)
(Remember when Macromedia and Adobe sued and counter-sued each other over software patents? That was fun to watch. Also, when companies do that, uh, it's probably a good time to start thinking about who is going to buy whom.)
Anyway, so, yeah. I think that's really mean of Adobe. I don't know if it's evil, necessarily. Just ignorant and boorish of them. It's sort of like them admitting, "Uh, yeah, we're supposed to be the big-league company you think of when you hear the word "CREATIVITY", but, uh, well we couldn't think of anything even halfway original so we decided to steal a brand name from the Perl community."
(I actually have a couple friends who work for Adobe. Maybe I should ask them "Hey, guys, WTF is up with you stealing our WORD? I mean, it's OUR WORD. WE OWN IT."
Except that would also then make me feel like an idiot.
Still, I might do it anyhoo. I've always wanted to be a whiny open source "advocate".)
