In my last post “What’s next for Agile?”, I talked about alignment between the development team and the business, from the customer focus perspective. As I was watching “Agile is dead, long live agile” presentation by Jeff Sutherland, from Oredev 2010, I felt I needed to add something. When does agile work? According to Jeff,
Let’s take a look at the agile manifesto. It starts with: “We are uncovering better ways of developingsoftware” Next are the values. I’m not going to bother with the “right” side, which is of course the “dark side”. On the left we have: Individuals and interactions Working software Customer collaboration Responding to change All this
Yesterday I went to Agile Tour Israel. At the end of the day I was surprised, I didn’t think I’d enjoy it that much. Once again, being pessimistic saved the day! The event organizers did all they could to push agile and show it as mainstream. Cynical as I am, I was surprised to see
The answer is yes. Microsoft is killing off Silverlight. Don’t underestimate the truth said in the PDC keynote: Microsoft is going the HTML5 way. But this is not a review of the he said/she said MS is playing for the last week. It’s about the risks associated with selecting a technology, or making an architecture
Some people think that by blaming Microsoft, I’ve removed the responsibility of self development from the developers themselves. These are two separate things.Developers who want to expand their horizon, enhance their craftsmanship, will find ways to do that. And because there are so many sources, they will probably not get it just from Microsoft.But we
After the LIDNUG presentation, we stayed online to discuss unit testing experiences. A couple of things stayed with me from that talk. One: we’re (we developers) are obsessed with tooling and technology (you didn’t expect hard news here, right?). Our main focus should be about solving the business problem first. But, us geeks, we like
After my last post, I got some feedback, that I didn’t really answer the question in the title. So I’m going to fix that. Roughly speaking, 10% of developers are doing unit testing today (Let’s call them group A). Some 15% have heard or tried (B), and the rest don’t even know it exists (C).
Running the panel at the Typemock Academy was a great experience for me. (Read: I’ve got loads to learn about running a panel). We wanted to make things interesting, and picked a topic that at its heart not so controversial. But when you dig in, it really exposes a problem: If unit testing has been
Ayende wrote about getting from a small utility to… a small utility. Let me see – I developed (or was part of a team that developed):1. Utility (Those were the days…)2. Project3. Application. (This was a bigger project, which got bigger)5. Framework (I should have made a U turn here).8. Platform. (Made and designed parts.
Today one of the developers asked for a meeting with me to discuss some design issues. It’s been a while since I did one of those, but was very entertaining for me, and helpful and productive for him I hope. At the end of the session, I reminded of a question that came up during