We agree that rates are weird and relativistic. Myself I've seen $50/hour described as too high, and $100 as too low (head explodes), and I've been treated alternately as both overqualified and underqualified for doing some technical thing that I know I could certainly do. Also seen and heard that bidding low will increase the chance of getting a gig as well as decrease the chance (for some clients), and, and, and... It's just crazy inconsistent and relative.
There's also the "all developers are the same, therefore commodity pricing is in effect" phenomenon which is annoying to encounter. And the "just tell me rate, because I know exactly how many hours this will take, and no other factor matters" phenomenon. Crazy stuff.
One good takeaway from the Lee article I had was that if you set a really high rate, even if you scare away a lot of people, all it takes is 1 client to agree to that, billing anywhere from 1 to a few hours in a given month, and you're in the holy "Ramen profitable" zone. Well, able to cover food and shelter anyway. But then you'll have tons of free time and energy leftover for other activities.
There's also the "all developers are the same, therefore commodity pricing is in effect" phenomenon which is annoying to encounter. And the "just tell me rate, because I know exactly how many hours this will take, and no other factor matters" phenomenon. Crazy stuff.
One good takeaway from the Lee article I had was that if you set a really high rate, even if you scare away a lot of people, all it takes is 1 client to agree to that, billing anywhere from 1 to a few hours in a given month, and you're in the holy "Ramen profitable" zone. Well, able to cover food and shelter anyway. But then you'll have tons of free time and energy leftover for other activities.