Computer programmers

realspeed

Suspended / Banned
Messages
8,827
Name
Bazza
Edit My Images
No
I don't know what it is, but why do computer programmers seem to always make it the hardest way possible to access information with big companies?

Just tried paying HIBU (yell) a business invoice. After searching several pages I managed to get to the bill paying section.

It must be either the way they are taught or want to make their work look pretty pretty. Having spoken to several programmers in my line of work I asked how many end users they consulted before producing their program? not one had bothered to do so.

I think that just sums it up, no research first =- not taught in uni to find out end users needs- blindly go ahead in the hope it will impress.
 
them as well, all the same to me, my son being one of them
 
Last edited:
Generally the convoluted awfulness comes as 'requirements' from up above. Programmers left to themselves will (mostly) produce efficient (but ugly) interfaces.
 
one writes programs and the other writes websites :)

but remember there is always someone spec'ing/overseeing/signing off on the project, mostly non technical persons.

7181.strip.gif


:)
 
Just tried paying HIBU (yell) a business invoice. After searching several pages I managed to get to the bill paying section.

As Neil said, this is web design, not programming, and writing web pages is akin to using an old word processor where you had to insert the formatting codes manually (WYSIWYG tools are also available for people that don't want to learn HTML and HTML is not a programming language.)

For corporates the design will typically come from the arty people department, not from the technical people. However, you always want to make it easy for people to give you money!

It must be either the way they are taught or want to make their work look pretty pretty. Having spoken to several programmers in my line of work I asked how many end users they consulted before producing their program? not one had bothered to do so.

I certainly don't want to make my programs look pretty. Time spent on user interface design just takes away from time available for developing actual program functionality. I'll happily sacrifice ease of use on the altar of functionality.

My idea of a good user interface is the gcc command line :naughty:.
 
we do a lot of custom development of projects for clients.

the IT devs want to work to a wire frame, getting the mechanisms and back end working, before playing around with layout and presentation.

the people in the meeting with the clients earning the money want screenshots and captures of the live (not mock-up) site/portal/toy first, then get it working afterwards.


Guess what gets promised to the client?
 
Believe it or not this happens in all 'design' disciplines. Our hardware engineers are always designing things that are impossible to maintain/repair post production. They have been asked several times to consult the maintenance engineers but they never do.
 
Believe it or not this happens in all 'design' disciplines...

Definitely!

In my experience, whether it be a mechanical, electronic or procedural system, the design side and the users have very little understanding (or sympathy!) of each other:

The "users" are constantly aghast that the "idiot designers/SME's" designed the system in such a stupid way...

...and on the other side...

...the designers/SME's constantly moan about the "idiot users" who a) don't know what they want and/or b) are too dumb to use the system.

In a previous life as part of a project management team it was my job to sit between these two parties (various technical and system design dept's and the client) and try and translate/relay each side's issues in a way the other side could understand. Sometimes it felt like I was a marriage counselor and although it didn't always work, left to their own devices they'd still be arguing about it now!

Fun and games. :)
 
Last edited:
I've just written an intranet at work.

The feedback I got was "Andy's not got much design experience".

My response was "No - but does it do what you asked for?

"Oh yes - it just doesn't look pretty".

"Well sorry, but I'm a head of infrastructure not a web developer/designer. You got that for free - by all means feel free to employ someone who can design a pretty website for you"

"Oh no it's great - we don't need it to look pretty"
 
I've been on many websites like that - very frustrating.
 
Last edited:
I've just written an intranet at work.

I had to do something similar. I ended up using Joomla and Artisteer. What did you use to create yours?

Mine was less flashy than its predecessor but everything works and it doesn't trawl the computer to a halt!
 
Back
Top