Sure, if you are hiring one person to do two jobs, it is going to be a struggle. Even two jobs that are related to each other - if they have different skill sets, it is two different roles.

Take racing as an example. Drivers and mechanics are clearly related and both critical to success. And most drivers can handle some mechanic work, while most mechanics can drive. But you don't have one person doing both roles on race day.

Hiring one person to do two jobs increases the time to the finish line. You same some money, but you come in last.

▲

ablazevics a day ago | parent | next [-]

Fairs though the counter I keep hearing is that it's less two jobs than one job with a handoff removed, which is where the time savings supposedly come from.

▲

codingdave a day ago | parent [-]

And who are you hearing that from? Designers and engineers? Or managers who want it to be true?

	▲	dieselgate a day ago \| parent \| next [-]
		In my experience as a developer it's true but I won't evangelize the point. For example: writing tickets is often done better by a developer rather than a non-technical PM/PO even though it's not a typical developer task.
	▲	ablazevics a day ago \| parent \| prev [-]
		[dead]

▲

dieselgate a day ago | parent | prev [-]

I think that's a great analogy. My only comment regarding "You [sic] same some money, but you come in last" is that sometimes you only need to finish the race rather than win. It's not always the case but happens often enough to be considered in my experience