> Open Source software is the exact opposite flow, dev > maintainer > user > business
That's a pretty sad assumption.
"dev > user" is why a lot of projects have very poor usability.
That's a pretty sad assumption.
"dev > user" is why a lot of projects have very poor usability.
it should be improved upon by responses from the users who use your implementation, but what you're saying suggests that efforts like architecting your software in ways that improve/maintain development standards or packaging your software in a dependency manager before delivering any level of user facing feature is a sad assumption to you. I don't think the concern of usability here takes the entire picture of a project into context.