Documentation: Enough Already! Not.

Mike McCoy Consulting, Other, Problem Solving, Soft Skills Leave a Comment

Documentation. I know we all hate having to create it. I don’t like writing it and feel like I always leave something out. However, our assumptions of what other developers should think we are trying to accomplish by our masterpieces of software are usually filled with potholes (sometimes big ones). The truth of the matter is that no matter how stellar your code or software is – if you’re the only one who understands how it works, it doesn’t do any good.

These are not paintings or sculptures that would live the rest of their days in a museum, untouched by human hands and just collecting dust as they run. In reality, documentation will be added to and changed as the information they describe evolves.

In this blog, we discuss two suggested strategies for the creation of useful and concise software documentation.

Strategy: Knowledge Transfer In Consulting Projects

Josh Green Agile, Consulting, Dev Methodologies, Soft Skills Leave a Comment

Imparting Knowledge And Preparing For The End Of A Contract

In this blog, I share an example of a consulting engagement that required significant knowledge transfer to new hires. We detail an approach for teaching Spring Batch to developers with no previous experience in Java or the Spring Framework.

The goal is to provide a real-world example of closing a contract, imparting knowledge with the client and their employees, and the potential issues faced in the process.

Web Development Business

Refreshing Your Scrum

Keith Shakib Agile, Consulting, Design, Dev Methodologies, Problem Solving, Soft Skills 3 Comments

Most of us now have some experience with Agile Scrum practices. Many of us have had years of practice on multiple processes. As a consultant, I have the opportunity to see many differences in how organizations implement and practice the most popular development process methodologies.

While the prescription for good practices is well-documented, many of us have lost our “mojo” at least once and seen many of the benefits of using the process decline.

In this blog, I will indicate some key points required to return to optimal agile performance. I will highlight three common pitfalls, some common causes of those problems, and reminders of how to get back to a high-performance Scrum implementation. Let’s dive in.

Web Development Business

Performing Technical Interviews For Consulting Clients

Clayton Neff Business, Consulting, Opinion, Soft Skills Leave a Comment

The situation will occasionally arise when we have gained enough respect and confidence from our clients that they will ask us to help them interview new technical people to join the team. As consultants, it’s important for us to be the person that our client needs us to be at the time, so we are definitely willing to help. But, needless to say, this situation must be handled with ‘kid gloves.’

Many managers are uncomfortable performing a technical interview in an area they do not feel competent in. Typically, that is when they will ask for your help in the interview process. As technical consultants, we should be able to provide useful feedback to them about the person’s apparent abilities. When it comes to the ‘soft skills,’ we want to ensure we’re on the same page with the client as to if we should limit the interactions to just the technical topics.

Whether you’re a consultant helping your client, or the client manager looking to fill your employee team, there are a number of topics that must be considered when searching for the right technical person. In this post, I will point out some useful topics to concentrate on while performing a technical interview– and why they are important questions to ask before hiring a new person to the team

Web Development Business

Technical Debt – Observe, React, Prevent

Keith Shakib Consulting, Opinion, Soft Skills Leave a Comment

The term “technical debt” was coined over a decade ago to help highlight a common problem in software development. Generally you can think of technical debt like this:

The cost of additional rework created by choosing an easy, shortcut solution now instead of the better approach that would take longer.

Delivering software to meet deadlines or functional goals that are wrought with technical debt is like buying items before you can afford them. Both practices can drastically affect your ability to reach your future goals, both long term and short term.

This article is a gentle reminder to recognize, fix, and avoid technical debt in your software projects.