News for hackers. Stuff that matters.
Re:How to Design Software Good by fao_ on Thursday November 08, 2018 @07:55PM (#18411532)
I kind of feel that you just read the title here. It's not talking about the 'fullest':

  An example of this would be if a music composition
  program has an easily-reached maximum song size because
  the code monkey who wrote it used a 16-bit variable
  instead of a 32-bit one. *While there are sometimes
  limitations that cannot be overcome*, the actual code
  written and the architecture used when it was written
  should have as little effect as possible on what the user
  sees and works with when using your software.
(emphasis mine)

I think it might be better rephrased as:

1) Don't add unnecessary constraints (or: Don't prioritise efficiency/etc. over the interface).

and

2) A good interface abstracts away technical problems, rather than presenting them in a different form.

Re:How to Design Software Good by bkmartin on Thursday November 08, 2018 @08:13PM (#18411636)
The most common example I see is the password requirement that it must be between 8 and 16 characters... The 16 character limit is the main issue there... You know it has to do with the wya the data is stored.
Re:How to Design Software Good by adrianN on Friday November 09, 2018 @01:39AM (#18412764)
Between 8 and 16 characters, but only 7 bit ASCII. But there is no error message if you use § in your password, it just kills the server.
Re:How to Design Software Good by Aenyn on Friday November 09, 2018 @06:14AM (#18413679)
At my workplace the official password policy requires /exactly/ 8 character passwords...
Re:How to Design Software Good by reificator on Friday November 09, 2018 @12:02AM (#18412438)
It had better not...
Re:How to Design Software Good by hitsthings on Friday November 09, 2018 @01:58AM (#18412817)
And yet...
Re:How to Design Software Good by emmelaich on Friday November 09, 2018 @07:58PM (#18419289)
I'm sure we agree 99%.