One Full-Stack programmer or two (Backend and Frontend)?

Question

Work organization

Hello.
For the first year since the creation of the site, I worked with Full-Stack freelance programmers (it is not yet possible to take on a full day).
It so happened that before the last programmer left, they began to implement Angular.
The problem is that when looking for a new developer, I noticed that this time I'm not looking for a " good Java developer " as before, but a " Java developer who knows Angular ".
The "good" requirement has lost some of its weight since I have to choose from those that know Angular.
This confused me and I thought about the option of working with two programmers (Backend and Frontend).
But I don’t really understand how this happens and how to divide tasks.
Previously, I simply set the task "Add a field", painted how it should work, and all this was done by one person (and created a column in the database, and wrote the code in HTML). After that, he indicated the amount of time spent and I paid for the work.
How to delegate this if I have two programmers? Will I need to set two tasks (for the backend and frontend) or will they have to interact with each other and decide who does what work?
In general , I would be grateful for a hint, what are the features of working with programmers who have different responsibilities, and how best to proceed.
Thanks

Answer 1

I would take two (as a matter of fact we do). Performance will definitely be better. But only on condition that you organize the interaction between developers well. It is better, of course, that people sit in the same office.
Options how to organize:
1. Only one ticket is placed. Assigned to the one who must make his piece first. After that, he transfers the ticket to another performer. If people sit in the same office, they can work on the ticket in parallel. When they did, they passed the test.
2. One common task is set. Subtasks are thrown under it. Everything is started separately for the backend, separately for the frontend. All tasks are closed - the main ticket goes to testing. Found bugs are again entered as subtasks. And so on until it closes.
The first option is better - less duplication of information.

Answer 2

Moving to two highly specialized specialists is a very big step for such a small project.
You win by qualification.
The quality of work will (theoretically) increase dramatically.
But the costs will also increase decently.