Archive for Process
Let’s distinguish between systems where the hazards of failure are material (critical) and those that are not. If it bugs don’t matter, they don’t matter. As the question (posed in a LinkedIn forum) asks about safety and security, we’re talking about critical systems.
There is a long standing debate in reliability engineering…
Read MoreHow Agile development is being eaten by the Testing BackBlob and what to do about it
Read MoreWe don’t need a miracle cure for rogue algorithms. More regulation will not prevent them. Proven software engineering and testing will.
Read MoreI’ve developed a systematic methodology to design a mobile app test suite and offer an online course that teaches this methodology. http://www.udemy.com/how-to-test-mobile-apps/ The course assumes manual testing, but is completely applicable to testing with any automated tool. Click here to view the course notes, which incude a list of specific…
Read MoreA few days ago, I participated in a panel discussion on open source tools for testing at the QUEST conference with the two founders of Selenium: Jason Huggins of Sauce Labs and Simon Stewart of Google.
Before the panel started we chatted a bit with the moderator. We couldn’t come up with…
Technical debt refers to aspects of a codebase are incomplete, deficient, obsolete, or buggy. This can occur for many reasons: insufficient time, uncertainty, omissions, poor workmanship, or poor management. This is termed “debt” because it will take additional time and money to correct, update, or revise.
Technical equity refers to aspects of a…
Technical Equity is the value that accrues when a software system is well-formed. Instead of burdening you with unnecessary excess cost, your codebase works for you. Technical equity pays dividends: you avoid wasted effort and the consequences of buggy releases, and gain the advantage of releasing sooner and/or with more features,…
Read MoreTechnical Bankruptcy occurs when technical debt overwhelms the maintainers of a software system. I’ve previously blogged about a case study: how the accumulation of poor development practices resulted in the business failure of highly successful Enterprise IT software company.
The technical debt metaphor provides a nice handle for a software development …
Through Google Circles, I happened to see David Welton’s very interesting reflection on the Tcl programming language (posted in 2010):
http://journal.dedasys.com/2010/03/30/where-tcl-and-tk-went-wrong/
About ten years ago, I chose to develop a commercial automated software testing tool with Tcl and Tk. This post explains that decision and its consequences.
Despite testing tools that tout “visual programming”…
In every software project where I’ve used some form of review process (formal inspections, walkthroughs, or reviews — for this post I refer to all as “reviews”), the gain has always justified the pain. Invariably, some developers really dislike this process, leading to tantrums reminiscent of Orange Country Choppers.
But I’ve regretted every time…
