Pre-ECM Project Checklist: Object Storage Decision

We’re going to add one more item to our pre-ECM project checklist:

1) Where should we store our content?

Database storage used to be expensive.  In the 1950’s, the cost per megabyte of storage exceeded $10,000/MB.  Today, the cost has dropped to a few cents.  Not only have storage costs dropped, so have memory costs as they have followed the same price drop as storage.  Taking advantage of lower costs; most DB manufacturers have begun offering high performance in memory databases (IMDB – In-Memory Database).

From an ECM perspective; because of the higher database costs, content storage solutions were designed to use databases to store only the metadata or the index values associated with content, and the actual files and documents were stored on cheaper file storage devices.   While lowering costs, this approach meant that ECM solutions were forced with managing, synchronizing, backing up, and designing applications where index values were one place and the actual documents, audio/video files were somewhere else. Continue reading

Putting Together an ECM Project Team Part 3

Part 3 – The Project Team

In previous blogs on this same subject, we have discussed the role of Executive Management in the overall Project Team effort.  And what elements from the  internal organization would likely comprise an effective team.   In summary, vibrant and effective executive leadership is likely to be critical in solidifying the vision for the project.  The target of effort to achieve project acceptance and enthusiasm is cascading in that the focus of executive leadership is middle management.  The components of a project team may be different for each organization or type of organization – whatever best suites the particular organizational structure, and what special considerations there might be in the project (i.e. does it involve web content, collaboration, integration with ERP or SharePoint environments, etc.).

Continue reading

Moving To The Cloud

For some interesting reading, range about the Internet for articles detailing the way the software world has changed in the past few years with the success of companies like Facebook and similarly ubiquitous, social-node technologies. Those companies have fostered the advent of the DevOps strategy, which is more a paradigm shift in corporate culture than merely a mechanical development/quality assurance/deployment strategy, and it demonstrates a new way of thinking about deployment scaling using the cloud (with an unbelievable number of servers available) while maintaining an aggressive development schedule. Sprint-cycle application development and cloud-based deployment are the order of the day for these newer entities. No longer does dev sit in a development cycle of a year or more, but rather a cycle that is measured in months at most, or weeks – even days. Getting customer-requested features quickly into the product and out to the customers is still job one, but – Oh, hey! – the difference in implementation! Ben Horowitz Article “How Software Testing Has Changed”
Continue reading

Please don’t make this mistake in your business. It will RUIN you.

This is so true…lest we forget the importance of feedback, especially from our customer.

Please don’t make this mistake in your business. It will RUIN you.

by Derek Halpern | Follow Him on Twitter Here

Every now and then, you stumble on something that makes you want to hit your head against the wall.

And it’s often when people make a large, glaring mistake. A mistake that should be self explanatory, but they make it anyway.

Here’s the full story…

Over on Facebook, I republished my video about why I think discounting is for idiots. And someone shared their opinion of my video:

bob

Now this is remarkable.

First, let’s talk about the big elephant in the room. They tell me I’m an idiot, and that they suggest businesses LIE to their customers.

But that’s not even the main point.

Instead, they’re not paying any mind to what I’m sharing because they don’t agree with it.

I’m not surprised by this though. There’s something known as selective exposure theory in psychology, and the long and short of it is: people look for information that affirms their pre-existing beliefs instead of contradicts them.

Now here’s the thing:

The mistake I’m sharing with you today has nothing to do with discounting. And it has nothing to do with lying.

Instead…

When you’re running your business, you should NEVER – and I mean NEVER – shoot down the advice of other people. Even if you think it doesn’t apply to you. Even if you think the other person is wrong.

Now this doesn’t mean you should believe everything you read.

Far from it.

I’m cynical. And skeptical. And everything I read, I take with a grain of salt. However, no matter how smart or dumb people sound, I always approach every scenario with the mindset of, “What can I learn from this?”

That’s why I read books about art history, copywriting, memoirs of fashion executives, and more.

Even if something doesn’t apply to me, I make it apply.

And that’s the secret.

If someone presents something to you that contracts what you know, you don’t have to change your mind and believe them. But you should ask yourself, “What do they know that I don’t?”

Even in this example, maybe they know something about discounting that I don’t. And even if they don’t, I still used their comments as a teachable moment for you.

So from this point forward, I implore you to never make the mistake this person made. I want you to use every experience as an opportunity to learn something new. Because in my experience, the best ideas comes from the dumbest things.

And I don’t want you to miss out on any of it.

Now here’s what I want you to do…

What’s one comment or critique you’ve received in your business (or life) that you didn’t agree with. How can you turn that into a teachable moment or a lesson? Leave a comment.

You can read the original article here.

Best Regards,

Robert Hughet
Quality Assurance Mgr.
ImageSource, Inc.

Building Out Distributed Apps (Big Data)

Yesterday, I attended a webinar by O’Reilly on how to reduce the pain of building out distributed applications. The focus was on scalability, which makes sense, since this is why you would want to distribute your applications.

Apart from the host’s unfortunate resemblance to Little Lord Fauntleroy, there was some interesting observations to be made. To wit:

Continue reading