Restructuring Work Practices: The Role of Clean Code and Unit Testing in Professional Growth

Deciding whether to quit your job is a significant decision and should be based on several factors. Here are some considerations to help you think through your situation:

Work Environment

Evaluating the overall work environment is crucial. Is it generally supportive, or are there systemic issues? In many cases, issues stem from a single boss, which can often be addressed through open communication and collaboration. Discussing your perspective with your boss about the importance of clean code and unit testing can lead to a compromise or better understanding.

Value of Clean Code

If you believe in the importance of unit testing and clean code for the long-term success of your projects, it is worth discussing these practices with your boss. Often, a thoughtful discussion can lead to a mutual understanding and a more balanced approach. Providing concrete examples of how these practices benefit the project can also help in changing attitudes.

Career Goals

Consider how the current position fits into your long-term career goals. If you feel that the current environment is hindering your growth, it might be time to explore other opportunities. However, consider whether the lack of these practices is the only factor or if there are other aspects of the job that could still be beneficial.

Job Market

Assess the job market in your field. If there are many opportunities available that value these practices, it might be easier to find a new job that aligns with your values. Researching companies that prioritize clean code and unit testing can also provide a clearer picture of your career prospects.

Personal Satisfaction

Reflect on your job satisfaction. If the lack of unit testing and clean code is causing significant frustration, it may affect your overall happiness and productivity. Personal satisfaction and well-being are essential components of a healthy work-life balance.

Alternative Solutions

Before making a decision, consider proposing a pilot project where you can implement these practices. If successful, this might influence your boss's perspective. Demonstrating the benefits of clean code and unit testing in a real-world scenario can be incredibly persuasive.

Conclusion: Weighing the Pros and Cons

Ultimately, weigh the pros and cons carefully. If you decide to leave, ensure you have another opportunity lined up or a plan for your next steps. Finding a position that aligns with your professional values and supports your growth in the long term is crucial.

Im a trained plumber and my boss who never plumbed in his whole life wants me to plumb with one hand behind my back. I told him that’s nonsense but he insists. Should I quit?

Yes, if it was like this, you should quit. However, the situation you described is not the case here. Let's assume that the situation is more similar to this:

I heard that clean code and unit testing are important things to do and I would like to learn more about them. However, my boss wants me to make quick progress on delivering my assignments. Should I quit?

No, in my opinion, that is not a proper reason to quit. However, you should strive to reach a skill level where there is no tradeoff between speed and clean, unit-tested code. To get there, start by working through the book called 'Clean Code' by Robert C. Martin.

Further Reading

Clean Code by Robert C. Martin