Changes between Version 242 and Version 243 of DevelopersForHire


Ignore:
Timestamp:
09/11/2007 11:27:00 PM (8 years ago)
Author:
Sumit Bohra
Comment:

vickeybohra@…

Legend:

Unmodified
Added
Removed
Modified
  • DevelopersForHire

    v242 v243  
    22
    33''I think it does make sense to put a date. Maybe we could sort this list in alphabetical order, too ?'' -- Etienne Robillard
    4 
    5 '' Yes I too agree with Etienne, better to add the names in in alphabetical order. But last updated won't highlight whether the developer is available or not. Better if we can use validity date for the details posted by the Develper. The developer should specify the validity date of the posting, i.e. when he wish to re-update the posting. This will make it mandatory for a Developer to update the validity before it expires and will help the company to know whether the developer is available or not.
    6 
    7 ''I suggest it can be in the following format:'' 
    8 
    9 ||'''Developer Name'''  (Arranged in alphabetical order)||'''Valid Until''' (Should be updated by Developer on expiry)|| 
    10 
    11 i.e.
    12 = Developers for hire =
    13 ||'''Developer Name''' ||'''Valid Until''' || 
    14 
    15 || A...|| || 
    16 
    17 ||  * '''Sumit Bohra - Project Lead (Python Django Java J2EE & Web2.0 Projects)''' [[BR]] I’m affianced in the Software Project Management, Systems Analysis, Development, Testing, Software Maintenance, Client Liaison and Documentation Activities. Ask me for my resume at: [mailto:vickeybohra@hotmail.com vickeybohra@hotmail.com]||15-Sep-2007||
    18 
    19 || Z...|| || 
    20 
    21 ''And I also request everyone listed over here to make things better. If you like the suggestion then please start adding your names above or below my name based on first letter of your names
    22 
    23 -Sumit Bohra''
    244
    255
Back to Top