Best rules as a contractor Post: 302754159

Sponsored Content

The Lounge What is on Your Mind? Best rules as a contractor Post 302754159 by Neo on Thursday 10th of January 2013 07:11:41 AM

01-10-2013

Administrator

Most of my career, over 95%, was as a self-employed person.

The formula is quite simple:

Honest, integrity, professionalism and honor above all.
Strong, current, relevant technical skills - always learning
Flexible, adaptive, and considerate to others and ideas
Hourly wages should be high enough for you to pay your own benefits, etc.

I also have a lot of experience on the other side of the equation, hiring contractors. I can tell you, for a fact, it is nearly impossible to find honest technical contractors who don't lie and fake their resume and references. In some countries, it is almost like resume cheating is the subculture norm.

I've even tried hiring "by the job" to do simple tasks like program some small code in PHP or HTML; and it is nearly impossible to get someone who can do a 1 hour job in less than three days or even weeks, LOL.

I've read so many "super duper" resumes, experts in this and that; but when I ask to just demonstrate some simple coding skills, the candidate falls apart with excuse after excuse.

So, to be a great contractor and make money is easy; if you are honest, skillful and all the things mentioned above.

Too many people are looking for shortcuts, they will lie and cheat and fake their skills on their resume and they struggle all their career. The people who just do the work, learn the skills, become experts, real experts, not fake ones; find that contracting is very easy (and rewarding!) and the money will flow and you will have a good life.

It's easy... their are no shortcuts, only hard work, honesty and integrity.

Without honor, all is lost.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

rules?

What rules? I have been searching for hours on the internet and just cannot seem to find the command you would type to add a serial port or the file that specifies whether a filesystem shoudl be mounted at boot time or not.............

2. Post Here to Contact Site Administrators and Moderators

Rules

https://www.unix.com/showthread.php?t=2971 Spelling Error. You 'Adhere' to rules, not adhear.

3. Post Here to Contact Site Administrators and Moderators

rules

rules are there but asking 2 questions out of 30 is surely understanable esp when the instructor gives an open book test and urged us to seek answers anywhere we can except from him directly.

4. Post Here to Contact Site Administrators and Moderators

Homework rules !

Why do you ask about prof info at homeworks forum..... do you contact to prof and tell him that this student asked for our help? I asked that because some of them are very strickt and conseder that as cheating

LEARN ABOUT DEBIAN

qsig

qsig(1B)								PBS								  qsig(1B)

NAME

       qsig - signal pbs batch job

SYNOPSIS

       qsig [-s signal] job_identifier ...

DESCRIPTION

       The qsig command requests that a signal be sent to executing batch jobs.  The signal is sent to the session leader of the job.

       If the -s option is not specified, `SIGTERM' is sent.  The request to signal a batch job will be rejected if:

       -      The user is not authorized to signal the job.

       -      The job is not in the running state.

       -      The requested signal is not supported by the system upon which the job is executing.

       The qsig command sends a Signal Job batch request to the server which owns the job.

OPTIONS

       -s signal      Declares which signal is sent to the job.

		      The signal argument is either a signal name, e.g.  SIGKILL, the signal name without the SIG prefix, e.g. KILL, or a unsigned
		      signal number, e.g. 9.  The signal name SIGNULL is allowed; the server will send the signal 0 to the job which will have	no
		      effect  on  the  job, but will cause an obituary to be sent if the job is no longer executing.  Not all signal names will be
		      recognized by qsig. If it doesn't recognize the signal name, try issuing the signal number instead.

		      Two special signal names, "suspend" and "resume", are used to suspend and resume jobs.  Cray systems use	the  Cray-specific
		      suspend()/resume() calls.

		      On  non-Cray system, suspend causes a SIGTSTP to be sent to all processes in job's top task, wait 5 seconds, and then send a
		      SIGSTOP to all processes in all tasks on all nodes in the job.  This differs from TORQUE 2.0.0 which did not have the  abil-
		      ity to propogate signals to sister nodes.  Resume sends a SIGCONT to all processes in all tasks on all nodes.

		      When  suspended,	a  job continues to occupy system resources but is not executing and is not charged for walltime.  The job
		      will be listed in the "S" state.	Manager or operator privilege is required to suspend or resume a job.

		      Note that interactive jobs may not resume properly because the top-level shell will background the suspended child process.

OPERANDS

       The qsig command accepts one or more job_identifier operands of the form: sequence_number[.server_name][@server]

STANDARD ERROR

       The qsig command will write a diagnostic messages to standard error for each error occurrence.

EXIT STATUS

       Upon successful processing of all the operands presented to the qsig command, the exit status will be a value of zero.

       If the qsig command fails to process any operand, the command exits with a value greater than zero.

SEE ALSO

       qsub(1B), pbs_sigjob(3B), pbs_resources_*(7B) where * is system type, and the PBS ERS.

Local																	  qsig(1B)