[humps]

If I was in that situation I would take the time to plan out in as fine detail as possible a task list for each day for each person. There are several benefits to doing this:

- They know exactly what needs to be done and are expected to do, so even the Maverick is placed on a leash.

- You are probably going to return to a mess anyway, but this way you (and your boss) have the task lists to point to as evidence when reprimanding or even removing people from the team down the line.

- You're covering yourself if the project does get delayed. You did everything you could to help the team while you weren't there.

Your boss may not be technical, but if he has these task lists for each person and you sit down and go through them with him before you leave, he can do daily checks to keep them on track.

Finally, switch off and enjoy your vacation. There is nothing you can do while you are away and probably a lot you will have to do when you return, so throw yourself into the break and enjoy it as much as possible.

[nprateem]

With a side benefit of demotivating both staff so much they'll probably leave as well. Very clever!

[dtech]

If a team is in a messy state or firefighting mode, an authoritarian and micro-managery leadership style can work very well, and even be appreciated by the team.

[qikInNdOutReply]

Nah, you sort out free spirits and free thinkers and leave behind cooperate bedrock bureacrat coders. But then again, this is the reason why we have startup culture, cause this works so well, the grinders have to pay to get innovation externally.

[toqti]

Wouldn't be a huge loss to be honest.

[smegsicle]

easier than firing them atleast