[washadjeffmad]

Oof. Firing isn't free, comrade. Reducing redundancy to a single point of failure has two major effects: the latency penalty becomes quadratic as workload scales, and if any person quits, you lose the whole team.

In general, creative roles like artists are the sum value of their education and experience, not just their measured output. If you don't possess art history vocabulary, you're going to be very limited in prompting or designing more advanced embeddings and LoRA or training models. I'm seeing this a lot right now - people don't want to share their prompts because they don't want everyone to know how much the model carried them and how little any actual "prompt engineering" went into it.

The smart thing for their boss to do would be to scale projects and have one of them focus on managing and filtering the new volume of assets. Since it sounds like they like working from scratch, even adding external time to "research tooling and methods" would probably keep them happy until they find the challenge in their new duties.

[Hoasi]

> people don't want to share their prompts because they don't want everyone to know how much the model carried them and how little any actual "prompt engineering" went into it.

Right. Because this whole "prompt engineering" is just another job title, not an applied science, and then again, prompts can and will be automated away.

[Deegy]

Even if we agree that your strategy is optimal, it would require the manager acting in a significantly pragmatic manner.

I would wager that the majority of managers will rather reactively jump at the chance to cut an entire salary from their cost structure.

[the_lonely_road]

The majority of managers would jump at the opportunity to reduce their number of direct reports? Owners might want to cut salaries but managers want to increase direct reports.