I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
This isn't so much an issue of right and wrong but of defining the parameters of an acceptable solution and driving to that result as efficiently as possible.
Engineering always involves trade-offs. And if some aspect of the solution isn't needed, I try to get rid of it.
For example, I've got a project where we didn't implement a UI for a bunch of functionality. We only need to change the data for that functionality once or twice a year so we just edit the database table directly to make the changes. We figured it would take 15-20 years to break even on writing the UI so we just didn't do it (and did something with a higher ROI instead).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great insights.
This isn't so much an issue of right and wrong but of defining the parameters of an acceptable solution and driving to that result as efficiently as possible.
Engineering always involves trade-offs. And if some aspect of the solution isn't needed, I try to get rid of it.
For example, I've got a project where we didn't implement a UI for a bunch of functionality. We only need to change the data for that functionality once or twice a year so we just edit the database table directly to make the changes. We figured it would take 15-20 years to break even on writing the UI so we just didn't do it (and did something with a higher ROI instead).