InfoQ Homepage Programming Content on InfoQ
-
The Decision to Refactor
Refactoring is the process of changing a software system in such a way that is does not alter the external behavior of the code yet improves its internal structure. The idea of improving an already written code is appreciated in most Agile teams. Continuous improvement is is something that these teams strive for. However, improving the already existing code involves time and money. Is it worth it?
-
CodeRush Xpress for C# and VB for Visual Studio 2010
Microsoft has decided to continue licensing CodeRush Xpress for free for developers using the non-free editions of Visual Studio 2010. Developer Express has released the beta version of CodeRush 10.1.1, containing features related to code selection, code navigation, class/field/variable declaration and refactoring.
-
LINQ on GPU with Brahma
Brahma is an open source C# library that provides support for parallel computations running on a variety of processors. Currently, Brahma has a GPU provider but its modular structure allows using different providers for other types of processors. One C# method can contain both statements running on CPU and GPU without additional glue code.
-
The Complete List of Migration Issues Upgrading to .NET 4.0
Microsoft has published a complete list of issues migrating from .NET Framework 3.5 SP1 to .NET 4.0. The list contains changes in 6 domains: Core, ASP.NET, ADO.NET, WCF, WPF, and XML.
-
MonoMac Brings C# Development to Mac OS
The Mono team has created a binding for Cocoa API, one of the major application environments for Mac OS, facilitating developers the possibility to write C# applications for Apple’s operating system.
-
Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors
Today, the Akka team released version 0.7 of their actors framework for the Java Virtual Machine. Akka attempts to address future concurrency challenges with a solution relying on message based actors, software transactional memory and appropriate fault handling strategies. InfoQ talked to Jonas Bonér about the intent behind Akka, its current state and adoption, and future plans.
-
A Manifesto of Done
Alixx Skevington posted a Manifesto of Done as the beginning of a discussion thread, talking about the commitments team members make to each other about the quality of their work and clearly expressing their commitment to delivering business value through their code. Covering areas such as coding standards, usable code, unit testing and test coverage he emphasises the importance of quality work.
-
Marshal.ReleaseComObject Is Considered Dangerous
Paul Harrington, Principal Developer on the Visual Studio Platform Team, has written an explanation on why calling Marshal.ReleaseComObject() to dispose of a COM object from managed code is considered dangerous and recommends not using it.
-
CWE/SANS Top 25 Programming Errors
Common Weakness Enumeration (CWE), a strategic initiative sponsored by the U.S. Department of Homeland Security, has published the document 2010 CWE/SANS Top 25 Most Dangerous Programming Errors, a list of 25 code errors that lead, in authors’ opinion, to the worst software vulnerabilities.
-
To Comment or Not to Comment
Any developer has written at least one line of comment throughout his code. Some have written many comments in an attempt their code to be more explanatory. This article gathers some of the practices used in writing code comments.
-
Scala 2.8 Beta 1 Released
The long-awaited beta for the new Scala version 2.8 has finally been released. It includes many new features, like for example a redesigned collections library, named and default arguments, and a much improved Eclipse IDE.
-
JDK 7 Milestone 5 Includes Concurrency and Performance Updates, But Is Not Feature Complete
Sun's Java SE team recently released the Milestone 5 build of JDK 7. This was expected to be a feature complete release of Java 7 but is some way short of that. InfoQ takes a look at what has been added and some of the major features still missing.
-
Test Driven Development and the Trouble with Legacy Code
Alan Baljeu was trying to use TDD with his large, legacy C++ code base. He found that the principle of the simplest thing that could possibly work was causing him trouble with the amount of rework.
-
Dealing with Memory Leaks in .NET
Fabrice Marguerie, a software architect and consultant, wrote the article How to detect and avoid memory and resources leaks in .NET applications, published on MSDN. The article explains how memory and resource leaks can happen while programming for .NET and how to avoid them.
-
Uncle Bob On The Applicability Of TDD
Following up a pot-stirring blog where he asserted that "anyone who continues to think that TDD slows you down is living in the stone age", Bob Martin takes a stab at providing some deeper insight into the real applicability, role, and benefit of TDD.