Re:Advice for an older software developer looking for a change
by mooreds on Tuesday October 18, 2022 @10:43AM
(#33247976)
It's all about derisking what you are selling (your labor and expertise).
It's been a few years, but here are a couple of tips:
* Start with a warm intro from someone you've worked with in the past. This lowers the risk for both parties. This is why I suggested reaching out to former co-workers; they know you and (hopefully) will vouch for you.
* Begin with a small project first. Again, this is about lowering risk. Is there a project you can do for a couple hundred bucks? Can you write a planning document, or do an analysis of the current infrastructure with a read-only account? Or a small enhancement/bugfix?
* Document your expertise in a way that others can find you. This could be code, gists, a blog (I have multiple :) ), articles in places like dzone or the stackoverflow blog, or podcasts. This is good for finding new clients, too.
* An entirely different option is to use a contracting company, where they find the work and take a cut (a large one, typically). This way the company has trust that you can leverage. It's been decades since I walked this path, so I don't know how available it is now.
One other thing: contracting is risky for both sides, not just for the client.
For the first project or two with a new client, don't ever bill more than you can afford to lose. I've never been stiffed 100%, but one time I had to pursue a client for months to get a 4 figure paycheck. Here's that story: https://www.mooreds.com/wordpress/archives/2650
It's been a few years, but here are a couple of tips:
* Start with a warm intro from someone you've worked with in the past. This lowers the risk for both parties. This is why I suggested reaching out to former co-workers; they know you and (hopefully) will vouch for you.
* Begin with a small project first. Again, this is about lowering risk. Is there a project you can do for a couple hundred bucks? Can you write a planning document, or do an analysis of the current infrastructure with a read-only account? Or a small enhancement/bugfix?
* Document your expertise in a way that others can find you. This could be code, gists, a blog (I have multiple :) ), articles in places like dzone or the stackoverflow blog, or podcasts. This is good for finding new clients, too.
* An entirely different option is to use a contracting company, where they find the work and take a cut (a large one, typically). This way the company has trust that you can leverage. It's been decades since I walked this path, so I don't know how available it is now.
One other thing: contracting is risky for both sides, not just for the client.
For the first project or two with a new client, don't ever bill more than you can afford to lose. I've never been stiffed 100%, but one time I had to pursue a client for months to get a 4 figure paycheck. Here's that story: https://www.mooreds.com/wordpress/archives/2650