What great programmers & designers need.

  • good tools (that they can control)
  • a good space (quiet, large and flexible enough to accommodate moods)
  • make things interesting (e.g.: allow learning and avoid repetition)
  • set high standards
  • allow them to concentrate/focus
  • allow them to understand/see the context
  • you always need more “hackers” together, as they produce square their group number
  • you can not recognize a great hacker; they themselves do not know
  • take away as many problems/worries/stress/obstacles as you can without being or getting in the way

Give it to them & expect results.


Posted

in

by

Tags:

Comments

One response to “What great programmers & designers need.”

  1. Dennis Kalkandis Avatar
    Dennis Kalkandis

    From Dennis

    The ability to maintain a good relationship with programers is more than just a result based issue for the client.

    Proper knowledge of a project is extremely difficult for a client o purport to a programmer.

    In most cases no additional information can be given to instruct the programmer other than:

    "I want it to look like this and do this."

    Secondly by

    "How much and how long"

    The two most uttered sentences by a client.

    The interesting situation about stress is that a client expects ongoing results
    and a commitment from a programmer.

    A programmer expects to be left alone
    to produce results for the client.

    The Programmer is never upfront with the availability of the hours they are going to allow for a project.

    Not one freelancer so far has met there alloted time frame or had given notice that this cannot be done in that time.

    See it from different points of view.

    A programmer gets updated for changes to the point of confusion.

    This correct for most clients and is the caused by the difference in the coding language barrier.

    The end result is this if a client could pin-point the exact schema of the project more than likely they are lnowledgeable enough to do it themselves.

    So in conclusion.

    A project should have scheduled a approximately time allocation per day.

    This provides co-ordination between client and programmer and can also accord the ability to extend new tasks
    to other programmers.

    If an approx time-line schedule is set then a project can flow alot easier.

Leave a Reply

Your email address will not be published. Required fields are marked *