Everything is difficult until it becomes easy

Article#: 00036

Date: 2020-10-23

Author: Radim

Only at the end of the project we know how we would have started and executed the project better.
Because we know where we've gone and where we would have gone to do better.
We had to deal with small and large problems.
We somehow solved them.
It wasn't always easy and sometimes it cost more time and effort than we had imagined.
But we have learned to solve those problems.
It would be a lot easier now ...

We may not always have to find our solution.
Maybe the solution already exists.
Take a look around, ask an experienced colleague, get inspiration from previous projects.
Learn from ready-made solutions.
Think about why it was done this way and not another way.
Think about the applicability of the solution to your problem.

In the project plan, take into account the time needed to overcome some obstacles. There are usually some out and about.

It's more convenient when we can learn from smaller problems before the more difficult ones arise.
If possible, have the equipment or the system available already during development.
This gives you the opportunity to solve most problems in the development and testing phase before installing the devices or systems at the customer's facility.

Once you solve the problem, next time you encounter the same problem it will be easy. Describe the problem and write down how you solved the problem and why in this way. So that you or someone else can quickly find out how to fix this problem next time.

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

Related previous articles:

• Realize every good idea ASAP!
• Industrial evolution - Listen to your customers and follow new trends!
• Stay alert!
• Have an expert on hand!
• What does the customer need?
• Don't disappoint your customer!
• Ask questions!
• Focus on target!
• Avoid overly optimistic estimates!
• Sharpen your axe before you start felling!
• Don't hide any problem!
• Check the result!
• Keep it simple!
• Good communication is important
• Development is evolution
• Don't neglect and don't skip any step!
• Transparency and reliability
• From an idea to a consistent system

Related next articles:

• Keep the answers to the question "Why"
• Write a project diary!
• Don't make it worse!
• Define test scenarios and test cases continuously!
• Do the right things and do them right!
• Safety first!
• More than just start and stop
• I can see what you can not see
• Store email messages in the project folder!
• Do you really want to start with this?
• Is the way really the goal?
• Prepare a good project plan and keep it up to date!
• HMI and PLC applications should grow together
• Write down your best practices and processes!
• Set your goals for today, tommorow, this week ...
• Are the people planned for this task really available?
• Appoint a representative!
• Who knows it?
• Write and accept only readable code!
• Use a usefull styleguide!
• Functional and intuitive HMI
• Who will operate?
• Collect all the requirements and sort them!
• Why do automation projects fail?
• Project leader
• Learn from your journey!
• Design machines with a focus on user's abilities and needs
• Think critically!
• Are there also any disadvantages?
• A good concept = Complete set of suitable solutions
• Hardware concept
• Modular software architecture
• Machine modularization
• Knowledge gained from a completed project is priceless
• Variable names
• Visual modeling
• Documentation issues
• Safety relays versus safety PLC
• Design considerations for effective HMIS
• Diagnostic tools
• Version control system
• Maintain order in the program code
• An irreplaceable employee
• HMI - Don't overdo it with complex design
• Hidden dangers during commissioning
• The false illusion of rapid progress

Comment#: 00001

Date: 2020-11-05

User: Radim

"You must learn from the mistakes of others. You can't possibly live long enough to make them all yourself."
- Sam Levenson

Comment#: 00002

Date: 2021-01-20

User: Radim

"It is a big advantage in life to make the mistakes you can learn from as early as possible."
- Winston Churchill

Comment#: 00003

Date: 2021-02-11

User: Radim

You learn from mistakes, and it's much cheaper if they are not your own mistakes.

Comment#: 00004

Date: 2022-05-06

User: Radim

New problems occur in real operation that were not expected or experienced during development or test operation.
Then you are happy if you know the system / devices well, if you know how they work, how they are connected and controlled, etc. This know-how comes simply from working on the system, from solving smaller and larger problems...

Comment#: 00005

Date: 2022-11-30

User: Radim

During development, do not use other (preliminary) hardware than the one selected for production. You gain important experience with the hardware. You will find out whether the performance is sufficient and learn how to eliminate problems that arise during development. If the software development phase is carried out on the hardware designed for sharp operation, you will experience fewer unpleasant surprises after the machine is commissioned.

Comment#: 00006

Date: 2023-08-11

User: Radim

"How to eliminate fifty percent of your business worries.

Everyone who wishes to present a problem to me must first prepare and submit a memorandum answering these four questions:
1. What is the problem?
2. What is the cause of the problem?
3. What are all the possible solutions of the problem?
4. What solution do you suggest?

My associates rarely come to me now with their problems. Why? Because they've discovered that in order to answer those four questions, they have to get all the facts and think their problems through. And they've done that, they find in three-fourths of the the cases they don't have to consult me at all because the proper solution has popped out like a piece o fbread popping up from an electric toaster. Even in those cases where consultation is snecessary the discussion takes about one-third of the time formely required because it proceeds along an orderly, logical path to a reason conclusion."

- Dale Carnegie. Crescent News (1944). How to Stop Worrying and Start Living.
- https://www.youtube.com/watch?v=fKzlc_N2yxw (01:07:50 - 01:09:53)

Comment#: 00007

Date: 2023-08-11

User: Radim

"Basic techniques in analysing worry:
Rule 1 - get the fact. Half the worry in the wold is caused by people trying to make decisions before they have sufficient knowledge on which to base a decision.
Rule 2 - after carefully weighing all the facts come to a decision.
Rule 3 - once a decision is carefully reached, act, get busy carrying out your decision and dismiss all enxiety about the outcome.
Rule 4 - when you or any of your associates are tempted to worry about a problem, write out and anser the following questions:
a) What is the problem?
b) What is the cause of the problem?
c) What are all possible solutions?
d) What is the best solution?"

- Dale Carnegie. Crescent News (1944). How to Stop Worrying and Start Living.
- https://www.youtube.com/watch?v=fKzlc_N2yxw (01:12:50 - 01:13:50)

Comment#: 00008

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#: 00009

Date: 2023-09-11

User: Radim

Does it make sense to think about digitalization if we don't see any use case?

"If you don't see any practical use case or clear benefit for digitalization in your specific situation, it may not make sense to pursue it blindly. Digitalization should always align with your organization's goals and needs. Here are some considerations:

1. Assess Business Objectives: Start by identifying your organization's objectives and challenges. Digitalization should align with your strategic goals, whether it's improving efficiency, reaching new markets, enhancing customer experiences, or reducing costs.

2. Customer Demands: Consider whether your customers or clients expect or would benefit from digital solutions. If there's no demand for digital services, investing in them may not provide a return on investment.

3. Competitive Landscape: Analyze your competition. If your competitors are effectively utilizing digital technologies to gain a competitive advantage, it might be necessary to explore digitalization to stay relevant.

4. Cost-Benefit Analysis: Conduct a thorough cost-benefit analysis to determine if the potential benefits of digitalization outweigh the costs. If the investment doesn't offer a reasonable return, it might not be justified.

5. Resource Availability: Evaluate whether you have the necessary resources, including financial resources, technical expertise, and staff training, to implement and sustain digital solutions effectively.

6. Future Growth: Consider the scalability of your organization. Even if you don't currently see a clear use case for digitalization, it's essential to think about your organization's future growth and whether digital technologies could play a role in that growth.

7. Technology Trends: Stay informed about industry trends and emerging technologies. While there may not be an immediate use case, technological advancements could create new opportunities down the line.

8. Customer Feedback: Engage with your customers or stakeholders to gather feedback on their needs and preferences. They may provide insights that could uncover potential use cases for digitalization.

9. Pilot Projects: Instead of a full-scale digital transformation, consider starting with smaller pilot projects to test the waters and assess the feasibility and impact of digital solutions in a controlled environment.

10. Consult Experts: Seek advice from digital transformation consultants or experts in your industry. They can provide insights into potential use cases and help you determine if digitalization is appropriate for your organization.

In some cases, it may indeed be the case that digitalization doesn't make sense for your organization at a given time. However, it's essential to regularly revisit this assessment as technology and business landscapes evolve. What might not be relevant today could become essential in the future. Ultimately, the decision to pursue digitalization should be guided by a thorough understanding of your organization's unique needs and circumstances."

- https://chat.openai.com (Does it make sense to think about digitalization if we don't see any use case?)

Comment#: 00010

Date: 2023-09-13

User: Radim

Often the person who knows the answer or the right way is closer than you think. All you have to do is ask.

Comment#: 00011

Date: 2023-10-04

User: Radim

"Never discourage anyone who continually makes progress, no matter how slow."
- Plato

Comment#: 00012

Date: 2024-03-25

User: Radim

Remove the "ballast" from the program!

Only include things in the program that are really needed. Unnecessary parts of the code in the program become obsolete, untested, raise unnecessary questions and are a source of ambiguity.

Sometimes it is a good idea to try more than one way in practice to find out which way is the best. However, once we have decided on a particular approach, it is important to consolidate our methods and remove the outdated ones. By removing "ballast" from the program, we eliminate potential sources of confusion and improve the overall quality of the code.