Posts Tagged 'Michael Mah'

A Seven Year Retrospective

 Posted by on Sep 30, 2011  1 Response »
Sep 302011
A Seven Year Retrospective

I felt like a psychiatrist in October 2004. An endless stream of strangers was coming to my office to complain about the software I was responsible for. I did not need to ask the classic question “How did you feel about the software bug?!” – I was proactively advised how the person calling upon me – every person! – felt about it… Some actually reverted to Hebrew (my native tongue) in order to make doubly certain I did not miss any nuance of their disappointment, dismay, despair, anger, anxiety and anguish. The only saving grace I had was that I have just been hired to turn the product around. It was a little difficult to implicate me Read more

Feb 062011

The fast rise of software talent marketplaces like oDesk and uTest represents a profound transformation. Software is no more a world of places – Silicon Valley, Seattle, Bangalore, Krakow or Tel Aviv. Rather, software is fast becoming a world of work streams. These streams are tied together through social networking and collaborative techniques in which virtual team spaces replace the site, the conference room, the metaphorical shelf on which the software artifacts are stored… and the water cooler. Three trends drive this transformation in software from a world of places to a world of streams: Shortage of talent. Have you recently tried to hire highly skilled programmers in areas such as mobile applications or cloud Read more

Mar 222010
Quantifying the Start Afresh Option

Source code analysis techniques have progressed to the point that answers to numerous tricky questions about software investment dilemmas can now be answered through quantifying technical debt.  Consider, for example, the following scenario: You are a venture capitalist. One of your portfolio companies has been working for a few years now on a promising software application. Various surprises with respect to schedule and functionality have been sprung on you along the way. The company asks for additional $2M to complete development and bring a 500K lines of code to market. Using technical debt quantification techniques you find the technical debt amounts to $1M. You are not at all comfortable “paying back” the technical debt in addition Read more