5 ms·
It’s certainly not perfect, but I genuinely think it’s much better than being an FTE anywhere else. Of course I’m biased. I mentioned benefits in another post,
by ryanSrich 5y ago
It’s certainly not perfect, but I genuinely think it’s much better than being an FTE anywhere else. Of course I’m biased.
I mentioned benefits in another post, so I wouldn’t say it’s gig economy.
What other environment could give a developer $100+/hr, ability to make their own schedule, and essentially all legal protections to work on side projects, work for other companies, etc. at the same time?
Is it for everyone? No. But we’ve had more quality devs interested than we can employ at this point, so I’d say it’s attractive to a good portion of the market.
- yakireev 5y agoI did not imply that your company is an Amazon warehouse, I'm sorry if it sounded like that. But if this "hourly wage for hourly work and nothing else" becomes a norm, that's what we'll eventually get, I'm afraid.
- deleted 5y ago[deleted]
- emteycz 5y agoIt's what we want. I wouldn't work any other way ever again. I don't think FTE jobs are going anywhere (companies always push to have us as FTE, not the other way around), let us be.
- jasonzemos 5y agoYou've forgotten the core tenet of every engineering discipline is the master-apprentice relationship. The reason why what you describe is really the gig economy is because you've turned contractors into autodidacts to cut costs. You're not only expecting engineers to work for you, you're expecting them to learn their craft without capitalizing that yourself. Someone has to pay for that too; it probably won't be your other contractors -- otherwise you'd be something like a real company again. Your success in this direction to turn software development into some kind of cattle feedlot is only a mirage. Let me make it clear in economic terms: you're up a few chips at the casino, for now, because the market allows you to be. In the long run it's not sustainable, and won't yield any major feats of engineering with any level of competence.
- ryanSrich 5y agoI really don’t understand this comment. At what point did I say or lead anyone to believe that we 1.) expect developers to be autodidacts? Because we don’t have meetings? Seems an odd way to measure engineering culture and 2.) this had anything to do with cutting cost? Our hourly wages are high enough to where the cost savings is negligible compared to fully loaded salaries. I’d be happy to share the numbers over email. Your idea of the master-apprentice relationship seems overtly romantic. I never said we don’t train staff, or haven’t brought on younger engineers. I literally onboarded an intern last week. They’ll likely make more working less than any intern at any FAANG is making this summer. > Your success in this direction to turn software development into some kind of cattle feedlot is only a mirage. I have to straight up disagree on the premise that it’s a mirage. Nevertheless, this is certainly an experiment, and one where we’ll adapt as needed. I feel as if you’re focusing too much on the contractor concept. Would you be as opposed to this model if say I hired FTEs at 20 hours per week? So essentially half salary. How is this any different (note my previous comments about benefits).
- op00to 5y agoYou pay for employee training. You don’t pay for contractor training.
- jxidjhdhdhdhfhf 5y agoWhat training? I had to pay for my own college degree, my employer didn't pay for that, but they do require it.
- mulmen 5y agoCollege is not job training. I'm not sure why this misconception is so widespread. I have a degree but my employers do pay for relevant training for my job. It's not like the industry stopped evolving 10 years ago.
- 5y ago