Analysis of dev agencies with hourly rates, team size and tech stack
devquarterly.com
devquarterly.com
[1] https://devquarterly.com/report/q2_2020/web#developers_worki...
Nice for the agencies, not all that useful to this crowd for data collection. Alot of the numbers are just way, way off from industry standards so it makes me wonder where they got them.
The funny thing is that some of these companies outsourced to the Ukraine and India and the rates didn't change. I would have thought that we would at least see some of the cost savings.
Both companies that outsourced ended up being complete disasters (we are still cleaning up the technical debt 3+ years later), which happened before I was involved.
Since this is the case, it made no sense to hire any company that didn't hire all developers directly in the US or Canada (which is now a requirement).
I suppose I should thank these companies, because it's the reason I have a job today.
Tech seems to be the only industry that thinks that hiring writers from overseas to produce content is somehow going to result in anything viable.
https://www.nytimes.com/2006/11/19/business/worldbusiness/19...
https://archives.cjr.org/short_takes/outsourced_edit.php
https://www.theguardian.com/media/2004/oct/07/reuters.pressa...
more recent: https://www.theguardian.com/media/greenslade/2015/jul/27/jou...
I thought it was a great analogy.
The issue is more precision and lucidity of thought and language, and the ability to communicate ideas and emotion to others from a given culture and socioeconomic background.
Consider that when development velocity grinds to a halt because of "technical debt", this is almost always just a euphemism for developers not being able to read each other's code. (I understand there is an actual idea behind technical debt, I'm just talking about what's almost always happening in practice.)
My point being; there's an efficient way to utilize cheap labor.
Back to the programming reality from the analogy, I've seen outsourcing happen, for businesses that revolve around American customer bases and rules and regulations- now the code is outsourced, but the basic understanding of how business logic related to the real world use was gone. So the offshore team, while technically competent, was not equipped to make decisions about software with the consumer in mind. If you were working on something and it didn't really make sense in a real world sense, as a dev, you could go to your product person and raise concerns. Without the cultural context- those concerns never get raised.
Treat them like 1) there is a language barrier and 2) they will not know there is a language barrier and they will forge ahead in the wrong direction.
Some of the best developers and PMs I have worked with were born in a country you barely know about, it just took a little time to get to know them and their skillset.
That's a tall order, the root of a million missed deadlines is that software is notoriously hard to fully design without writing code.
Are you doing something you've done a hundred times before, or are there some twists?
That is the real work here; discovering acumen. Once you know that, you can hand out work that fits within their wheelhouse.
American developers excel at this because there's less of a communication gap. If an American can not do something he will tell you. If you are wrong about the way you are doing something, an American developer will tell you. Outsourced subcontractors will blindly do what they understood they were supposed to do without questioning anything resembling rationale.
Just know that going in.
You know what else is like that? A computer.
GIGO, etc.
The real problem is the incentive structure, and of course, difficulty of the job that is programming.
Why would the rates be lower if the market is one where demand for labor exceeds supply? It's not like lowering the rate is going to allow them to sell more hours, since they are still constrained by human capacity. If the quality of the work was not good, that's a different issue.
We had a rate card that included both the cost to the agency per hour for a particular role and the agreed rate we had settled with the client. We had a fixed rate for each role/locale even though we paid people different amounts. I knew my own salary and handful for my direct reports and the "cost" side of the rate card was a lot more than I was getting paid. And that cost was the base on which padded to get profit from the client.
And that profit itself wasn't pure profit for the company because a lot of paid for our fixed costs (office space, hardware) and non-billable roles (HR, receptionists). And of course a lot of it ends up in the hands of our holding company and their stock holders.
edit: after checking out the entire article now, it is quite insightful to be honest. Lots of interesting research and data. I think they should just make a simple html version like the craigslist website and it will be a super hit.
I feel like these numbers don’t add up.
There are for sure not 15k devs there. I’ve been to Andorra and visited a few meetups. They had very few people in attendance.
It reports fewer agency developers in China than in Andorra. The difference between the two represents 1% of Andorra's total population and 0.7E-4% of China's.
Both of them work well since they impose a structure and programming model that basically works for a lot of business software, so you can focus on the domain problems and move quickly over the standard tasks like an asset pipeline or account management.
Makes sense not seeing React, though. It is far more complicated and fragile to get SEO-friendly pages rendered with React (and there aren't many legacy systems that use it, either).
Can anyone give me any advice, books or podcasts, how to get better in business negotiation, to be more confident to ask a proper charge?
I've subcontracted out to folks, and even at a 2x markup, with the coordination, review, and other unbillable activities I made almost no profit. As a percentage, it was barely worth even having the initial leverage and I rarely did it (at 2x markup) unless it was strictly to meet a deadline. In large orgs where profit is a requirement for just about every interaction I can see how 3x or 4x would be necessary to justify doing the work in the first place.
Then the consulting agency obviously makes a nice profit off of it.
And then the consultant themselves can usually benefit from it as well, because typically they get a higher wage than the average employee to begin with, and also it becomes a very easy conversation to have with the company "just hire me as a FTE instead of paying the consulting company. My salary is currently $50/hr, you're paying them $150/hr for my work. Instead you can just pay me $100/hr, and we both benefit." I've seen a lot of consultant -> FTE transitions happen like that.
That only does work if the company is actually looking for a long-term FTE, though. Like I mentioned above, a lot of the time the company is paying the premium in the first place is so that they can quickly and easily drop you off their payroll if needed. They lose out on that by bringing you on as FTE.
The percentage that is overhead will vary, but only by so much. Otherwise, someone will come along and find a way to undercut your prices and take your business. It's reasonable to assume that if one hourly cost is double another, the developer's pay is higher.
(Not denying someone might find a way to really pull a scam in the short-term, and find a kid they can pay minimum wage to, but that's not a scalable or stable arrangement).
That's really only true if you assume that all of these dev agencies are equal. In reality, a lot of them have different specialties (both tech wise or industry wise), better (or worse) reputations, or certain partnerships. All of these things can greatly change the amount that the dev agency can charge.
I've personally seen plenty of agencies charging $100/hr while another agency with a different "specialization" (but otherwise similarly skilled and paid devs) charge $250/hr. The bill rate hardly ever corresponds with salary, IME.
Portugal with 37$, never seen such salaries here..
I encounter this sort of thing so often, and it’s really, really bad. Positively awful. Super disconcerting.
In most cases like this, it’s just that one slide is longer than the others. In this case, there are a couple like that, but also for the rest, image tags have been used without specifying their dimensions, so they take up no space as the carousel slide enters, and then once the image starts loading they reflow instantaneously as the dimenions are known.
Please, if you have a carousel, you must make sure that its height never changes as it progresses. (And please always put width and height on your images, too, so the intrinsic aspect ratio can be applied properly.)
Oh, and auto-progressing carousels as a whole are a blight, but a sometimes-just-barely-tolerable one. So long as they’ll just stop progressing once I interact with them! Please!
Does anyone like carousels? I encounter software developers railing against them, I encounter normal people railing against them (from recently, a non-techie had one request about a new site, that the carousel inserted by the developer of the prototype—because it was a part of the WordPress theme used—be removed), I honestly can’t think of having encountered a single person that likes carousels. They’re just all-round irritating.
If you can afford to hide content why even put it in the first place? Specially on the most prominent part of your website.
If you want to deliver a message focus on essential content that cannot be hidden.