...and What If You Are Just a Small Planet at the Edge of the Milky Way

Table of Contents

I recently had a conversation with my colleague about the importance of having a domain expert available in a project to clarify domain-specific questions.

In most cases, your work is more buggy and costly without access to such a person, I said.

But what if the product is not so important in the context of the whole company (a big insurance corporation, for example)? And it will be replaced by another project within two years. Yet it must be maintained and developed during this time to keep the business functioning in this area. Then the business is not so eager to dedicate a valuable domain expert for this case… And then the team is left wandering, looking for good domain answers, but this is included in the cost, my colleague replied.

You might be right, I responded.

(Of course, I could have attempted to convince him that people may become unmotivated or frustrated, but what difference does it make if the project is not that important for the business, and from a business perspective, there is no significant reason to become highly involved?)

It may sound sad, but frankly speaking, not everyone works on first-class projects, the shining stars in the sky, where everyone is excited just to think about them. In such cases, just do your work in a way that you can be proud of, with as much craftsmanship as possible, or consider changing your job.

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

Natural Course of Refactoring online on InfoQ

I am so delighted that the article about Natural Course of Refactoring is live. It is a very simple, yet powerful idea about refactoring (but not easy after all) and I hope this way it will reach more people than ever before. So please retweet it and share it wherever you can.

Read More
Systematic Approach to Automated Software Testing with Vertex Testing

Systematic Approach to Automated Software Testing with Vertex Testing

Many automated test suites suffer from complexity and maintainability issues. In this article, we examine common testing pitfalls and introduce Vertex Testing—a structured approach that enhances software testing practices by focusing on domain behavior.

Read More

Why Agile Fails

Introduction

Implementing a methodology from the Agile family is not at all easy. The problem usually lies in management, who upon superficially understanding what it’s all about, perceive the new method as a promise that from now on, everything will magically work better. It doesn’t matter if we have subpar team members and adhere to the principle that “any specialist can be replaced by a finite number of students.” It doesn’t matter if there’s complete disregard for knowledge management and skill development in the team because there’s never time for that. It doesn’t matter if people working on projects are shuffled between projects—after all, it’s about interdisciplinarity, and everyone should know everything.

Read More