Using Pareto Principle when programming.

Photo by Blake Connally on Unsplash

owadays before programming, I usually ask myself :

What is the easiest way can I do that ?

I am not a hero and I am not trying to get any medal.
If there is an easier way to proceed, why choose a more difficult path ?

I try to do things that works, is good enough and make my life easier doing so. Programming is already tough, there is no need to make it even more difficult.

For example, in my screen design there is a list of reports to add.


There is only one icon for addition and another on to toggle valid ones or all as shown above.

When implementing the validation, I have saved all types of data and needed to reset them.

Option 1

Add a delete button.

But there was none in the mockup. I have to modify HTML codes which might lead to design regressions.
Moreover, the designer will most probably update the screen. This will make it harder for me to keep track of the changes.

Option 2

A much simpler solution is to use Postman to remove the data I don’t want and send through a PUT request.



Senior Software Developer, Writer, Amateur Photographer, Reader

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store