In a recent news report CNN has revealed a translated Toyota memo which links problems of the car manufacturer regarding an electronic acceleration concern to a software issue. When even news magazines pick up such stories, this shows the growing importance of software for embedded systems.
According to a report by CAST Software, technical debt now costs a company on average $3.61 per line of code. The report's findings are summarized in this article and more discussion is presented from other thought leaders on the topic.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Who ever has wondered what kind of software is used by Santa Claus & Co, got a hint recently in youtube. This might irritate some software engineers who have assumed, Santa Claus would only use Open Source Software.
The Software Craftsmanship North America (SCNA) 2011 had a number of renown speakers including Corey Haines, Chad Fowlers, Uncle Bob, Michael Feathers, and others. We have created a digest of some of the ideas presented at the conference and shared by participants.
Mitch Harper, co-founder of BigCommerce.com, claimed in a recent issue of the Sydney Morning Herald that university education might be the wrong way to become a software engineer. According to Harper, a self-educated software engineer without an university degree: universities leave their students rather unprepared for the realities of being a software engineer.
On the 1st November software engineer and author John R. Fox has published his book “Digital Work in an Analog World”. According to its subtitle “Improving Software Engineering by Applied Psychology”, the book does not consider software engineering in practice. Rather, it is focusing on the psychological aspects relevant and practices relevant for engineers.
As announced on 18th August 2011, the Irish Software Engineering Research Center (Lero) has signed a €300.000 contract for a research project with the European Space Agency (ESA). Goal of the research activities is to provide a solution framework for future space missions.
Keeping up-to-date with software architecture can be a tough endeavor. Information is normally available within thick books or somewhere hidden in the Web. Another more entertaining way can be to watch clips available at video sites such as YouTube and Vimeo.
A discussion has been taking place on the LinkedIn Agile Alliance group questioning if "technical debt" is still a valid metaphor in today's global software development world. This discussion has surfaced a strong support for the effectiveness of the metaphor even after 20 years.
By definition a Manifesto is a public declaration of principles and intentions which describes the motives, reasoning and demands of a group. One of the more popular manifestos is the Agile Manifesto but there has been quite and epidemic since then.
There is a constant tussle between following Agile techniques and still managing to do enterprise architecture. While Agile development focuses on adjusting the design as more insight is gained, architecture establishes the technology stack and addresses quality attributes. Combination of the two is successful when agile techniques are leveraged to drive towards the desired architecture.
Developing apps that surprise and delight can seem like an illusive goal that is difficult to articulate or quantify. But in this latest presentation just posted on InfoQ Mike Lee, the software engineer that worked on projects like Delicious Library,Tap Tap Revenge and the Obama ’08 iPhone app, proposes an algorithm for making better apps.
In a recent presentation at SATURN 2011 Eric Richardson has drawn some analogies between architects in an agile environment and hurricane meteorologists. For example, both produce various forecasts respectively documents, use many kinds of data sources as inputs, and employ different techniques to acquire data. The question arises is: what can architects learn from meteorologists?
In lean manufacturing, the definition of inventory is pretty clear. It is the extra material, work in progress material and material queued up for the next bit of work. Lean emphasizes on reducing the inventory because there is always an inventory handling costs. In software development, often requirements are seen as inventory, what about the code?