LinuxQuestions.org - Delete this thread please

Some advice from a person who would evaluate and make a hiring decision about a Linux programmer.

That github project hasn't been touched in 2 years.

The README is one line of nothing.

README is the first place anybody goes so that they can learn about the project, how to build it, and so forth.

I wouldn't spend much time looking any further. I'd open a few C files at least.

Temps or part timers are two categories to me: College interns, and contractors.

I know an intern is new and learning, and I expect them to learn. I expect that they will complete their course of study and want to grow their knowledge into a career.

When I hire a contractor, I fully expect that they know their subject well enough that I'd not have to worry about their learning on the job. Their career development is none of my business, I need a very specific task from them. 1-2 weeks later, if they don't know what their doing, they're gone and we find another solution.

I'd never hire somebody who's abilities are a question mark. I need something specific done. The investment part in growing a candidate would be the college intern situation.

You need to be your own advocate. You need to find a Linux related job and find ways to grow that job into what you want, or use it to gain other jobs where you can do that. Hopefully you've been ardently working on something like this for the last 18 years.

There's no template which guarantees success, however one can remove barriers to success by gaining knowledge, and working to place their self into situations where they can gain knowledge.

To go further, the part where I mentioned that there would be a time limit for a contractor to show progress? Same thing in reverse. You agree to go to some place, they promise you they'll put you in a program, or give you training, and they do not. You inquire of them what their thinking is, and in parallel, you look for another situation, somewhere else. If you find another situation, and when you speak to the company you are working for, and they have no better answer, then you go to the new job. You may have to continue this practice a bit, sorry but the lowliest person on the totem pole is not always given any preferential treatment. Likely your job category would be tester or phone support, or PC support where you are responsible to follow a very certain set of guidelines to set up peoples' PCs. Typically if you show insight, promise, and professionalism, many companies will reward you for it. If they don't, then you have to look out for yourself.