5 ms·

> 1. Increase your rates. Make them non-negotiable. There's people that are ready to pay for quality. If a client asks you to lower your rate, they probably are

by Kluny 8y ago

> 1. Increase your rates. Make them non-negotiable. There's people that are ready to pay for quality. If a client asks you to lower your rate, they probably aren't a good client in the first place. What if you're mediocre, though?

Ma8ee 8y ago
Then you belong in the cubicle. Stay there until you are good. (Which won’t happen automatically, you have to put in the work.)
- cbzehner 8y ago
  This isn't true. Very few people are bad across the board -- find your strengths (as other commenters have said) and focus on those. It's better to be excellent in one or two areas, especially ones your passionate about than solid across the board. If you suck at something and it's causing problems, that's a different story -- but don't get stuck on comparing yourself to others. I wish I could downvote this comment. Please ignore it.
  - Ma8ee 8y ago
    Quite a few people don't have enough skills to freelance. Either because they don't have that one skill in high demand, or they lack the drive to network and sell themselves. These people will just become miserable trying to make a living without a steady employer.
joshvm 8y ago
You should still aim for charging quite a bit higher than what you think is reasonable. There are an awful lot of bad developers, so even mediocre is probably fine. I've had consulting gigs where I've charged $200 an hour to answer a survey as a domain expert, and I learned later that I probably undercharged. People will pay, don't worry about that. If you land a job that you feel got a bit close for comfort, lower your rates and re-calibrate. But assess why before selling yourself cheap - was it really beyond your skill? Did you just need more time? Don't forget that if you charge more, you can better devote your time to those projects. If you charge less you have to spread yourself more thinly to remain solvent.
- kasey_junk 8y ago
  I can’t imagine any professional setting I’ve been in, where firing up the machinery to get a consultant in place would be worth $200. Conversely I’ve been in many situations where an expert reading one page of text and nodding (with a follow up email) was worth several thousand dollars.
mikeleeorg 8y ago
It depends on which vector you deem yourself mediocre. If you think your technical skills are mediocre and want to be a technical contractor, then focus on being a great solutions provider. And by "solutions provider," I mean take the time to deeply understand the root causes of your clients' problems, then help them find the actual solutions. Sometimes these solutions are not even technical, which is totally okay. Clients will love that you're helping them solve problems in addition to providing technical services.
- Kluny 8y ago
  I can write code that works, finish features, and I'm pretty good at debugging. I can also teach/encourage others without condescending, ask good questions, and explain a problem clearly technically and non-technically (once I understand it myself). I guess I'm mediocre in that it consistently seems to take me 8-10 hours to finish jobs that come with a 4 hour time estimate (my company is big on estimates). I'm also pretty sloppy - code reviewers routinely catch minor errors that I should have known better than to commit. I have the experience, way too often, of using some feature that I pushed months or years ago and learning that it's, like, haunted or something. Doesn't work the way it's supposed to at all. Obvious failures that I should never have called "done". When it comes to building a complete product, from start to finish, I mostly can't get past MVP stage (talking about personal projects in this case). And I once spent over a month trying to update the version of TinyMCE for a CMS that I was working on, and did not succeed. I literally got another job and left the company with that task unfinished. The new job pays double, and I still feel like a bit of a fraud. And yeah, I'm writing "bog-standard PHP" as the other commenter put it. I've tried to get work in other languages to diversify my skillset, and haven't succeeded. At this point I'm starting to not care anymore - I like PHP just fine, loose typing be damned, and I'm starting to think I want to move out of technical roles rather than improve my language skills.
  - kr4 8y ago
    keep building new stuff, on side in addition to your job (which is usually borring/monotonous). concentrating on details. Once you've spent 10k hours on programming it'd just come naturally to you. You'd be amaised how magically and naturally you can solve complex problems. This is an unfailing formula of attaining mastery in literally anything you can imagine [0]. 0: https://www.amazon.com/Outliers-Story-Success-Malcolm-Gladwell/dp/0316017930?ie=UTF8&tag=thstsst-20&linkCode=as2&camp=1789&creative=390957 https://www.amazon.com/Outliers-Story-Success-Malcolm-Gladwe...
tptacek 8y ago
If there is a list of annoying false things technology people believe about business, this notion that bill rates track technical ability would have to be near the top of it. Your rate has almost nothing to do with how good a programmer you are. Sorry, excellent programmers who've had a hard time getting consultancies launched. Your bill rate roughly† tracks how much value you provide to your client. "Value" is complicated and situational. For programming work, for most clients, extreme technical excellence is of marginal value. Clients that engage third party developers tend to see software as a cost center and/or are simply trying to solve a business problem. They care about how quickly that problem can be workably solved, and (please take notes:) how predictable the costs are. You can be thoroughly mediocre at programming and an excellent business value, if your mediocre code solves business problems people will allocate budget for and if you can deliver it predictably. If you can deliver predictably and fast, you can ship bog-standard PHP code and charge integer multiples of what a much better developer might implement in Rust or Haskell. The market tends to pay a premium for problem domain specialization, and less of a premium for elite skill. None of this much matters for someone just getting their feet wet trying to get their first couple clients. Do whatever gets you started. But get out of the habit of convincing yourself that you have to qualify somehow to charge more money. Even the consultants who are constantly telling people to raise their rates are also not charging enough. I'm a varsity member of team "raise your rates" and I thought we were undercharging 4 years ago. Since then, FTE rates have gone through the ceiling and our rates have not scaled with them. It is very unlikely that any consultant chatting about consulting on HN is charging their real market rate. I have one bit of bad news for you: if you want to make a career out of being a contractor or consultant, you need to get off freelancing sites ASAP. It's fine to get started there, but you're not developing your practice in any meaningful way as long as you're using them; you're just getting better at slinging code (which doesn't earn you better rates!), while radically undercharging clients. Getting off freelancing sites is rough, because freelancing sites tend to provide a comparatively stable revenue stream, and real consulting revenue is lumpy. If you've never experienced "lumpy" before: it's (a) terrifying and (b) really easy to screw up, by assuming you're flush with cash when really you've effectively just been pre-paid for the next N quarters. Some people reasonably don't want to work under lumpy consulting conditions. Better you figure that problem out for yourself early rather than wasting your time pretending, or, worse, forgoing a fuckload of income by chaining yourself to freelance sites. † Roughly because most serious clients allocate a budget that establishes a range of what they're willing to pay to solve a problem, and an invisible component of that budget is how much work they're willing to put in to sourcing a contractor --- the first credible contractor they talk to might win the deal, meaning there's no competition to aid price discovery. Corollary: one way to "provide value" and charge a premium is to be easy to source. Something that people who build consulting firms, the kind with lots of consultants, learn quickly: clients put a premium on firms that are always available.
iovrthoughtthis 8y ago
What does mediocre mean?
iovrthoughtthis 8y ago
You can produce quality work.
onion2k 8y ago
Increase your rates regardless. Clients don't know, or really care, about quality so long as what you build works. Where quality is important is in keeping your costs low. Having to revisit old code to fix bugs or trying to work with bad code to add features has very little impact on your client. It affects you. Strive to write good code for your own sake. Plus, if you take on fixed price projects writing code you don't need to go back to really increases your profit.
- scruffyherder 8y ago
  > so long as what you build works. You mean, ships on time.
Spooky23 8y ago
Doesn’t matter. People pay too much for broken crap all of the time.
csomar 8y ago
I've seen mediocre to really bad people getting paid $3000/day for their mediocrity and not delivering results. Increase your rates.
- rl1987 8y ago
  For how many workdays in row?
  - csomar 8y ago
    For over a year.
thrawaylost112 8y ago
You are making a huge mistake assuming that everyone has ability to tell a mediocre from a 10x engineer, which is patently false assumption to begin with. Market has information asymmetry baked in. Not everyone is informed, that's where you earn your bucks.
xfitm3 8y ago
Persistence and QA. Find your own mistakes before someone else does.

by Kluny 8y ago

Ma8ee 8y ago

Then you belong in the cubicle. Stay there until you are good. (Which won’t happen automatically, you have to put in the work.)

cbzehner 8y ago
This isn't true. Very few people are bad across the board -- find your strengths (as other commenters have said) and focus on those. It's better to be excellent in one or two areas, especially ones your passionate about than solid across the board. If you suck at something and it's causing problems, that's a different story -- but don't get stuck on comparing yourself to others. I wish I could downvote this comment. Please ignore it.
- Ma8ee 8y ago
  Quite a few people don't have enough skills to freelance. Either because they don't have that one skill in high demand, or they lack the drive to network and sell themselves. These people will just become miserable trying to make a living without a steady employer.

joshvm 8y ago

You should still aim for charging quite a bit higher than what you think is reasonable. There are an awful lot of bad developers, so even mediocre is probably fine. I've had consulting gigs where I've charged $200 an hour to answer a survey as a domain expert, and I learned later that I probably undercharged. People will pay, don't worry about that. If you land a job that you feel got a bit close for comfort, lower your rates and re-calibrate. But assess why before selling yourself cheap - was it really beyond your skill? Did you just need more time? Don't forget that if you charge more, you can better devote your time to those projects. If you charge less you have to spread yourself more thinly to remain solvent.

kasey_junk 8y ago
I can’t imagine any professional setting I’ve been in, where firing up the machinery to get a consultant in place would be worth $200. Conversely I’ve been in many situations where an expert reading one page of text and nodding (with a follow up email) was worth several thousand dollars.

mikeleeorg 8y ago

It depends on which vector you deem yourself mediocre. If you think your technical skills are mediocre and want to be a technical contractor, then focus on being a great solutions provider. And by "solutions provider," I mean take the time to deeply understand the root causes of your clients' problems, then help them find the actual solutions. Sometimes these solutions are not even technical, which is totally okay. Clients will love that you're helping them solve problems in addition to providing technical services.

Kluny 8y ago
I can write code that works, finish features, and I'm pretty good at debugging. I can also teach/encourage others without condescending, ask good questions, and explain a problem clearly technically and non-technically (once I understand it myself). I guess I'm mediocre in that it consistently seems to take me 8-10 hours to finish jobs that come with a 4 hour time estimate (my company is big on estimates). I'm also pretty sloppy - code reviewers routinely catch minor errors that I should have known better than to commit. I have the experience, way too often, of using some feature that I pushed months or years ago and learning that it's, like, haunted or something. Doesn't work the way it's supposed to at all. Obvious failures that I should never have called "done". When it comes to building a complete product, from start to finish, I mostly can't get past MVP stage (talking about personal projects in this case). And I once spent over a month trying to update the version of TinyMCE for a CMS that I was working on, and did not succeed. I literally got another job and left the company with that task unfinished. The new job pays double, and I still feel like a bit of a fraud. And yeah, I'm writing "bog-standard PHP" as the other commenter put it. I've tried to get work in other languages to diversify my skillset, and haven't succeeded. At this point I'm starting to not care anymore - I like PHP just fine, loose typing be damned, and I'm starting to think I want to move out of technical roles rather than improve my language skills.
- kr4 8y ago
  keep building new stuff, on side in addition to your job (which is usually borring/monotonous). concentrating on details. Once you've spent 10k hours on programming it'd just come naturally to you. You'd be amaised how magically and naturally you can solve complex problems. This is an unfailing formula of attaining mastery in literally anything you can imagine [0]. 0: https://www.amazon.com/Outliers-Story-Success-Malcolm-Gladwell/dp/0316017930?ie=UTF8&tag=thstsst-20&linkCode=as2&camp=1789&creative=390957 https://www.amazon.com/Outliers-Story-Success-Malcolm-Gladwe...

tptacek 8y ago

If there is a list of annoying false things technology people believe about business, this notion that bill rates track technical ability would have to be near the top of it. Your rate has almost nothing to do with how good a programmer you are. Sorry, excellent programmers who've had a hard time getting consultancies launched. Your bill rate roughly† tracks how much value you provide to your client. "Value" is complicated and situational. For programming work, for most clients, extreme technical excellence is of marginal value. Clients that engage third party developers tend to see software as a cost center and/or are simply trying to solve a business problem. They care about how quickly that problem can be workably solved, and (please take notes:) how predictable the costs are. You can be thoroughly mediocre at programming and an excellent business value, if your mediocre code solves business problems people will allocate budget for and if you can deliver it predictably. If you can deliver predictably and fast, you can ship bog-standard PHP code and charge integer multiples of what a much better developer might implement in Rust or Haskell. The market tends to pay a premium for problem domain specialization, and less of a premium for elite skill. None of this much matters for someone just getting their feet wet trying to get their first couple clients. Do whatever gets you started. But get out of the habit of convincing yourself that you have to qualify somehow to charge more money. Even the consultants who are constantly telling people to raise their rates are also not charging enough. I'm a varsity member of team "raise your rates" and I thought we were undercharging 4 years ago. Since then, FTE rates have gone through the ceiling and our rates have not scaled with them. It is very unlikely that any consultant chatting about consulting on HN is charging their real market rate. I have one bit of bad news for you: if you want to make a career out of being a contractor or consultant, you need to get off freelancing sites ASAP. It's fine to get started there, but you're not developing your practice in any meaningful way as long as you're using them; you're just getting better at slinging code (which doesn't earn you better rates!), while radically undercharging clients. Getting off freelancing sites is rough, because freelancing sites tend to provide a comparatively stable revenue stream, and real consulting revenue is lumpy. If you've never experienced "lumpy" before: it's (a) terrifying and (b) really easy to screw up, by assuming you're flush with cash when really you've effectively just been pre-paid for the next N quarters. Some people reasonably don't want to work under lumpy consulting conditions. Better you figure that problem out for yourself early rather than wasting your time pretending, or, worse, forgoing a fuckload of income by chaining yourself to freelance sites. † Roughly because most serious clients allocate a budget that establishes a range of what they're willing to pay to solve a problem, and an invisible component of that budget is how much work they're willing to put in to sourcing a contractor --- the first credible contractor they talk to might win the deal, meaning there's no competition to aid price discovery. Corollary: one way to "provide value" and charge a premium is to be easy to source. Something that people who build consulting firms, the kind with lots of consultants, learn quickly: clients put a premium on firms that are always available.

iovrthoughtthis 8y ago

What does mediocre mean?

iovrthoughtthis 8y ago

You can produce quality work.

onion2k 8y ago

Increase your rates regardless. Clients don't know, or really care, about quality so long as what you build works. Where quality is important is in keeping your costs low. Having to revisit old code to fix bugs or trying to work with bad code to add features has very little impact on your client. It affects you. Strive to write good code for your own sake. Plus, if you take on fixed price projects writing code you don't need to go back to really increases your profit.

scruffyherder 8y ago
> so long as what you build works. You mean, ships on time.

Spooky23 8y ago

Doesn’t matter. People pay too much for broken crap all of the time.

csomar 8y ago

I've seen mediocre to really bad people getting paid $3000/day for their mediocrity and not delivering results. Increase your rates.

rl1987 8y ago
For how many workdays in row?
- csomar 8y ago
  For over a year.

thrawaylost112 8y ago

You are making a huge mistake assuming that everyone has ability to tell a mediocre from a 10x engineer, which is patently false assumption to begin with. Market has information asymmetry baked in. Not everyone is informed, that's where you earn your bucks.

xfitm3 8y ago

Persistence and QA. Find your own mistakes before someone else does.