Re: About FreeBSD.org visitors
On 06/10/2013 05:01, Erich Dollansky wrote: this type is called 'design'. As an engineer I do the software behind an website but I do not dare to make the design. Ok, I tell the designer, when I think the design could be improved but I do not dare th change it myself. The trick is to realise that site design is simply another form of engineering, albeint with rather different contexts and constraints than writing software. Writing a website so that the users can interact with it readily, find and understand what they wat, avoid frustration and have a pleasant overall experience is conceptually much the same sort of thing as writing a website so it doesn't hog server resources or continually fail ungracefully or have a badly indexed sub-optimal database schema. Basically you want it to do it's job efficiently and smoothly, whether 'it' is the back-end server code, or the on-screen presentation. Granted, optimizing sites for human interaction is a whole different skill set, but it's not some holy task that only some annointed designer with the mandate of heaven can undertake. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: About FreeBSD.org visitors
Hi, On Sun, 06 Oct 2013 07:55:10 +0100 Matthew Seaman matt...@freebsd.org wrote: On 06/10/2013 05:01, Erich Dollansky wrote: this type is called 'design'. As an engineer I do the software behind an website but I do not dare to make the design. Ok, I tell the designer, when I think the design could be improved but I do not dare th change it myself. The trick is to realise that site design is simply another form of engineering, albeint with rather different contexts and constraints than writing software. Writing a website so that the users can interact with it readily, find and understand what they wat, avoid frustration and have a pleasant overall experience is conceptually much the same sort of thing as writing a website so it doesn't hog server resources or continually fail ungracefully or have a badly indexed sub-optimal database schema. Basically you want it to do it's job efficiently and smoothly, whether 'it' is the back-end server code, or the on-screen presentation. Granted, optimizing sites for human interaction is a whole different skill set, but it's not some holy task that only some annointed designer with the mandate of heaven can undertake. yes, it is not rocket science but - as you said - a different skill set. Erich ___ freebsd-advocacy@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-advocacy To unsubscribe, send any mail to freebsd-advocacy-unsubscr...@freebsd.org
Re: About FreeBSD.org visitors
Hi, On Sun, 6 Oct 2013 05:06:02 -0400 Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: On Sun, Oct 6, 2013 at 3:45 AM, Erich Dollansky erichsfreebsdl...@alogt.com wrote: On Sun, 06 Oct 2013 07:55:10 +0100 Matthew Seaman matt...@freebsd.org wrote: On 06/10/2013 05:01, Erich Dollansky wrote: this type is called 'design'. As an engineer I do the software behind an website but I do not dare to make the design. Ok, I tell the designer, when I think the design could be improved but I do not dare th change it myself. The trick is to realise that site design is simply another form of engineering, albeint with rather different contexts and constraints than writing software. Writing a website so that the users can interact with it readily, find and understand what they wat, avoid frustration and have a pleasant overall experience is conceptually much the same sort of thing as writing a website so it doesn't hog server resources or continually fail ungracefully or have a badly indexed sub-optimal database schema. Basically you want it to do it's job efficiently and smoothly, whether 'it' is the back-end server code, or the on-screen presentation. Granted, optimizing sites for human interaction is a whole different skill set, but it's not some holy task that only some annointed designer with the mandate of heaven can undertake. yes, it is not rocket science but - as you said - a different skill set. Erich http://en.wikipedia.org/wiki/Software_engineering The first sentence : *Software engineering* (*SE*) is the application of a systematic, this is the mistake made here. We - at least me - talk about this: http://en.wikipedia.org/wiki/Communication_design Nobody mentioned the software behind. Only the search function is mentioned very often as being behind current standards. Erich disciplined, quantifiable approach to the design, development, operation, and maintenance of software http://en.wikipedia.org/wiki/Software, and the study of these approaches; that is, the application of engineeringhttp://en.wikipedia.org/wiki/Engineeringto software.http://en.wikipedia.org/wiki/Software_engineering#cite_note-BoDu04-1 Thank you very much . Mehmet Erol Sanliturk ___ freebsd-advocacy@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-advocacy To unsubscribe, send any mail to freebsd-advocacy-unsubscr...@freebsd.org
