InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Five Habits of Highly Effective Software Developers

Posted by Floyd Marinescu on Aug 24, 2006

Sections
Process & Practices,
Architecture & Design,
Development
Topics
Programming ,
Training / Certification ,
Ruby ,
Methodologies ,
.NET ,
Java
Tags
OOP ,
Patterns
What are some of the code-level practices of highly effective developers? Robert Miller wrote a detailed article on  Java.NET covering 5 practices which could apply to any language, including minimalist constructors, methods with clear focus and intent, minimizing logic in mutating methods, and minimizing dependendies between behaviour methods.  Miller's article frames the practices as making developers more effective, and thus more profitable.

The habits, summarized below, are:
Habit 1: Constructor Performs Minimal Work. Ideally, its constructor will only load data into its instance variables using the constructor's parameters
Habit 2: Methods Clearly Convey Their Intent.
 Long and descriptive method names help developer teams quickly understand the purpose and function of their software.
Habit 3: An Object Performs a Focused Set of Services.
Each object in the software to be focused on performing a small and unique set of services. Objects that perform a small amount of work are easier to read and more likely to be used correctly because there is less code to digest.
Habit 4: State-Changing Methods Contain Minimal Behavior Logic.   Intermixing state-changing logic with behavior logic makes the software more difficult to understand because it increases the amount of work happening in one place.
Habit 5: Behavior Methods Can Be Called in Any Order. Ensure that each behavior method provides value independent of any other behavior method.

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

Note my reply on the site by Matthew Adams Posted
  1. Back to top

    Note my reply on the site

    by Matthew Adams

    It's over on the article's site:
    today.java.net/pub/a/today/2006/08/24/five-habi...

    --matthew

Educational Content

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.