587 karma · joined July 26, 2011
I wouldn't say it's a key profit area for them yet, and we also can't call it a success yet (as they haven't reported the total retail purchases).
[1] http://blogs.wsj.com/digits/2014/10/24/a-win-for-microsofts-...
Nespresso has lost nearly every attempt to protect exclusive control of the capsules [1]. In grocery stores, you can find many compatible capsules and a variety of flavors and choices.
[1] http://qz.com/200161/someone-is-finally-forcing-nespresso-to...
The article lost me on this point. I think Google and Facebook are trying to aggressively expand the reach of their original mission, and not acting out of fear that they will fail like RadioShack has.
I live in Europe now, and enjoy a wide variety of interesting regional apples. Whenever I return to the USA I'm disappointed by the selection and quality of apples available. Red and green. They look nice, but often are waxy and bland.
In my office in Zurich, we break out the electric fans during a hot day, and people take off their button shirts and walk around in flimsy undershirts. Most large stores have A/C though.
I honestly don't miss A/C at all, I remember living in NYC during heat waves, and dreading the shock transition from extreme hot to cold that happened when you entered or exited a building.
However, when you just want to find stuff fast, it's annoying to have to deal with Perl/CPAN or RVM/Rubygems, especially when the dependencies are not installed on your server/workstation.
That's why I've switched to silver searcher (ag) [2], as it can be installed with any OS package manager (brew, apt, yum).
[1] http://rak.rubyforge.org [2] https://github.com/ggreer/the_silver_searcher
As of today, we're in the process of ripping out all of our Cucumber tests and replacing them all with RSpec features.
In our largish company we found that product owners generally didn't care about reading Cucumber features. The definition of the products and how they works are defined in the agile boards and cards we write together, along with documentation and wireframes which live on our intranet.
http://oredev.org/2013/wed-fri-conference/art-and-code-with-...
At the start of this year, the company I work at had about six different CMS platforms. Many of the applications that used them were built on top of CMSs, and were tightly coupled to them. As for static content generators, we tried that. It really didn't scale, especially for dynamic content. Too many hacks, deploys, and hard to train people.
As of today, our team has switched nearly all public content for our company to LocomotiveCMS (http://www.locomotivecms.com/), and deployed a centralized multi-tenant system. In many cases, we use our Locomotive instances as an API, pushing content via the API or the command-line tool, wagon. The CMS then renders HTML templates (or even JSON), which are consumed by our applications via HTTP. Sometimes it's just a tiny part of a page, or sometimes entire mini-sites. As a result, most of our apps don't need to know about a database.
Whenever there's a change that requires a new model, or the addition of a field, it can be done quickly through the LCMS back-office UI (or the wagon CLI tool). We update the application(s) affected, and re-deploy. Non-techies can edit the content using the admin web UI in a familiar way.
In any case, it's been working really well for us. The CMS has become an API, a service, and a separate app, shared by many applications. We've become more flexible and efficient as a result, our web applications are no longer burdened by CMS frameworks or admin interfaces of their own. And we dont have to struggle with Sharepoint or Wordpress or any other nonsense.
It's been a fundamental shift in how we think about the CMS, and has scaled well across multiple projects.
I'll peek at the pull requests and see if my company might be able to contribute some help.
Maybe markdown + git + nice UI clients?