Delicious

Clean Coders is all about educational videos for software professionals, by software professionals. They're unlike anything you've seen before. Add our code-casts to your library and watch Instantly! Watch as many times as you like.

The key to making programs fast is to make them do practically nothing. ;-)

These 11 proven practices for efficient, lightweight peer code review are based on a study at Cisco Systems using SmartBear CodeCollaborator. They can help you ensure that your reviews both improve your code and make the most of your developers' time.

International in scope and free for public use, CWEâ„¢ provides a unified, measurable set of software weaknesses that is enabling more effective discussion, description, selection, and use of software security tools and services that can find these weaknesses in source code and operational systems as well as better understanding and management of software weaknesses related to architecture and design.

Learning Rails for the first time should be fun, and Rails for Zombies allows you to get your feet wet without having to worry about configuration. You'll watch five videos, each followed by exercises where you'll be programming Rails in your browser.

Mike Lee considers that a software engineer makes great applications not because he follows good rules but because he has a better way of looking at the world and he learns from experience.

Code is inventory. It is stuff lying around and it has substantial cost of ownership. It might do us good to consider what we can do to minimize it.

Simply click the Syntaclet Bookmarklet and it will automatically apply language specific syntax coloring with line numbers to all the code on the page.

Here is a list of courses and innovative resources to help CS students, faculty, and instructors. These are examples of the training Google engineers use to learn new skills.

Nick Schrock presents how Facebook’s code evolved over time, explaining some new constructs – fbobjects, Preparables, Ents - introduced to address the complexities of a large social graph.

jSizer comes to the rescue. It is a small swing-based app which reads a jar file and produces a graph depicting packages, classes node hierarchy while effective coloring and shaping helps to differentiate each node based on some vital metrics.

JDepend traverses Java class and source file directories and generates design quality metrics for each Java package. JDepend allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to effectively manage and control package dependencies.

JSHint is a community-driven tool to detect errors and potential problems in JavaScript code and to enforce your team's coding conventions. It is very flexible so you can easily adjust it to your particular coding guidelines and the environment you expect your code to execute in.

The Little MongoDB Book; an ebook meant to help people get familiar with MongoDB and answer some of the more common questions they have.

This screencast demonstrates IDEA's static code analysis features and how to write your own rule using Structural Search & Replace. I'll give you a quick overview of IDEA inspections, show you how to use Structural Search, and then demonstate creating a new inspection and quick fix based on this search

These are notes gathered from talking with many friends at Facebook about how the company develops and releases software.

What is the most effective thing you have done that improved your programming skills? What would you recommend to others that want to improve?

Code quality metrics are an important part of maintaining a healthy project, and reducing technical debt. Integrate code quality metrics reporting into your CI builds - this allows better project-wide reporting, and also makes your code quality metrics much more proactive.

Google’s guava is one of the best, most useful all-purpose java libraries to come out in a long time. It’s surprising that it isn’t standard in most projects now

Roy Osherove discusses principles and practices that make teams more effective, successful and happy. Team topics covered: automating everything possible, buying/using/discarding tools, getting quick feedback, communicating without using meetings, building by feature not layer, code & tests reviewin