QA
Get flash to fully experience Pearltrees
Performance Testing
We Recommend These Resources There seem to be some misconceptions regarding the Java Heap size arguments. For those who don't know, Java is peculiar in the sense that you have to specify the amount of memory you want your program to use, before you run your program. If you fail to do so then depending on the version and implementation of the JVM, your program will only be allowed to use a fraction of your computer's total RAM. This is the reason why you might get an OutOfMemoryError even if your machine has 24gb of ram and you know your Java program needs way below that amount of memory.
Misconceptions regarding Java heap size arguments
Requirements: Not Just for Application Projects
Requirements: Not Just for Application Projects Seventy percent of projects that fail are due to poor requirements, no matter what kind of IT project it is. Applying a reasonable requirements discipline often faces more resistance than with business automation projects. Why do we doubt ourselves? Talk about requirements and most people jump to the requirements work done for business application projects. But what about internal IT improvement projects or infrastructure projects?
Four ways to manage code, simplify projects
We support a number of coding repositories and workflows on Assembla. This article is a high-level overview of the alternatives. Some material about code contribution comes from a previous article Agile next generation: Three ways to go beyond scrum . Innovation in development relies on changes in the way developers deliver code, which is closely tied to the evolution of code repositories. There are many code management workflows, but most fit into four categories. Lock : Years ago, developers used to copy a part of the code base to work on, and formally or informally lock it, so that other developers wouldn't work on that part.
The Java User Group Lausanne (JUGL) organized last week an evening where Java quality analysis tools were compared side-by-side, analyzing the same open source project. More than 100 participants came to watch the presentations done by * Coverity * Headway Software * Parasoft * Sonar * XDepend Each tool was presented during 20 minutes, analyzing the same code base: the version 2 of the IceScrum open source project management tool. All tools have a different approach to quality, there are however a lot of common defects that are targeted by most of them like unit testing coverage, code duplication, dangerous code, code dependencies, coding standards respect. The evening started with Sonar, the only open source tool of this presentation. Its aim is to produce quality dashboards (technical or management) of software development projects.
Quality Analysis Evening with the Java User Group Lausanne | Software Development Musings from the Editor of Methods & Tools
Thoughts on Code Commenting
One of the "behind the scenes" ways of organizing your code and making it maintainable is code commenting. Whether you're coding in Java, CSS, JavaScript, PHP, or any language for that matter, code commenting plays an important role in making your development life easy. I thought I'd just share some off-the-cuff thoughts about code commenting. Don't leave to-do lists within your code comments, especially if you're delivering code to the client. You think you're going to remember to remove it...you wont.
Do You Enjoy Your Code Quality?
Rally Software Seattle, Boulder, or Raleigh Do You Enjoy Your Code Quality?
i 14 Votes This time I am sharing my discussions about how all these high traffic sites handle multiple users simultaneously. The discussion is not specific to a certain web site but rather was related to a set of guidelines that every developer should follow to make such tasks easy.
How websites handle multiple users simultaneously? « My Blog – My Thoughts
All-In-One Code Framework Coding Standards
I recently stumbled upon the All-In-One Code Framework project on CodePlex. It’s a very impressive collection of samples in C#, VB.NET, and C++, and most of the samples I’ve seen are of superb quality. One thing that’s cool about this project is that they publish their own set of coding standards . It’s a very elaborate 87-page document written in the “ Framework Design Guidelines style” with “DO” and “DO NOT” items sprinkled liberally throughout the guidelines.
What is the simplest technique you can apply to write cleaner code? Clean Code by Robert C. Martin is a very good book that focuses exclusively on writing cleaner code.
Cleaner Code with One Simple Technique
The most maintainable codebase that I worked with grew at a rate of about ~10 KLoC per month, every month. There wasn’t a large team there, it ranged fro 3 – 6 people. This is the project that I think about whenever I had to talk about good code bases. It is a WebForms project (under protest, but it is). What make it maintainable? Not the WebForms part, which wouldn’t come as a surprise.
Maintainability, Code Size, and Code Complexity
Test Path
Beautiful Code