Check the result!
Article#: 00011
Date: 2020-05-03
Author: Radim
A good result usually appears only after several iterations.
In the project plan, calculate the time required for the few iterations.
After completing a task, check whether there is a way to optimize the result.
For example: adapt the result better to the requirements, simplify the solution, make the solution more transparent, make the system more reliable, etc.
If yes, do it!
Later you will be glad that this part no longer needs to be optimized.
© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).
Related previous articles:
Related next articles:
- Don't hide any problem!
- Avoid overly optimistic estimates!
- Focus on target!
- Don't disappoint your customer!
- Industrial evolution - Listen to your customers and follow new trends!
- Realize every good idea ASAP!
- Introduce the terminology and standardize it!
- Everything is difficult until it becomes easy
- 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 ...
- Appoint a representative!
- 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?
- Modular software architecture
- Abbreviations
- Machine modularization
- Knowledge gained from a completed project is priceless
- Variable names
- Choice of programming language
- Visual modeling
- Documentation issues
- Safety relays versus safety PLC
- Software update
- Design considerations for effective HMIS
- Clear signals
- Talk to operators
- It doesn't work without sensors
- Event logger as the very first function implemented in the program
- Diagnostic tools
- My boss was a hero
- Maintain order in the program code
- Make backups, make small changes and test a lot
- Graphic designer
- Dream of a platform-independent PLC program
- High Performance HMI
- HMI - Have a consistent style
- HMI - Don't overdo it with complex design
- Hidden dangers during commissioning
- HMI is not a web page
- Choosing an HMI display
- The false illusion of rapid progress
- HMI layout and correct display size
- HMI layout design
- HMI navigation
- HMI - back and forward navigation buttons
- HMI – Don’t hide anything
- HMI - annoying pop-up windows
- What makes an HMI intuitive?
Comment#: 00001
Date: 2020-10-25
User: Radim
At all stages of project implementation, ensure that your results are suitable for their intended use.
Comment#: 00002
Date: 2021-11-29
User: Radim
"Writing good software requires a willingness to keep working at a problem, making code more readable, more efficient, and less error-prone over time by responding to feedback and thinking deeply about problems (sometimes the best tool is a pencil and paper for writing down your thoughts). Don’t expect to get things completely right the first time!"
- https://towardsdatascience.com/notes-on-software-construction-from-code-complete-8d2a8a959c69
Comment#: 00003
Date: 2022-09-13
User: Radim
"One good test is worth a thousand expert opinions."
- Wernher von Braun
Comment#: 00004
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#: 00005
Date: 2022-11-25
User: Radim
"Listening to customers is the best way to get in tune with a product's strengths and weaknesses.
Also, remember that negative reactions are almost always louder and more passionate than positive ones. In fact, you may hear only negative voices even when the majority of your customers are happy about a change. Make sure you don't foolishly backpedal on a necessary but controversial decision."
Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.
Comment#: 00006
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#: 00007
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#: 00008
Date: 2022-12-15
User: Radim
There is a big difference between "done" and "done". The "done" status of a task in Excel or on a to-do list does not always mean that it makes sense, works, is understandable and has been confirmed by a test.
Comment#: 00010
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#: 00011
Date: 2023-09-15
User: Radim
Complaints and identified problems are good sources of innovation.
Comment#: 00012
Date: 2023-09-27
User: Radim
"By continuously improving the design of code, we make it easier and easier to work with.
This is in sharp contrast to what typically happens: little refactoring and a great deal of attention paid to expediently add new features.
If you get into the hygienic habit of refactoring continuously, you'll find that it is easier to extend and maintain code."
- Joshua Kerievsky. Addison-Wesley (2004). Refactoring to Patterns.
Comment#: 00014
Date: 2024-01-05
User: Radim
I have found the solution !!!
But unfortunately the problem did not match my solution.
:-)
Comment#: 00016
Date: 2024-02-14
User: Radim
Benefits and risks of software updates via remote access to customer machines
In today's agile world, quick and easy software updates are essential for maintaining technologies and systems. However, the transition from manual installation of updates to remote access raises an important discussion about the risks and benefits of this approach.
Technical feasibility and tools:
The technical aspect is not an obstacle. With today's concepts and tools, the application software can be updated on remote machines at the customer's premises.
Risks:
However, the main concerns relate to the risks associated with this procedure. There is a possibility that the installation of the new software version may cause unexpected problems that can have serious consequences. The machine may no longer be able to be started and may even no longer be accessible remotely. A specialist then has to travel to the customer. This can take up to several days and leads to expensive production downtime for the customer.
Benefits:
Conversely, remote software updates have many advantages. Customers do not have to wait for a technician to be present, which saves time and travel costs. In addition, the rapid availability of updates can improve overall customer satisfaction and increase efficiency.
Solution:
To minimize the risks associated with remote updates, clear rules and procedures must be established. These include thorough testing of updates prior to deployment, detailed data backup and recovery plans and adequate training of customer personnel.
Comment#: 00017
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.