Appoint a representative!

Article#: 00053

Date: 2021-02-18

Author: Radim

It is optimal when two people are working on a task and understand it, one with primary responsibility and the right to make decisions, and the other as a consultant, tester and representative.
Two people can discuss and optimize an idea.
Two people can find a more suitable solution because two heads are better than one.
A project where two people understand a task has a better chance of completing successfully if one person is no longer available.
The representative can review and test the work of the author.
The representative learns the main developer's skills and style.
In the end, both developers know exactly how the code works and why it was created that way.
The quality of the result is much better.

Pairing should vary between tasks so that each team member works with a different persons.
It's a great way to circulate knowledge and experience within the team.
Programmers get used to the way the other team members write the code and can easily familiarize themselves with it and make adjustments later if necessary.

© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).

Related previous articles:

• Are the people planned for this task really available?
• Set your goals for today, tommorow, this week ...
• Write down your best practices and processes!
• Prepare a good project plan and keep it up to date!
• Is the way really the goal?
• Do you really want to start with this?
• Store email messages in the project folder!
• I can see what you can not see
• Do the right things and do them right!
• Write a project diary!
• Keep the answers to the question "Why"
• Everything is difficult until it becomes easy
• Realize every good idea ASAP!
• Get and stay in the flow!
• Stay alert!
• Have an expert on hand!
• Ask questions!
• Assign tasks efficiently!
• Communication skills are extremely important
• Don't replace employees in the middle of the project!
• Develop a sense of responsibility!
• Recruit and retain the best employees!
• Get the things done with a small, motivated team!
• Focus on target!
• Think on paper!
• Avoid overly optimistic estimates!
• 9 women can't make a baby in a month
• Sharpen your axe before you start felling!
• Understand - Agree - Be Identified - Believe
• Don't hide any problem!
• Check the result!
• Don't leave a work package half-finished!
• Don't neglect and don't skip any step!

Related next articles:

• Who knows it?
• Write and accept only readable code!
• Use a usefull styleguide!
• Project leader
• Learn from your journey!
• Think critically!
• Modular software architecture
• Machine modularization
• Variable names
• Visual modeling
• My boss was a hero
• Version control system
• Maintain order in the program code
• Keep everything you need together
• Dedicated employees
• An irreplaceable employee
• Hidden dangers during commissioning
• The false illusion of rapid progress

Comment#: 00001

Date: 2021-12-05

User: Radim

"In smaller projects where one developer can work on a component, we face a certain dilemma: Is it better to entrust the entire development of the component to one person or to distribute analysis, programming and testing among several people? In general, the first option is a little more efficient, but riskier. When a person is working on a task, he/she doesn't need to communicate with anyone, only he/she understands that component, and when he/she is not available, any change can be a big problem. If, on the other hand, several developers take turns on a single component, it is much more likely that problems will be identified and more team members may be able to work with the component, so this option is generally more appropriate."
Translated from:
- Petr Paleta. Computer Press (2003). Co programátory ve škole neučí.

Comment#: 00002

Date: 2022-09-14

User: Radim

"Pair programming helps us not only to avoid mistakes and develop high-quality software, but also to spread knowledge and become even better together."
- AUDI AG

Comment#: 00003

Date: 2022-09-14

User: Radim

"Pair programming is an awesome working method, not only to create high quality software but also to share your passion and spirit with your colleagues."
- Maximilian Zuleger

Comment#: 00004

Date: 2022-11-14

User: Radim

"Conduct code reviews. "Four eyes see more than two. That's why you should let other developers review your source code on a regular basis. Pair programming, on the other hand, a technique where two developers write code together for longer periods, isn't for everyone and is often not needed. But complicated, important or security related code greatly benefits from code reviews and will improve your code quality a lot.""
- https://stackify.com/software-testing-tips/

Comment#: 00005

Date: 2023-07-11

User: Radim

"New risks are also emerging in automated production, because who will restart a plant or even just a machine if the staff responsible for it at the time of shutdown are no longer working in the same plant. The transfer of knowledge, for example about the last software versions or settings, becomes indispensable. If you do not have the processes and the right solution in place, you risk everything. At this point, trends such as deploying increasing amounts of robots can only help to a limited extent, because even robots are dependent on updates and a certain level of maintenance."
- Curated by Statista, supported by octoplant by AUVESY-MDT. No Fatalism in Manufacturing. Exciting Insights from Leading Studies. (Page 5)
- https://info.auvesy-mdt.com/hubfs/Statista%20ePaper%20EN%20-%20AUVESY-MDT.pdf

Comment#: 00006

Date: 2023-07-25

User: Radim

"Yes, it absolutely makes sense for the boss to ask employees how they would solve a problem. In fact, it is a highly beneficial and strategic management approach for several reasons:

1. Employee Empowerment: When the boss asks employees for their input on problem-solving, it empowers them and shows that their opinions and expertise are valued. This can boost their confidence and motivation, leading to increased job satisfaction and a stronger sense of ownership over their work.

2. Enhanced Problem-Solving: Employees at various levels of the organization bring diverse perspectives and insights. By involving them in the process, the boss can tap into a collective intelligence that can lead to more comprehensive and innovative solutions.

3. Higher Engagement and Morale: Employees are more engaged and committed to their work when they feel that their voices are heard and their ideas are considered. This heightened engagement can positively impact overall team morale and productivity.

4. Building Trust and Collaboration: Seeking input from employees fosters a culture of trust and collaboration. It encourages open communication and breaks down hierarchical barriers, enabling a more cooperative work environment.

5. Identifying Strengths and Skill Development: Asking for employee input can help the boss identify individual strengths and skills within the team. It provides opportunities for employees to showcase their abilities and may lead to their professional development.

6. Better Decision-Making: Involving employees in problem-solving can lead to better decision-making. It allows the boss to access a wider range of information and insights, reducing the likelihood of making hasty or uninformed choices.

7. Adapting to Change: Employees who are involved in the problem-solving process are more likely to embrace changes resulting from the chosen solution. This is because they feel a sense of ownership over the decision and are more invested in its success.

8. Continuous Improvement: Encouraging employees to participate in solving problems promotes a culture of continuous improvement. It fosters a proactive approach to addressing issues and challenges, which can lead to long-term organizational growth.

Overall, asking employees how they would solve a problem is not only sensible but also a strategic and effective leadership practice. It can lead to increased collaboration, employee satisfaction, and improved problem-solving outcomes for the organization as a whole."

- https://chat.openai.com (Does it make sense for the boss to ask the employees how they would solve the problem?)

Comment#: 00007

Date: 2023-08-17

User: Radim

Why is there never enough time to do it right the first time, but always enough time to do it over?

"The saying "There's never enough time to do it right the first time, but always enough time to do it over" reflects a common observation about human behavior and project management. It suggests that people often rush through tasks or projects initially, hoping to save time and effort, but end up making mistakes or producing subpar results. As a result, they eventually need to invest more time and resources to fix those mistakes or redo the work properly.

There are several reasons why this phenomenon occurs:

1. Underestimation of Complexity: People might underestimate the complexity or difficulty of a task or project at the outset. This can lead to inadequate planning and allocation of resources, resulting in mistakes or oversights.

2. Pressure to Meet Deadlines: There is often pressure to complete tasks or projects quickly to meet deadlines. This can lead to shortcuts being taken or important steps being skipped in the interest of saving time.

3. Lack of Attention to Detail: When rushing through a task, individuals might not pay enough attention to details, leading to errors that require corrections later.

4. Overconfidence: Sometimes, people might overestimate their abilities or knowledge, leading them to believe they can complete a task quickly without proper preparation or diligence.

5. Incomplete Information: In some cases, tasks or projects might be started without having all the necessary information or requirements. This can lead to incorrect assumptions and decisions.

6. Limited Resources: Constraints on resources such as time, money, or manpower might force people to cut corners initially, with the intention of fixing things later when more resources are available.

7. Learning Curve: Sometimes, tasks involve new skills or technologies that individuals need to learn along the way. Initial attempts might be suboptimal as people are still acquiring the necessary expertise.

The saying serves as a reminder that investing the necessary time and effort upfront to do a task properly can save more time and resources in the long run. Proper planning, attention to detail, and thorough execution can help prevent mistakes and the need for redoing work.

However, it's worth noting that the saying is not universally true. In some cases, rushing through tasks might yield acceptable results, and redoing work might not be necessary. It all depends on the nature of the task, the level of expertise involved, and the specific circumstances."

- https://chat.openai.com (Why is there never enough time to do it right the first time, but always enough time to do it over?)

Comment#: 00010

Date: 2023-10-18

User: Radim

"The later in the development cycle we discover a bug in the software, the more expensive it is to fix."

- https://www.linkedin.com/pulse/unit-testing-world-industrial-automation-jakob-sagatowski/?trackingId=8Il2af6t8cNMxCT2pRn76Q%3D%3D

Comment#: 00011

Date: 2024-01-05

User: Radim

Let's speed things up!

One man needs one hour to dig a hole 1 meter deep, 1 meter wide and 1 meter long. How much time does it take if you engage 10 men?

ChatGPT: "If one man can dig a hole that is 1 meter deep, 1 meter wide, and 1 meter long in one hour, and you have 10 men working simultaneously, you can divide the time by the number of men to find the total time it takes for the group to complete the task.

So, it would take 1 hour / 10 men = 0.1 hours (or 6 minutes) for the group of 10 men to dig the hole."

Do you agree with ChatGPT's answer?