Comments for It will never work in theory

Comment on Realizing quality improvement through test driven development by cheat black ops 2

cheat black ops 2 — Thu, 17 May 2012 13:08:46 +0000

You are a great blogger. Please keep it up. I cant wait to read whats next.

Comment on A decade of research and development on program animation: The Jeliot experience by IT application development

IT application development — Thu, 17 May 2012 11:47:03 +0000

Pipes is the best approximation I’ve seen to date of something that puts the power of the mashable web in the hands of everyday people. If you haven’t seen it, give it a try, and then round up some friends and create an open source clone using HTML5, processing.js, and similar tools.

Comment on Announcement: Empirical Software Engineering at American Scientist by open source IT solutions

open source IT solutions — Thu, 17 May 2012 11:37:56 +0000

A self-adaptive system changes its behaviour in response to stimuli from its execution and operational environment. As software is used for more pervasive and critical applications, support for self-adaptation is increasingly seen as vital in avoiding costly disruptions for repair, maintenance and evolution of systems.

Comment on Got Issues? Do New Features and Code Improvements Affect Defects? by php programmers

php programmers — Thu, 17 May 2012 10:49:13 +0000

Coverity Static Analysis’ best-in-class analysis engine identifies the most critical bugs in your C/C++, Java, and C# codebases, scaling to thousands of developers working across geographic boundaries, thousands of defects, and millions of lines of code in a single analysis.

Comment on A Survey of the Practice of Computational Science by php developers

php developers — Thu, 17 May 2012 10:45:27 +0000

Computing plays an indispensable role in scientific research. Presently, researchers in science have different problems, needs, and beliefs about computation than professional programmers. In order to accelerate the progress of science, computer scientists must understand these problems, needs, and beliefs.

Comment on Component reuse vs. snippet remixing by php development

php development — Thu, 17 May 2012 10:39:39 +0000

People have been building complex software for over sixty years, but until recently, only a handful of researchers had studied how it was actually done.

Comment on Realizing quality improvement through test driven development by SugarCRM Development

SugarCRM Development — Thu, 17 May 2012 10:04:02 +0000

I am very happy that i found this site. I have bookmarked this site to visit again and find out the new post. SugarCRM Development

Comment on A Review of “Code Simplicity” by Erik

Erik — Tue, 08 May 2012 18:16:50 +0000

“How do you specify a location in an e-book that doesn’t have page numbers?” The simplest answer for generic electronic documents [1] is that you quote an extensive enough amount that a simple text search turns up the relevant section. The need for specifying a location is peculiar to the non-searchability of paper media.

[1] I have no experience with ebooks, but if they are different something is very wrong with them.

Comment on A Review of “Code Simplicity” by Brooks Moses

Brooks Moses — Sat, 05 May 2012 19:04:38 +0000

On your comment on law 2: “Replace the word “desirability” with “value”, and this is simply the definition of net present value.”

That’s not actually quite true, as anyone who’s taken an engineering economics 101 course should remember — it’s the definition of net present value _if you assume that value tomorrow is exactly equivalent to value today_. Usually there’s a time-cost-of-money factor, so that you consider having a certain amount of money a year from now to be 95% (or whatever) as valuable as having it today.

I point this out, because I think that assumption is an error in the original; time-cost-of-value factors apply to program desirability and effort just as much as they apply to cash. This is an error I’ve seen many times — if I have a choice between releasing a good product now and spending half of the next five years fixing the architectural duct tape, or releasing a somewhat better product with no duct tape after a year of architectural redesign up front, Kanat-Alexander’s law would tell me that the latter is more desirable. In practice, it probably sinks my project because there’s no incoming revenue for a year and someone pursuing the other strategy is taking over the market.

Comment on A Review of “Code Simplicity” by Lauren Smith

Lauren Smith — Fri, 04 May 2012 03:39:43 +0000

Thanks for the excellent review. I agree the purpose of software is to help people. This book reminds me of another good read I just finished by John R. Fox entitled, Digital Work in an Analog World: Improving Software Engineering Through Applied Psychology. The author writes about the process of software development through a non-technical perspective and offers insight into techniques, teamwork and management. You can learn more about the book here: http://www.analogdevelopment.com/