Quote:
Originally Posted by azxten
[You must be logged in to view images. Log in or Register.]
Yes, but this is what I mean about working on a business instead of in it. Instead of continually doing work that will always need to be done you should be working on eliminating or off loading work to free up your time.
It's kind of like imagining the manger of a McDonalds being too busy cooking fries to do anything else because it's "too hard to protect the cash drawer" to trust anyone to cook the fries. No, it's not too hard to protect the cash drawer if you take the time to put a safe in the store and instruct the people cooking fries to put their money in the safe every 2 hours. Then you find that you have the time to work on more important things than cooking fries and the cash drawer safety issue has been eliminated because only you have access to the safe.
|
True enough, its just that building out a system whereby you can safely farm out certain edits and classes of jobs/tasks is usually not a simple matter. You need a system of permissions, data that describes these permissions, user structures that work with these permissions, web interfaces to allow protected edits to various entities...all wrapped on top of what is essentially a big set of code files and some db tables that have no intrinsic protections. Its often not as simple as just buying a safe and instructing people.