Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As a user, I see (generally speaking) how a lot of software has "opinionated" procedures.

The programmers/engineers may have assembled a "perfect" tool (in the sense that it actually solves the problem that it should solve) but often practical usage needs to go through a number of steps that feel "unnatural" to the final user.

In some cases I managed to actually talk to the programmers but what I found most time is a sort of elastic wall, they often concur that this (or that) thing would be better/easier/simpler, then (for this or that reason) they never change it.

Maybe it is just me and my suggestions may well be either "impossible" to implement or plainly stupid, but after having been told a few times "You are right, if we do this it would be better, I am taking this note for next release." and then 1, 2, 3, 4 updates/releases after nothing has changed, it becomes tiring/frustrating to provide feedback/suggestions that will never be implemented.

Only as an example (which is a pet peeve of mine) is input forms, talking of desktop apps nowadays a (say) 1024x768 resolution on a monitor is a "bare minimum".

A single form (entirely viewable without scrolling) can well contain 30/40 input fields, yet (for some reasons) a number of softwares use multi-tabbed (tiny) forms, i.e. for the 30 fields you have three tabs, each one with 10 fields, if you forget an input on a field on tab #1 and go on, you cannot see which field is is missing (as you are on tab #2 or tab #3), then when you confirm you get a missing field error and you have to check all three tabs.



Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: