We are all filmmakers now, right? Just stick to the story and don't ruin for everyone, Doug.

Nearly 15 years ago I built a P2P torrent-style anonymized backup program, based on Reed-Solomon EC. At the time, disk sizes and internet speeds were against it.

Now, I'm wondering if I should resurrect it. Any interest in a open-source, cross-platform P2P backup program?

Speaking for myself, I've been through six different frameworks/versions of "data binding", starting with VB3, now all the way through AngularJS. I've got 20 years of similar examples in DBMSs, distributed protocols, GUI design, testing, requirements, etc.

It's not that I refuse to learn new technologies, because I've taken on new things every year that I've worked in this field. jQuery? Love it. HTML5, CSS transitions? B-E-A-utiful. Bootstrap? You betcha.

I do, however, refuse to make all the same mistakes and work through the same leaky abstractions and other problems just to try the new hotness. A great example is the NoSQL movement - now that Postgres supports JSON documents (and has had great K-V support for a while now), I'll be very happy to exploit those features without wrestling MongoDB or Firebase to the ground.

You had me at Feynman.

Came here to say essentially the same thing - GET REQUIREMENTS. No matter which road you end up choosing, the requirements will make choices much clearer, and their objective nature will give you a buffer against the business folks who agreed to them, but want the flaming logo on Wednesdays.

I did this a few years ago for a decent-sized telecom, that wanted to get rid of dozens of home-built systems in favor of telecom-specific ERP type software (usually called OSS for this industry). The RFP was a bust (no vendor selected), but those requirements guided the next 18 months of systems development, COTS adoption, integration and legacy retirement. In the end, even the business folks acknowledged that without the written requirements, they would not have been able to make any of the advances we made.

This is also known as "Bugs Bunny-ing" someone.

I see what you did there.

Hey, feels just like Reddit!

I was brought into my current job about eight years ago, ostensibly to bring PM and SDLC process to the wild west of application development in my department. The mainframers wanted nothing to do with process improvement, saying they had everything under control. The client/server and web folks gave me the "we're different, old rules don't apply" argument. I asked around, looked through old documentation, anything to get a feel for where this group was at and what they'd done. After about six weeks, I decided it was basically a green field and brought in your run-of-the-mill PMI-style project mgmt and basic SDLC. Nothing fancy, and pretty stripped down since most projects were in the $50K-$150K range.

Fast forward to this year. Management makes a sweet offer for early retirees, and they take the bait. In droves. One of the retirees drops a folder off on my desk as she's headed out the door. It says, "Blast from the past...thought you might enjoy this." It was a fairly complete PM and SDLC definition, from two years before I'd arrived. No one (including the manager who had hired me and given me the task) had offered this to me before, even though that manager's name was on the approvers list.

Now I'm not sure this was strictly age-ism, but might this problem be more properly defined as a "green-field" syndrome? That is, that people would rather bump into the same problem than have to listen to someone else who's already been there?