bcRIPster

Everything you know about the first AI winter is wrong. It was a hit job. Minsky learned from Pitts and McCulloch. Then he buried their field for twenty years. The same institutional pattern that shaped the first AI winter is running again today.

Nice rebuttal though. He has a point. Either show your proof refuting the claim or stfu. I get so tired of armchair experts discounting everything because they just know it can't be true, that it would be nice if someone put people like this in their place once in a while.

High-five. I like your thinking!

No, it wouldn't, there's more than enough stuff like this that goes around that taking one slice off the stack isn't really going to change the stack. ;)

The thing is these solutions all sounds great on paper, but in practice for the common person? Not so much. For those people that know what their doing it really doesn't matter because they know what they are doing and update as they scale.

It's the 99% of the rest of the people who see "how easy that was" and suddenly they're over their head. And they are the same people who tell you that you can't change anything about the broken ass interface bolted onto the spreadsheet while you're fixing it.

"Can't you just fix it so it will stop crashing? Why do you want to change all of this? We don't have approvals to change this, the spreadsheet is what was approved by change control. Just make it work."

IT WILL NEVER WORK. Go away. =D

I understand, but every time I get handed one of these it's because someone who didn't know what they were doing was rapid prototyping something and woops they have 200 hundred users and it's crashing, it's corrupting data, etc...

At one job I'm like "people, just use Access, it's installed on your computer" and they look at me like I'm talking dark wizardry shit with their fingers itching on their pitchforks because they don't know if I'm going to eat their babies.

Arrrrgh!

A spreadsheet is NOT a database! Argh!

As a person who gets asked to fix these kinds of projects once they hit a wall (performance/concurrency/etc) and then have to migrate them to a proper DB platform, just stop it! Put it on in a DB up front and save some poor developer their sanity.

Please.

Well, she did prove one point though. She's not a customer for these things and doesn't have first hand understanding of that market. So she's got that going... :P

Apple makes a tech tool? Uh, no. They make fashion tech and have for over a decade now. Yes it's functional for techies but it's fashion plane and simple, and yes people will shell out for it. I know people that were already planning out the buy on the $10K model the day it was introduced before it even had a solid price because the price doesn't matter.

I'm going to disagree. I do SEO work and this format is dying. Readers are put off by it as it lacks sincerity, it's also soon to get penalized in upcoming indexing activities.

If she was doing this right she would leave the pitch off the end of the article and provide a simple hint over to her services that exist on a non-sensationalized pitch page.

The change would add a level of sincerity to her article and leave it conveying the sense of authority she's trying to project while showing a level or respect to the reader by making them the target or the piece. Ultimately this piece is clearly targeted to bots, not people and that is why it is poorly executed. At the end of the page when I realized I had been successfully bated to read the article there was zero percent chance of me clicking any other page on that site.

I enjoyed the article at first but she invalidated the positive experience with the pitch for her seminar at the end of the piece which just led me to discount the entire article as nothing but SEO bait for Google. Frankly it was irritating enough that I felt compelled to bitch about it in a comment...

Take this as an example of how not to do a sales pitch blog post in 2015.

Sooo... what we're really saying here is that we really don't know.

I think you're presuming too much. As long as your code is documented and you're willing to release all potential IP claims as part of the sale I can imagine there would be someone interested in buying this straight out. You might even be able to sell them some kind of limited support/consultation agreement where you don't do code but can answer questions for a fixed period of time. It's not like you're doing some kind of business exit strategy. You're just selling off an asset from your portfolio.