Development Practices

Most Recent

Document All the Things Before Handing Off a Maintenance Project

Before handing off a maintenance project, here are items you should document or get from the client or the previous person who worked on it.

Development Practices

Code Quality Metrics Are Guides, Not Goals

Measuring your code quality with metrics can be a mistake. Instead, you can use the metrics as a guide — showing you potential opportunities to improve.

Development Practices

Better Documentation Through Low-Fidelity Diagrams

Low-fidelity diagrams generate more accurately documented systems than complex master diagrams. Here's how I use them on software projects.

Development Practices

Prepare Your Software for Growth: Create Boundaries

You can be prepared for system and team growth with preparation and a smart application of boundaries in your software project.

Development Practices

Making Changes in a World of YAGNI

In many agile development projects, code will need to change frequently, and clean code that is easy to understand is easier to change.

Development Practices

Ensure a Successful Continuous Improvement Engagement With These Activities

Regularly plan to do these activities to keep your project healthy between active phases of development in a continuous improvement engagement.

Development Practices

Why & How to Tackle Internationalization at the Beginning of a Project

Writing code to support localization at the beginning of the project can ease the addition of new languages and regions later on.

Development Practices

3 Tips for Handing Off a Large Project

Ensuring a new team can easily start doing effective work after you've handed off a project to them is important. Here are some ideas on how to do that.

Development Practices

Embracing Nullability for GraphQL APIs

Build an API that expresses uncertainty with nullable fields, and your frontend implementation can use those APIs to handle less-than-ideal data.

Development Practices

6 Things to Consider when Adding a New Project Dependency

Dependencies are liabilities, and not all of them are worth the risk. The next time you're deciding whether to add one, ask yourself these six questions.

Development Practices

Three Ways to Develop, #3: The Swarm

Getting more than two developers together in a "swarm" is a valuable tactic that can improve context sharing and team decision-making.

Development Practices

Three Ways To Develop, #2: Pair Programming

Pair programming is a very effective development approach. But knowing when to pair is just as important as knowing how.

Development Practices

Development category

Other Categories

Keep up with our latest posts.