PROGRAMMERS...a little shop talk, if you will...
 

Do you work best with a tight spec? By that I mean, the *method* of the function is described.

Or do you like it better when just the end result is specified (input > your contribution > output)?

tight spec.... because the end result will be defined by it

as long as i can be covered in peanut butter while i masturbate at my keyboard it doesnt matter to me. more specifications are always better as long as they're done right. if not its probably better to let a programmer do what he wants

(input > your contribution > output) generally costs more. It takes time to take requirements and come up with feasible specifications.

If specifications are there then you just code away without caring about any of the design issues.

Edit: As for the preference, I prefer the first option because there's more creativity involved... but it would cost more for the client of course :)

I prefer to work from a desired feature set and nothing more.

*edit* this isn't usual, btw.

Well I like to have some details about the work...it helps make the script better...however, some people are just exagerating LOL...I did a script for someone and he was so picky...took like 3x the times it should've taken...and in the end it just isn't worth my time since I didn't charged him much more...

he kept asking me to recode some parts...even AFTER he told me he wanted'em that or that way...

you got to let the data find what it is looking for :pimp

plus, translation from client to code is always an art form

I get the client to provide me with a dot point list of what they want, as specifically and comprehensively as possible.

I'll give it a quick look over, to make sure it makes sense, quote off that, and work off that.

When you get to the end - there's no argument about work done if you've worked off a 50 point list as opposed to 'make me a program that does X'

My programmers use this quote a lot...

'I am not a fukn designer...!"

so i guess they like to have specs upfront :winkwink:

He is a good programmer then :winkwink:
If you buy a custom script and it is design wise awesome looking, then you know the backend is crap and they are trying to hide it with a fancy design, if it looks like shit then you know it will have a killer backend :2 cents:
Unless you buy it from a bigger company that have both designers and programmers, then everything will be shit since they cant work together :1orglaugh

i define my own specs :)

99% of the time, the client has no idea what they really want. They have a concept.... but once they start to see the finish line, their head starts to swim with all kinds of new ideas as to how to make it even better or different.

I've met very few non programmers who knew every single thing they wanted with a script right from the start.

tight spec.. if it isnt right.. clients fault, I wouldnt work for anyone who's just going to waste my time, recoding the same things over and over.

Maybe thats why I dont take clients at all anymore :)

thank god im not the only one LOL...people are often confused between the 2 apparently...a lot of people contact me with like half a design, and they want a complete solution, so half of the work I have to do is messing with the design...

yeah, half the work is figuring out what people want

Never really liked programming in the long term. Ended up as Project Manager with a team of programmers, and well, you're all fucked. :)

that's exactly what I'm doing :thumbsup

Try to switch them to Diet Dr. Pepper and they'll keep longer on the shelf. Getting them to exercise is a near certain impossibility, but doesn't hurt to try that too. :pimp

I think it depends on the coder(s).

For example, if you are outsourcing something to an offshore company, you definately want to have strict specifications. Leaving them room for 'creativity' will only lead to delays, problems and more time/money spent.

On the flip side, if you have an experienced coder in-house, it might take more time to draw up the specs than to actually have him code the project based on a simple discussion.

Also, it is often impossible for the client/project manager to come up with fully detailed technical specs unless they have a deep technical expertise. They might know what they want, maybe in what language and what database, etc...but they won't consider all the intricate details that come up which will lead to a need to go against the specs.

I hate documentation/specs. However I know for a fact that they are sometimes the best option (for example, with Tico programmers ;p). That's my :2 cents:

Fo you PHP guys, my tip of the day is to use Smarty. Once you get used to it you will LOVE it and its vast array of advantages/benefits.