4 ms·
Not what I'm finding. I'm midcareer myself, trying to build up consulting work, but without coding experience (I've teaching myself to code). Clients seem mo
by chernevik 15y ago
Not what I'm finding. I'm midcareer myself, trying to build up consulting work, but without coding experience (I've teaching myself to code). Clients seem most interested in what I can do, and how reliably. It feels slow starting, but I've only been at it a couple months and I'm seeing traction.
Mind, I don't worry much about rate just now. I'm more interested in the portfolio and the relationships. I figure if I can fill up my calendar, I can start to raise the rate.
I suppose it sucks to be doing "junior" work, but you know something? At this stuff, I _am_ junior. If my background and experience and whatnot mean something to a client, then it will show in the work and relationships. They'll be that much more willing to find a rate that works for both of us as I get busier. But I certainly don't bother talking about them, because they have nothing to do with the relationship I'm proposing.
Now if we're only talking about a coding _job_, no. I doubt could get one, and don't know how quickly I could grow the salary if I did. But I think even that might be be in a different position in a year or so.
- _delirium 15y agoThat's an interesting alternative; thanks for mentioning it. Yeah, I was thinking of regular jobs, not consulting, but that's definitely an option, since it lets you sidestep some of the broader generalizations about age and under/over-qualification, and home in on what you can do for a specific client in this specific moment.