Don't neglect and don't skip any step!
Article#: 00003
Date: 2020-04-11
Author: Radim
Project tasks have to be done in a reasonable order.
Following tasks depend on the previous tasks.
If a previous task has not been completed or has not been performed properly, mostly some of the following tasks can also not be performed properly.
The responsible person (software developer) may not have been able to carry out the task properly due to time pressure or some incompetence.
"A poor brick gets built into the wall."
This later leads to repeated problems in the project.
After the cause of the problems has been found, not only the bad module but also some other dependent modules need to be adjusted to solve the problem.
If you invest too little time or too little effort to get the thing working properly for the first time, later you will have to invest a lot more time and effort to correct the things!
© Radim-Automation, 2020–2026. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).
Related previous articles:
Related next articles:
- Development is evolution
- Don't leave a work package half-finished!
- Introduce the terminology and standardize it!
- Everything is difficult until it becomes easy
- Do the right things and do them right!
- Safety first!
- More than just start and stop
- I can see what you can not see
- 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
- Abbreviations
- Machine modularization
- Knowledge gained from a completed project is priceless
- Variable names
- Choice of programming language
- Visual modeling
- Event logger as the very first function implemented in the program
- Diagnostic tools
- My boss was a hero
- Version control system
- Keep the documentation up to date throughout the project
- Maintain order in the program code
- Make backups, make small changes and test a lot
- Hidden dangers during commissioning
- The false illusion of rapid progress
- How long will a failure keep our production down?
Comment#: 00001
Date: 2020-06-17
User: Radim
It is better to make a floor in the room before we bring the furniture, and not the other way around.
Comment#: 00002
Date: 2022-10-31
User: Radim
"Disciplined testing and commissioning procedures executed by qualified resources are critical for safe and efficient startup. Shortcuts here inevitably lead to ongoing operational problems, costing many times the minimal savings from reduced commissioning time."
- https://blog.isa.org/industrial-automation-projects-challenging-management
Comment#: 00003
Date: 2022-11-16
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#: 00004
Date: 2022-11-30
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-06-08
User: Radim
"Today, technical debt, also known as tech debt and code debt, usually occurs when development teams choose to write speedy code while building new features of a software development product. Speedy code delivery can help your team meet deadlines, and the debt you accrue may be worth it, though it could also lead to negative outcomes if managed incorrectly. These negative outcomes aren’t always avoidable once the decision to accrue technical debt has been made."
- https://asana.com/resources/technical-debt
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-10-04
User: Radim
"Never discourage anyone who continually makes progress, no matter how slow."
- Plato