6 ms·
> For example developers, who are writing clean code and refactor their stuff before they deliver If you want that you probably shouldn't be outsourcing to fre
by bawolff 6y ago
> For example developers, who are writing clean code and refactor their stuff before they deliver
If you want that you probably shouldn't be outsourcing to freelancers in general. People aren't going to make clean code if they know they are never going to see it again and arent being paid for how clean it is.
- dgellow 6y agoThat's a bold statement. I personally do care. I do contracting work and care about the code I write. And companies I work with seem to appreciate.
- hnarn 6y ago> arent being paid for how clean it is To be fair, a lot of full-time developers in big companies also do not get paid for how clean the code is, because no one cares. I'd probably lean more towards personal character deciding this than just looking at people behaving only and always as incentives tell them to in any situation. Some people take pride in their code and some don't.
- robjan 6y agoThe difference is if you are an employee you are more likely to need to make changes to your own messy code so there is an incentive to keep it clean
- hnarn 6y agoAll I'm saying is that I don't think it's as simple as "you either have incentive or you don't", because if it was, then developers writing bad code that they themselves had to go back to wouldn't exist, but they clearly do. I'm one of them and I talk to a lot of them daily. To say that "of course this freelance code is garbage, they're paid peanuts" is naive, because it implies that: a) Well paid engineers always write beautiful code, and the more they get paid the more beautiful it becomes, which obviously isn't true. b) Badly paid engineers don't care about code quality if they don't get paid for it, which isn't true because open source is a thing. Reducing everything to economical incentives is, in my opinion, not very useful.
- bawolff 6y ago> Badly paid engineers don't care about code quality if they don't get paid for it, which isn't true because open source is a thing. When you do open source, you are the one who has to live with the results. Forever. I think open source proves the point you're arguing against. Besides, the argument is not that they are paid peanuts, just that they are being paid for other things. The incentives are not lined up for freelancers to give high investment up front to reduce long term maintenance costs. That doesnt mean every freelancer writes crap code, just that on average its not a system that selects for easily maintainable code.
- crucialfelix 6y agoOr you keep trying to get time for refactoring and cleanups, but instead the product team keeps pushing for urgent new features and the project manager keeps questioning why development is getting slower and the defect rate is getting higher.
- atleta 6y agoNah. Besides professional intrinsic motivations (some people just can't convince themselves to produce shit) it also matters what the client wants and requires. Of course, a clueless non-technical client, esp. if they are inexperienced on top of this, will not care and thus my hire someone who works like you suggest. A bit more sophisticated client will find someone who's experienced in managing and hiring developers, a tech lead, and help them pick and sometimes giude/check-in on their freelancer. Though very few people actually do this.
- varispeed 6y agoFast - cheap - quality, pick two. That rule always apply.
- jamil7 6y ago> People aren't going to make clean code if they know they are never going to see it again and arent being paid for how clean it is. You realize freelancers often have ongoing relationships with their clients, right? As well as relying heavily on recommendations and referrals. Why would I risk putting shitty work out there?