Simple systems have less downtime
- Simplicity while building a system leads to less downtime because you don’t need to wait for a specifically proficient person to do/help with anything, anybody in the team can take over troubleshooting without a huge learning curve or training.
- Troubleshooting, therefore, takes less time, because learning the system and then identifying and resolving the problem is almost intuitive.
- When each part of the system has a clear function, it is easier for you to find several alternative solutions.
- Follow these principles to build simpler systems:
- Features don’t justify the complexity. Choose tools that are easy to operate rather than the most feature-rich option.
- Complex ideas lead to complex implementations. Pare down your ideas so they can be explained fast.
- Try modifications before additions. Most people rush to add new layers, steps or integrations for new requirements. Instead, first, check whether the core system can be modified.
Full post here, 6 mins read