This was news for us since we didn’t know they were editing those files.

After doing some research, we found out that the current library does not support the PDF editing structure, so I came up with a few solutions for this issue.

1 – generate the pdf again when they need to provide the additional information

2 – rewrite the pdf-generating functionality straight from data to PDF, no longer from HTML to PDF.

3 – do nothing.

I provided estimates and explained the thinking behind each solution.

Steak holder chose to do option 3.

They didn’t explain the decision, but I can see it.

We, as developers, love to fix problems by coding. We see the problems and use software to fix them.

But sometimes, you need to step back and realise what the customer needs.

In this case, they needed a fast flow of processing and editing applications.

By implementing option 1, they would lose this fast flow. And implementing option 2, was too expensive for barely any gain.

Hence, solution 3 was OK with them.

This is a good example of when you are striving for customers’ happiness and not your desire to write more code.

#RubyOnRails #Ruby #DevLife #softwareengineering #programming