I think this only works when everyone involved is reasonably capable and experienced. Pure management numskulls that can't code themselves out of a while loop are never going to get it. No need for them in my little universe.
I've been in the game long enough to know just how funny it is to say "Here's the deadline for this project". Really? How in the world did you come up with that date? This isn't to say that one should not have a sense of how long something will take, but software projects are notoriously tough to estimate from just about every perspective.
I'm not sure what "load balancing" means. Are you asking about one person working more than another or the rate of code produced per unit time (say, per day)?
I mean "load balancing" in the sense of the amount of work that get assigned to an employee so that you don't get tasks like designing an ORM from scratch in less than week just because your PM heard bad things about Hibernate.
If the answer is don't work for assholes or retards, then that fails for everyone outside of a major tech centre where you take whatever jobs are available.
Well, all situations are not the same. Obviously things will be different when managers are knowledgeable. This doesn't mean that they have to know it all. I like people who come right out and say "I don't know much about this" because then everyone starts learning. It elevates the conversation from nonsense to something constructive.
My problem is that I see this used as way of forcing unpaid overtime on to workers by creating unreasonable release dates. In an agile environment where people are given lots of autonomy and can give accurate estimates I like your idea, but it seems for most it will be a disaster. We've recently had a client demand we deliver a month earlier on 6 month project in a 5 man shop with only two months left. If it wasn't for paid overtime I'd bail out of here.
I've been in the game long enough to know just how funny it is to say "Here's the deadline for this project". Really? How in the world did you come up with that date? This isn't to say that one should not have a sense of how long something will take, but software projects are notoriously tough to estimate from just about every perspective.
I'm not sure what "load balancing" means. Are you asking about one person working more than another or the rate of code produced per unit time (say, per day)?