4 ms·
If you have each client take on the $ burden, then you don't have this problem. You've may have convinced yourself that by absorbing the cost, you are doing yo
by wilmoore 14y ago
If you have each client take on the $ burden, then you don't have this problem. You've may have convinced yourself that by absorbing the cost, you are doing your client a great service.
In fact, you are putting more burden on yourself for little value. It takes 15 minutes to walk the client through how to pay for and manage a github organization. I do it with all of my clients. It is an opportunity to teach/coach and give them a sense of ownership which is how it should be.
- LordIllidan 14y agoYou make a good point in that this could be absorbed as an implicit cost of a client project - but tell me again, why would we do this, when we can simply use BitBucket and create as many repositories as we like, without any problems whatsoever? Our only limit is then the amount of people we hire, which is far more reasonable in my eyes. If we were working on a small number of projects, then it would absolutely not be a problem to work with Github - it's when you have a lot of tiny projects that it becomes prohibitively expensive to work with. Fair enough, that's how Github wants to price their service - I guess its catered more to actual startups (who have a few large core projects) rather than businesses like ours.