We've all been there. You're on a web-based project, and things are going well. At least, you think they are. The right people are selected for the appropriate functions, and everybody's clear on their roles. You've got a designer, a developer, a project manager, and business stakeholders who are driving the requirements. You've got interlocked programs that tie in with your initiative, and you've got a fairly constrained budget to manage to. The timeline is tight, but if everybody just does their job, you should make your dates. The initial requirements are gathered, stakeholder expectations are set, and the first set of deliverables -- comps that define what the end product should (generally) look like -- is due. But it doesn't get delivered. The comps seem stuck in a perpetual working state with the designer, as repeat revisions are created behind the scenes in consultation with other designers... out of sight of the other stakeholders and app
Official: IBM to gobble Red Hat for $34bn – yes, the enterprise Linux biz Well, this is exciting. I came across this announcement this morning while I was on my regularly scheduled exercise bike ride. I get up every morning and get on the bike for a while, checking email and the news. And what news is more intriguing to me, than the blending of a massive, (relatively) ancient technology behemoth with a 25-year-old Open Source champion. From a CycloPraxis conjecture standpoint, it's a pretty tasty combination. I mean, here you have the classic corporate giant that's pretty squarely placed in the Capitalizing/Enduring "quadrant", acquiring a company that's always struck me as an innovator, and certainly reads like an Author/Inventor culture, liberally sprinkled with a good dose of Building. A Glassdoor review of Red Hat says : I have been working at Red Hat full-time (More than a year) Pros - Wonderful environment where your coworkers actually li