The Hadoop Summit of 2010 started off with a vuvuzela blast from Blake Irving, Chief Product Officer for Yahoo. Yahoo delivered keynote addresses that outlined the scale of their use, technical directions for their contributions, and architectural patterns in how they apply the technology.
Steve Huffman, co-founder of Reddit, shares the main lessons he learned scaling Reddit from a small web application to a large social website.
Microsoft has had its successes and failures over time, and it has managed to come first with some products even if it came later in the game. Is Microsoft going to be as successful with Windows Azure as it has been with the Windows operating system? Or will it remain a niche player like Windows Mobile?
Jeff Atwood has recently lost two of his blog sites: Blog @ Stackoverflow and Coding Horror. He managed to recover the contents of both websites, but what lessons are to be learned from this event?
An IT services provider company has migrated an ERP application totaling 950,000 lines of VB6 code to .NET in 9 months.
John Moe discusses a range of approaches to SOA, including incremental (Guerrilla) SOA. This has caused a stir in the SOA community with representatives from vendors and consultancies alike trading value-based blows (for instance which is the greatest cost, software or people?) to try to illustrate the benefits of these (their) solutions.
Traditional management models don't tell leaders how to support their Agile teams without undermining their emerging self-organisation. Allusions to musical performance and "conducting the orchestra" abound - but not all are in agreement. Is the "conductor" model a good practice or an anti-pattern? In his TED talk, conductor Itay Talman shows that it may depend on what we think a conductor does.
Tathagat Varma, general manager with a large provider of IT management solutions, wondered whether Agile's productivity improvements could be linked to how it improves teamwork. His article analyses Agile values and practices by mapping them against Patrick Lencioni's business fable "The Five Dysfunctions of a Team."
What did a group of Agilists see when they "went to the gemba" in Japan to observe Lean in action? Here is a roundup of observations from bloggers and newsgroup writers on this spring's "Roots of Lean" tour to Japan, led by Mary and Tom Poppendieck. The tour visited both manufacturing and software organizations, and included Henrik Kniberg, Sune Gynthersen, & Gabrielle Benefield, among others.
Brett Taylor, founder of FriendFeed, describes how they overcame some limitations of MySQL to handle problems of scaling and database evolution by implementing a "schema-less" storage system on top of MySQL.
Challenges of Agile adoption and execution get amplified when working in a distributed mode. Distributed Agile brings its own share of challenges in terms of geographical separation, varied timezone, cultural differences etc. Killing a distributed Agile project is not very difficult.
A recent article makes a case for the REST architectural style using a Department of Defense’s project, called Net-Centric Data Strategy (NCDS), as an example. The authors argue that some of the core objectives of NCDS can be more naturally supported by the four basic principles of REST.
In this interview made by InfoQ’s Rob Bazinet during RubyFringe 2008, Dan Grigsby talks about programming and entrepreneurship, how a programmer can take his idea and transform it into a successful product.
Nestlés Nespresso SA division, which is headquartered in Paudex, Switzerland, recently announced the successful completion the first phase of their SOA initiative 'NesOA' in just six months! Optaros and MuleSource helped define and implement a new middleware architecture called Nespresso Open Architecture, or NesOA.
Developers commonly break user stories into tasks to facilitate distributing the implementation work across the team, and allow tracking of progress at a finer level of granularity. Unfortunately, a story can explode into a list of non-trivial tasks so large that the story is not deliverable by the end of the iteration. Ron Jeffries suggests: "Do stories as a unit, not broken into tasks."